Getting Started
Choose the right audience track, complete the minimum safety checks, and avoid jumping into advanced specs before you need them.
#
- Confirm your role for this session: user, merchant operator, or integration developer.
- Use the official Ryvra domain and approved account access path.
- Have access to the environment you need (account wallet, merchant workspace, or integration sandbox).
- Understand that AI may propose work, but authorization stays in Ryvra control systems and finality stays in ledger and settlement.
#
- Open the documentation landing page and choose your persona track.
- Read the guide overview page for role-specific assumptions, authority boundaries, and safety controls.
- Review governance and security guidance before enabling any autonomous-finance workflow.
- Complete the role-specific prerequisites page before executing live actions.
- Run one low-risk workflow end to end and verify terminal status against ledger and settlement outputs.
- Use the RFC index and glossary to validate current terminology, interfaces, and rollout scope.
#Audience-first routes
#Expected outcome
- You can identify the correct guide and complete first-step workflows without route ambiguity.
- You know when to stay in the plain-language track and when to open the deeper specification layer.
- You can escalate to role-specific troubleshooting guidance when an operation fails or must be suspended.
#Common failures
- Starting from the wrong persona guide and applying incorrect assumptions.
- Skipping prerequisite checks and encountering preventable validation failures.
- Opening jargon-heavy material too early and missing the simpler workflow explanation.
#
- Return to the documentation landing page and switch to the correct persona guide.
- Re-run prerequisite checklists before repeating failed operations.
- Validate latest guidance in tokenomics, security, release notes, and relevant troubleshooting pages.