Outcome
A practitioner can move from the public getting-started entry point to a successful AURA run against real data in under five minutes on a supported platform.
Journey
- Find the supported install path without choosing an artifact.
- Install and invoke
aura.
- Start from a batteries-included configuration.
- Run
/mcp add and choose a supported curated or custom MCP server.
- Provide credentials through the guided flow.
- Verify the connection and discovered tools before saving.
- Grant the tools only to the worker roles that need them.
- Restart AURA so the new configuration takes effect.
- Run the suggested starter prompt against real data.
Acceptance criteria
- The happy path is documented as one coherent journey.
- Supported prerequisites and credentials are stated before the user begins.
- The guide reflects that
/mcp add is currently a standalone-mode workflow.
- Connection failure identifies a concrete recovery action.
- Worker access is explicit and follows least privilege.
- The required restart is stated at the point it is needed.
- The first streamed response does not present unexplained dead air.
- Internal demos and onboarding use this journey rather than cloning the repository or building from source.
- A timed validation on each supported platform demonstrates that the median happy path is under five minutes.
Related epics: #212, #309, #310
Parent epic: #311
Initiative: #370
Outcome
A practitioner can move from the public getting-started entry point to a successful AURA run against real data in under five minutes on a supported platform.
Journey
aura./mcp addand choose a supported curated or custom MCP server.Acceptance criteria
/mcp addis currently a standalone-mode workflow.Related epics: #212, #309, #310
Parent epic: #311
Initiative: #370