Artifacts and Deliverables - VVG-web/aurora-studio GitHub Wiki
Wiki home ยท related: Asking the base ยท Trust ยท commands: practice
An artifact is a document an analyst or the agent produces โ a user story, acceptance criteria, an algorithm, a
specification, a review. It lives in Artifacts/<type>/ and is never knowledge: it is not read back as a fact.
Only cards are. A deliverable is an artifact that has been assembled and handed outward.
flowchart LR
Q["a task in your words"] --> E["enrichment<br>from the base"] --> P["a plan with<br>questions to you"] --> W["worker<br>drafts"] --> K["critic"] --> M["Momus<br>checks claims"]
M --> A["Artifacts/<type>/<br>based_on filled in"]
A -->|"make:review"| R["Artifacts/reviews/"]
A -->|"ship:export"| X["docx / pdf"]
A -->|"ship:publish"| C["Confluence<br>generated page"]
X -->|"ship:release"| F["Deliverables/released/<br>immutable"]
| Do | Command | Notes |
|---|---|---|
| Write a story, criteria, an algorithm, a spec |
agent:make (panel: Production โ type โ task) |
stages are marked in the file header, so after an interruption it resumes from the same point |
| Find out which template and where | make:kinds |
the project's registry of artifact kinds: template, folder, prompt, "no technologies" rule, the final-text boundary |
| Assemble a spec from requirements | make:spec <topic> |
SPEC-NNN, status draft, a full based_on
|
| Hand a spec to a contractor | make:spec-pack <SPEC-NNN> |
a self-contained bundle: grounds, decisions, abbreviations, handoff risks |
| Check the contractor's implementation | make:validate <SPEC> <object> |
covered / contradicts / not implemented, per scenario |
| Assemble an OPZ, PMI or user guide | make:assemble <document> |
a document from the base by a template |
Write the task in your own words; it understands @path, /skill, @server and attachments (kept for two weeks).
Every artifact carries based_on โ the cards it stands on โ so you can see what to revisit when knowledge changes
(ops:impact --explain <document>).
| Do | Command |
|---|---|
| Check a story or criteria against the base |
make:review <object> โ a verdict and remarks that quote the cards the text contradicts |
| Check without a human, by a closed checklist |
make:review-auto โ three model runs vote on each question, a script computes the score; --page, --cql, a batch mode |
| Do | Command | Result |
|---|---|---|
| Office format | ship:export <file> |
docx or pdf through pandoc (needs it installed) |
| Publish | ship:publish <file> |
a generated page in Confluence; the production kitchen โ everything below the marker โ does not go out |
| Freeze what was delivered | ship:release <document> |
an immutable snapshot in Deliverables/released/ and a commit of the base |
| Acceptance | ship:acceptance <object> |
a report; customer remarks sorted into defect / requirement / question / disagreement |
released/ is immutable. The panel's editor opens it read-only. Without freezing you cannot prove what you
delivered. Drafts live in Deliverables/work/; delivery packages and versions taken off work โ in
Deliverables/_archive/.
Next to the story and criteria templates, TemplatesCommon/ holds thirteen akdb_<type>_v1.0.md templates. They
describe knowledge cards in AuroraKnowledgeDB/, not documents in Artifacts/: an artifact is never a card,
and a card is never an artifact. They are not listed in the registry of artifact kinds (make:kinds) and are not
chosen for producing documents. โ The card
ops:trace follows a chain from the customer's spec item โ requirement โ specification โ Jira issue โ criteria โ
acceptance, and shows where it is broken. sync:jira-status suggests which requirements are implemented from issue
statuses. โ Daily work
This wiki is generated from the wiki/ folder of the repository โ edit the pages there, changes made here are overwritten. ยท RU-Home