amadan
plan: coordinate the Oficina overnight readiness run
1 file changed,
+121
−0
implementation/overnight-2026-09-07.md+121 −0
CI cancelled — superseded by a newer push — run details
diff --git a/implementation/overnight-2026-09-07.md b/implementation/overnight-2026-09-07.md| new file mode 100644 |
| index 0000000..17e080a |
| --- /dev/null |
| +++ b/implementation/overnight-2026-09-07.md |
| @@ -0,0 +1,121 @@ |
| +# Oficina implementation run, 2026-09-07 |
| + |
| +Status: execution queue; independent Fable review pending. |
| +Operator authorization: Paul requested implementation of the entire readiness |
| +assessment, parallel agents, Amadan coordination, and continuous deployments. |
| +Coordinator session: oficina-overnight-root-20260907 (Codex). |
| +Independent reviewer: Claude Fable 5.1, canonical claude-fable-5-1, connectivity |
| +verified 2026-09-07 using the installed Claude CLI. |
| + |
| +This is an agent execution plan. It changes no suite ruling. Consume the |
| +doctrine at 60b01a8 and each app's current design by citation, not restatement. |
| +The goal stays open while required implementation remains. Readiness validation |
| +requiring weeks of real-team use cannot be completed by overnight code changes. |
| + |
| +## Execution protocol |
| + |
| +1. Fetch before reading current specs. Read repository instructions and existing |
| + discussions. Preserve ongoing sessions and their worktrees. |
| +2. Claim one bounded slice in an Amadan branch discussion; add checklist tasks. |
| +3. Write and independently review a spec where required. Implement in an isolated |
| + worktree. Reuse existing approved copy; prepare new strings for copy review. |
| +4. Run appropriate repository and browser checks. Request Fable review of the |
| + complete diff, resolve findings, and repeat review after material changes. |
| +5. Deploy a canary as required by repository policy. Record tested revision, |
| + browser results, rollback target, and migration compatibility. |
| +6. Push and verify actual remote CI. Merge only with required reviews and gates. |
| + Deploy exact merged main to shared hosts, verify the process's /api/version |
| + and relevant browser workflow, then update Amadan tasks. |
| +7. For data migrations, preserve backup/key recovery. Do not erase historical |
| + backups as a side effect of introducing encryption or other features. |
| +8. Record blocked prerequisites precisely. Work on the next independent slice |
| + instead of repeatedly waiting. Never turn a blocked feature into a stub |
| + represented as complete. |
| + |
| +## Initial active work |
| + |
| +| 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 | |
| +| 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 | |
| + |
| +## Complete feature queue |
| + |
| +Each numbered entry is a work package, split into reviewed deployable branches. |
| +An entry is not complete merely because its first branch lands. |
| + |
| +1. Home: assertions, suite sign-in consumers, membership/roster, team invitations, |
| + provisioning, team switching, owner recovery, departure/access review, activity. |
| +2. Docs content: images, tables, links across edit/read/export; incorporate or |
| + supersede existing import branch after coordination; DOCX import/export fidelity. |
| +3. Docs review: anchored/orphaned/resolved comments, mentions, notifications, |
| + suggestions accept/reject, named versions and safe restore. |
| +4. Docs lifecycle: rename/duplicate/organisation/trash and durable interrupted-edit |
| + recovery; prove content sealing and honest limits across live/legacy storage. |
| +5. Sheets correctness: atomic bulk writes, reachable tabs, multiple worksheet |
| + import/export, cross-tab references, stable structural edits, copy/paste. |
| +6. Sheets usability: consistent sort/filter, CSV policy and routes, validation, |
| + conditional formats, charts, basic pivots, measured workbook-based calc coverage. |
| +7. Slides: complete existing editor/live-sync/assets branch after coordination; |
| + PDF export and thumbnails, PPTX compatibility, comments/history, offline |
| + presenting, templates/brand assets, Calendar/Meet presentation integration. |
| +8. Calendar: attendees/invitations/RSVP/update/cancel, free/busy/find-time, |
| + working hours, external subscriptions, timezone/recurrence interoperability, |
| + mobile reminders, search, localisation/browser gaps, agenda/Meet links. |
| +9. Memoria: real sibling S1-S3 producers and conformance, restore reconciliation, |
| + source freshness/unavailable states, deletion/revocation, filters/navigation; |
| + assistant only after source correctness, opt-in/cost controls, S6 numeric |
| + grounding and provenance-preserving save to Docs. |
| +10. Files: verify Slopbox current durability and production state; suite identity, |
| + uploads/downloads, folder/project organisation, previews, search, versions, |
| + trash, external shares, cross-app attachment workflows under its trust model. |
| +11. Mail: verify Keymail current state, suite identity/onboarding, domains, |
| + aliases/groups/delegation as needed, Calendar invites, complete migration and |
| + delivery checks. Do not weaken client-held encryption for suite indexing. |
| +12. Meet: create/continue app only after locating existing session decisions; |
| + 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, |
| + 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 |
| + internal links, resumable/deduplicated imports, full useful export; fidelity |
| + corpus with explicitly approved sample data. |
| +15. Proposed additions in accepted assessment: Forms to Sheets with validation, |
| + permissions/abuse controls/notifications/export; assigned actions on comments |
| + and meeting notes. No separate chat product in this queue. |
| +16. Release validation: identity/content/key/access restore drill, support/incident |
| + mechanisms, accessibility/mobile/browser checks, cold-start/save/search/import |
| + performance and capacity/cost limits. Real-team pilot remains external |
| + validation, not something an agent fabricates through synthetic tests. |
| + |
| +## Cross-repository dependencies |
| + |
| +- Home assertion integration and roster are separate checkpoints. Do not broaden |
| + access merely to make a sign-in demonstration work. |
| +- Memoria sibling APIs can progress before Home. The suite module and producer |
| + contracts must be validated against current code rather than stale README claims. |
| +- Existing Slides and media-platform Claude sessions are blocked/idle; read their |
| + Amadan records before taking ownership. Do not restart unrelated sessions. |
| +- Meet stage 4a proceeds independently of image/video transforms; stage 4b is |
| + required for group-call production evidence. TLS-only-network gap is explicit. |
| +- New user-facing copy remains subject to local copy-review instructions unless |
| + Paul changes that requirement; prepare concrete reviews and continue backend work. |
| +- A proposed feature that conflicts with an attributed ruling requires a recorded |
| + decision, not silent redesign. Select existing permitted behaviour when possible. |
| + |
| +## Completion evidence per branch |
| + |
| +Amadan task and discussion; base and candidate SHA; Fable model/verdict/findings; |
| +local tests; actual CI verdict at tip; canary process SHA and browser workflow; |
| +merged SHA; shared deployment process SHA; rollback compatibility; task state. |
| + |
| +## Session limits |
| + |
| +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. |