Use case
Beta
Documentation
The spec, the decision and the sign-off are outputs of the run itself, kept in Memory — not homework once the work is done.
The stage, and what it produces
What it is
Because each stage produces a reviewed artifact, your documentation is a byproduct of delivery. Memory keeps the decisions, constraints and reasoning as a graph the next run can read — instead of pages someone has to keep current.
Kept from the run In Memory
- Decision: idempotency via keys
- Constraint: PCI scope minimized
- Spec + acceptance criteria
- Sign-off: Inès · 12 Aug
Illustrative — produced, reviewed and approved before the next step.
In a run
What the stage runs through
- Artifacts produced at each checkpoint
- Decisions and reasoning kept in Memory
- Retrievable by the next run, as context
- No separate doc to write or maintain
Works with
The parts of the platform it leans on
Where it stands. Memory ships today (Beta). The full chain of artifacts grows as orchestration lands.
Turn this stage into a governed output
Start with what ships today, and grow into the full run as it lands.