mosaicstack/stack
25
0
Fork 1
Code Issues 358 Pull Requests 13 Actions Packages Projects Releases 15 Wiki Activity

docs(rocko): slice 1 S2 preparation packet (record)

Browse Source 
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
jason.woltje
2026-10-04 21:56:11 -05:00
co-authored by Claude Opus 5.5
parent 06cf0d33d6
commit b02aade221
1 changed files with 37 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/rocko/work/slice1-s2-preparation-2026-10-04.md
+37
View File
@@ -0,0 +1,37 @@
# Slice 1 S2 preparation
RESULT: preparation complete; implementation not started. Sage explicitly holds S2 until Darkwing's schema v3 lands and Sage sends the start instruction. The queue currently points Rocko to row 37; that does not override the hold. Row 39/S4 follows S2 and S3.
## Inputs read
Brief commit: `43c48d7a`, S2 section and shared slice rules. Content pins at preparation:
| File | SHA256 |
|---|---|
| docs/plans/2026-10-04_slice-1.md | `655e12906286d290cc38e9daeb7bc8838e5003bdf1738bc68764a4bf52de9c81` |
| agents/darkwing/work/slice1-data-model-2026-10-04.md | `948b94ce8c48628c6ada2be14a79547dffffa08bc26b4016960324ef263c6ce0` |
| agents/darkwing/work/slice1-data-model-addendum-2026-10-04.md | `0b36acb022a10941a7bc7b0546bd03ec17ca781f11349ec0ccdd79f1cef0789d` |
| agents/darkwing/work/slice1-data-model-addendum-b-2026-10-04.md | `14e747f5067d12d5fc0aa7994c38108f38c2d116b94b67a216b11af99fbda879` |
| agents/darkwing/work/slice1-proto/proto-v2.mjs | `d428da74ef487b9e0e951af621b7b7409ae2850c8884cb1f19b706919bcbeaa1` |
| agents/darkwing/work/slice1-proto/proto-v2-notes.md | `90ce5645bc6dec5754df5b0ed1d1c8f69db2d2bfa589e0562afbf52c6ac53125` |
Precedence: B over A over the original note. The original token-to-agent language and Vikunja assumptions are superseded, not implementation guidance.
## Acceptance to carry into the build
- Ownership: new `packages/bus/`, its store, broker/socket protocol, verbs and tests. Runtime `<dataRoot>/bus/` is broker-created, mode 0700. S2 is Gitea #1519, reviewer Darkwing. Sage makes all Gitea posts and commits.
- Store: schema v3, node:sqlite, WAL, open-time schema digest validation, append-only tables. Preserve the prototype's replacement guards as well as UPDATE/DELETE guards. The v2 digest covers schema tables, indexes, triggers and views, not triggers alone.
- Broker: sole cooperative writer; stamp role/run from launch records rather than caller-supplied identity. Keep the same-OS-user limitation explicit; this is not isolation from a hostile same-user process.
- Decisions: raise, route and resolve; log within-role outcomes, route cross-role decisions to the configured arbiter and gated decisions to the human. Gated actions need a matching resolved decision. Human resolution and launch revoke/restore take only the outside-agent CLI path.
- Claims/messages/events: one role holder, holder-only release, decision-backed revoke, role-addressed delivery to the current holder, append-only delivery history, and the closed event vocabulary. Do not silently treat stale transport addresses as current role authority.
- Tokens: fixture tokens only for S2. Only the broker reads contents; memory only, no logs or persistent copies and no agent-child exposure. Resolver/launcher references are metadata, not permission to pass service tokens to agents.
- Schema-v3 handoff: addendum B section 5 adds snapshot `via` and `read_at`, integer bucket/tombstone constraints, stale-read ordering in `task_external_changes`, and `tasks_open`. S2 ships that schema; S3 owns task writes, polling, live scope probes and Vikunja integration.
- Gate: every prototype refusal becomes asserted acceptance coverage; broker protocol coverage; bus tests on Node 24 and Node 26; every `scripts/test-*.sh` on the required index export; Darkwing's review before Sage commits. Prototype notes report prior runs, but preparation has not rerun or certified them.
## Handoffs before coding
Wait for Sage's schema-v3/start message. At that point pin the actual schema and prototype handoff, recover current owner rulings, and settle the interfaces to S1's business/authority loaders and S6's launch records against those artifacts. Do not freeze an interface from the superseded design sketches now.
S4 remains subsequent work: CLI reads through the broker, outside-agent human decisions, inbox/tasks/agents/trail, and the owned outbound notification/digest path. It is not started as part of this preparation.
No application source, schema, role policy, queue state or credential file was changed. No tests, model calls, live requests, launches, commits or pushes were performed. This packet records reading and readiness only.