Version 1.5 records Jason's Q167 ruling and added text as its source block. It replaces REQ-DEC-2 routing: a gated decision citing the project's current spec commit goes to the domain arbiter, and only an uncited decision or a hard wait goes to the human. It adds the hard waits (REQ-WAIT-1 to 3, with data.delete, network.expose and account.create), projects and the spec file (REQ-PROJ-1 to 4), agent landing (REQ-LAND-1), approvals that outlive the run (REQ-DEC-5), settled decisions under a new spec (REQ-DEC-6), the four workflow roles and proactive contracts (REQ-ROLE-5, 6), staff requests (REQ-COS-2), assistant summaries (REQ-ASSIST-3) and name addressing (REQ-MSG-2). docs/acceptance/314.md is the run Jason does in the Stack once the rows are live. Co-Authored-By: Claude Opus 5.5 <[email protected]>
153 lines
5.2 KiB
Markdown
153 lines
5.2 KiB
Markdown
# Acceptance run for task 314 (Q167)
|
|
|
|
Jason runs this inside the Stack once rows 135 to 143 and 147 to 149 are
|
|
live. It checks PRD version 1.5: one need goes from his spec to a landed
|
|
commit, and only hard waits reach his inbox.
|
|
|
|
`<business>` is the business the bus host runs. `<project>` is the
|
|
project the need belongs to, `stack` for this run. Every command runs on
|
|
the host, as Jason.
|
|
|
|
The need is a `mosaic version` command that prints the release and the
|
|
bus schema.
|
|
|
|
## Before the run
|
|
|
|
- `mosaic bus status` says the host is live.
|
|
- `mosaic inbox` shows no open decision. If one is open, resolve or
|
|
supersede it first, so step 6 starts from an empty inbox.
|
|
- The organization has security-reviewer and merge-gate instances, added
|
|
through the chief of staff's organization change with Mos's go, and
|
|
both are in `launch.instances`.
|
|
- `arbiters.technical` is `cto`, which step 5 assumes.
|
|
|
|
## Steps
|
|
|
|
1. Create the project repository, if it doesn't exist yet:
|
|
|
|
```
|
|
mosaic project init <business> <project>
|
|
mosaic project check <business> <project>
|
|
```
|
|
|
|
Pass: `check` reports the layout valid. The first commit's author is
|
|
Jason. (REQ-PROJ-1)
|
|
|
|
2. Open the spec in the Console editor and write it:
|
|
|
|
> North star: anyone can tell what is running in one command.
|
|
> Need: a `mosaic version` command that prints the release and the bus
|
|
> schema.
|
|
|
|
Before saving, open the same file in a second Console tab. Save in the
|
|
first tab. Pass: the save makes one local commit with Jason as author,
|
|
and the editor shows the new commit. Then edit and save in the second
|
|
tab, which still holds the old commit: the save is refused and writes
|
|
nothing. (REQ-PROJ-2, REQ-PROJ-3)
|
|
|
|
3. Tell the assistant about the need:
|
|
|
|
```
|
|
mosaic talk assistant "New need: the mosaic version command in spec/north-star.md. Start it."
|
|
```
|
|
|
|
Pass: `talk` prints only the assistant's reply to this message.
|
|
|
|
4. Watch the work start:
|
|
|
|
```
|
|
mosaic tasks
|
|
mosaic agents
|
|
mosaic trail <task>
|
|
```
|
|
|
|
Pass, all on the trail:
|
|
- pm makes the tasks and sends the chief of staff a staff request
|
|
naming the roles and counts (REQ-COS-2);
|
|
- the chief of staff launches a coder, a reviewer and a
|
|
security-reviewer through role.launch (REQ-ROLE-5);
|
|
- the coder pushes a work ref, and the reviewer and the
|
|
security-reviewer each approve it.
|
|
|
|
5. Watch it land:
|
|
|
|
```
|
|
mosaic trail <decision>
|
|
git -C <working repository> log --oneline -3 main
|
|
```
|
|
|
|
Pass:
|
|
- pm hands the approved candidate to merge-gate, and merge-gate
|
|
raises the `git.merge.protected` decision citing
|
|
`spec/north-star.md` at the commit from step 2;
|
|
- the CTO resolves it, not Jason (REQ-DEC-2);
|
|
- merge-gate lands it, the trail records the allowed action with the
|
|
landed commit, and the commit is on the working repository's `main`
|
|
(REQ-LAND-1).
|
|
|
|
6. Check the inbox, then ask for one hard wait on purpose:
|
|
|
|
```
|
|
mosaic inbox
|
|
mosaic talk assistant "Open a new account for the project on an outside service."
|
|
mosaic inbox
|
|
```
|
|
|
|
Pass: the first `inbox` is empty, so nothing from steps 3 to 5 reached
|
|
Jason. After the request, the inbox holds one decision for
|
|
`account.create`. Resolve it with the reject option. (REQ-WAIT-1)
|
|
|
|
7. Restart the host halfway through the next merge. Use a second small
|
|
change, for example "print the help when an option is unknown", and
|
|
restart once the CTO has resolved its merge decision and before
|
|
merge-gate lands it. Mos or Jason runs the restart:
|
|
|
|
```
|
|
mosaic bus stop
|
|
mosaic bus start <business> --pm
|
|
```
|
|
|
|
Pass: the merge lands from a new run of the same merge-gate instance
|
|
with the approval from before the restart, and no new decision is
|
|
raised.
|
|
(REQ-DEC-5)
|
|
|
|
8. Change the spec in the Console editor: also print the commit. Save.
|
|
|
|
Pass:
|
|
- the save makes a new commit by Jason;
|
|
- `mosaic trail` shows no decision settled under the step 2 commit
|
|
reopened (REQ-DEC-6);
|
|
- `mosaic trail` shows new raises citing the new commit, and no
|
|
raise citing the step 2 commit accepted after the save;
|
|
- pm and the CTO each answer the spec commit with an accept
|
|
(REQ-PROJ-4).
|
|
|
|
9. Change the spec in a way that breaks a settled decision, for example:
|
|
"the version command prints nothing and exits." Save.
|
|
|
|
Pass: pm or the CTO answers with a BLOCK naming the conflict, the
|
|
commit stays, and the assistant tells Jason about the block in its own
|
|
words. The assistant's message doesn't quote the chief of staff's text.
|
|
(REQ-PROJ-4, REQ-ASSIST-3) Then revert the spec in the editor with a
|
|
new commit.
|
|
|
|
10. Give the coder instance a name with the CLI command row 141 adds
|
|
(`docs/TOOLS.md` names it once that row lands), then send it a
|
|
message by that name:
|
|
|
|
```
|
|
mosaic agents
|
|
mosaic talk <name from the agents list> "Reply with your role name."
|
|
```
|
|
|
|
Pass: the reply comes from the instance with that name, and the trail
|
|
records both the name and the instance. (REQ-MSG-2)
|
|
|
|
## Result
|
|
|
|
The run passes when every step passes. Record the run with the date, the
|
|
release, the bus schema and the result of each step in Vikunja task 314.
|
|
A failed step names the requirement it checks, so the fix goes back to
|
|
that row.
|