amadan
plan: account for review and Home owner coordination
1 file changed,
+51
−4
implementation/overnight-2026-09-07.md+51 −4
No CI script — run details
CI log
amadan: no CI script — add an executable .amadan/ci or a `ci` target to the Makefile
diff --git a/implementation/overnight-2026-09-07.md b/implementation/overnight-2026-09-07.md| index 17e080a..4d470f1 100644 |
| --- a/implementation/overnight-2026-09-07.md |
| +++ b/implementation/overnight-2026-09-07.md |
| @@ -1,6 +1,6 @@ |
| # Oficina implementation run, 2026-09-07 |
| -Status: execution queue; independent Fable review pending. |
| +Status: execution queue; Fable review 1 requested changes; corrections below. |
| Operator authorization: Paul requested implementation of the entire readiness |
| assessment, parallel agents, Amadan coordination, and continuous deployments. |
| Coordinator session: oficina-overnight-root-20260907 (Codex). |
| @@ -36,8 +36,8 @@ requiring weeks of real-team use cannot be completed by overnight code changes. |
| | Track | Owner | First slice | Next dependency | |
| |---|---|---|---| |
| -| Home | /root/home_track | Separate credential and directory origins, existing assertion-plan task 1 | Reviewed assertion wire and consumer rollout | |
| -| Docs | /root/docs_track | Content sealing with explicit legacy migration limits | Key provisioning and safe rollout | |
| +| Home | Existing Claude session d63f5ac7; /root/home_track supports | Origin split independently reviewed; support branch paused for ownership handoff | Existing owner acknowledgment, isolated canary, SMTP readiness | |
| +| Docs | /root/docs_track | Reviewed crypto primitive and tests; rollout amendment awaiting review | Compatible read/write states, key provisioning, restore rehearsal | |
| | Sheets | /root/sheets_track | Atomic batch cell writes and paste correctness | Workbook tabs and stable references | |
| | Suite | /root | Track all work, Fable review, canary coordination, contract prerequisites | Independent slices below | |
| @@ -78,7 +78,9 @@ An entry is not complete merely because its first branch lands. |
| consume suite discussion 3 (signed-in participants) and platform media stages |
| 4a/4b; prejoin/devices, guests, host controls, media/screenshare/reconnect, |
| multi-person calls, Calendar links, accessibility/captions, measured limits. |
| -13. Shared experience: Estilo adoption from actual two-app implementations, |
| +13. Shared experience: first builder creates shared primitive in Estilo, second |
| + adopter validates/corrects it. Save status: Docs builds, Slides adopts. |
| + Comment thread/inspector/presence: Docs first, Sheets or Slides second. |
| consistent sharing/comments/presence/errors/save states/navigation; recent, |
| shared-with-me/favourites/project grouping; actionable notifications. |
| 14. Migration: folder trees, permission mapping, compatibility reports, stable |
| @@ -119,3 +121,48 @@ No invented deadline, pricing, customer evidence, or readiness percentage. |
| No automatic deletion of legacy data, credentials, backups, or other worktrees. |
| No unreviewed shared deployment. Reviewer outages leave candidate branches queued |
| while implementation and other independent checks continue. |
| + |
| +## Review 1 corrections and verified dependencies |
| + |
| +Fable 5.1 (claude-fable-5-1) reviewed the initial queue in session |
| +6353bce7-f4f4-4be7-86f3-465c48708a86; verdict REQUEST CHANGES. |
| +Full review is retained there and posted to suite discussion 5. |
| + |
| +- Home origin routing now has its own independently reviewed bounded spec, |
| + separate from the unfinished assertion plan. Platform inspection confirms both |
| + public domains attached to home.bds.oncarlos.com. Existing signing-related |
| + secret names exist, but a future assertion key is not assumed provisioned. |
| + Existing Claude owner retains Home completion and rollout; our support branch |
| + is held pending coordination (requested by Paul). No production restart until |
| + mail/config/canary prerequisites pass. Preserve existing production keys. |
| +- Docs crypto spec reviewed; compatibility activation amendment awaiting review. |
| + First deploy must remain compatible with unconverted storage. Seal activation |
| + is a separate controlled maintenance step, never an opportunistic boot rewrite. |
| + Rollback target must read candidate-written data; test that against the exact |
| + target before activation. Historical backups remain, with explicit leak limits. |
| +- Module importability is verified rather than inferred: /root/home_track built |
| + fresh Memoria main b9e5de9 with CGO_ENABLED=0; it downloaded suite 60b01a8 and |
| + compiled successfully. README importability status is stale. AHEAD recovery |
| + contract and producer/consumer adoption remain a separate owned work package. |
| +- Estilo's first builder/second adopter is explicit above. Each first app pin is |
| + reviewed independently; existing token drift tests stay binding. Caller-supplied |
| + localized strings are reused verbatim, with no English fallback in primitives. |
| +- Coupled deploy order: compatible consumers and their tests prepared first; |
| + Home verification keys/issuer live before any consumer enables suite sign-in; |
| + roster enforcement tested separately. Keep lone-mode behavior while disabled. |
| +- Version endpoint verification is required on each actual app deployment. |
| + Framework-provided /api/version is not absent merely because app routes do not |
| + mention it; prove the actual endpoint before relying on it. |
| +- Before identity/content activation, rehearse restore of data plus keys and |
| + permissions on isolated fixtures. This is a prerequisite, not end-of-run polish. |
| +- Copy rules: /home/paulca/.agents/skills/copy-review/SKILL.md and |
| + /home/paulca/.agents/skills/writing-pipeline/SKILL.md. Stage strings, serve using |
| + copy-review/serve.sh, apply approved result verbatim. Agent execution plans and |
| + coordination prompts are not product copy. |
| +- /root/* names are agent task identifiers, not paths. Agents report actual |
| + isolated worktrees in each app discussion. Never treat the names as checkouts. |
| +- Meet uses the already-recorded participant ruling (suite #3); original owner's |
| + full spec and outstanding approvals must be located before app implementation. |
| +- Fable quota reported reset at 20:50 Europe/Dublin; prepare reviewable work and |
| + evidence until then. Do not replace Fable silently or treat a quota reply as |
| + a review verdict. |