Teams Todo: SQLite implementation plan

Status: the completed SQLite/review UI now uses real direct-origin FIPS. Simulation code/UI is removed; its old databases are retained unopened. Real state starts in local.sqlite and network.sqlite, bound to the actual FIPS identity. Every received event still needs individual acceptance.

Active FIPS transition (supersedes simulation retention below)

The older checked simulation phases below are historical implementation evidence. Global membership revisions, shared resets and deletion/hierarchy merge remain unfinished. The invitation slice below supersedes the original manual board-ID onboarding.

Active invitation slice

The owner approved replacing manual board-ID exchange with Share → paired-node selection → delivered invitation in the recipient's list → Accept & join / Decline.

Pinned bounds: invitation metadata only, 4 KiB UTF-8 body; 7-day maximum expiry; 32 KiB encoded envelope; 512-byte frames; 128 fragments; 8 incomplete transfers (2 per sender); 60-second reassembly lifetime; 2 concurrent transfers; 3 fragment attempts / 3-second feedback deadline; 8 durable retry attempts with exponential backoff capped at one hour. At most 128 live invitations per app/local identity, 16 per remote/app, 1,024 retained records per local identity; terminal records retain 30 days after expiry before pruning. Sender/recipient keys and UUID pin each offer; receipt/status processing never approves access. Completed owner decisions are idempotent and cannot restore a later revoked grant.

Active automatic delivery slice

Approved UX: explicit Send releases local work; recipients automatically receive released events into Incoming and views refresh automatically. Accept/resolve/decline remain explicit, including board creation and resolution context.

Bounds: at most 128 queued jobs, two automatic jobs at once, four pages per catch-up turn with the existing 20-event / 512 KiB page limits. Backoff is five seconds to five minutes. Fifteen-second rotating reconciliation recovers missed hints; app UI refresh is five seconds. No automatic publication, grant approval or event acceptance.

Update modal save fix

Reported: Save cleared title/details without events or changes after refresh. Source reproduction: web execution's display input loses scalar field boundaries; Teams Todo re-parsed it as CLI tokens, rejecting multiword title/details before save. The shared form renderer also reset persistent forms immediately on submission.

Current domain decisions

Completed removal of the initial runtime

Historical initial evidence remains in the archived plan, archived architecture and deployed investigation. Their checked items describe the old scope, not current simulation/transport verification. No old runtime or data is retained.

P1 — settle the real UI with separate peer databases

P1b — personal ordering and winner reconfirmation

P1c — winner-first display and task details editor

R0 — finish semantic and authorization policies

R1 — persistence, reconstruction and history

P2 / R2 — real FIPS integration

R3 — full review, merge and optional agreement

R4 — owner setup and direct invitations

R5 / R6 — presentation, diagnostics and reset

R7 — verification and release handoff

Do not add/run automated test suites without an explicit request. Interactive simulation and narrow one-off verification are distinct from adding a new testing framework.