Teams Todo (teams-todo)

Local-first collaborative SQLite boards, hierarchical todos and immutable semantic events over FIPS. Local changes save immediately after shared-board Sync preflight; received changes enter a separate inbox and require individual review.

Create, share and join

  1. Enable FIPS and Teams Todo. Pair the participating instances through /fips.
  2. Open /teams-todo list and create a board.
  3. Open the board's ⋮ → Share… → Select nodes & invite…. The FIPS-owned dialog shows named paired instances, including ungranted nodes, the exact scope and expiry. Select nodes and explicitly Allow & send invitation. Close to return to Teams Todo.
  4. On the other instance, /teams-todo list shows Invitations, with board title and inviting instance. Accept & join opens the stored FIPS scope review; confirm Accept & join, then Close to return to the refreshed app list. Decline dismisses it without granting access. No board-ID copying is required.
  5. The author sees Pending delivery → Delivered → Accepted / Declined, and clicks Send updates after acceptance. The recipient's Incoming inbox receives the released board/tasks automatically; accept board creation, then each wanted change.
  6. Repeat in either direction. With three or more authors, pair and approve every origin directly on each recipient; accepted third-party history is never forwarded.

Invitation delivery works before the recipient has a board grant, over a separate paired-only FIPS onboarding channel. It carries validated board metadata, not tasks or history. Receipt grants nothing. Joining atomically saves the recipient's FIPS grant and invitation decision, but does not accept a board or task. Only the creating instance can send board invitations. Manage existing access handles revocation.

Invitations expire after at most seven days. Queues/decisions survive restart; delivery and decision notifications retry with bounded backoff. Retry delivery / Check join status permit explicit recovery. Replayed invites/approval never restore revoked access. Requests, grants, invitation delivery state, identity and pairing remain FIPS-owned. Global membership/role changes remain future work; authorization is still each owner's exact local node/topic grants. Manual share <board> access setup remains a CLI fallback.

Send, automatic delivery and review

Task controls and personal priorities

Task ⋮ begins with Add child…, Add sibling…, Update. Update and 📝 open the same title/details modal with Save/Close and collapsed creation metadata. Details support 50,000 characters and explicit shared events/clear resolution. Stale or invalid saves retain the typed draft; no-op saves emit no events. Web commands consume the structured payload so multiword titles, multiline details, quotes and option-like text remain intact. Save keeps editor fields visible while pending; incomplete web forms are rejected without clearing saved details. Empty details still explicitly clears the field.

Drag active root handles to order whole subtrees locally. Choose branch winners with Keep/Pick; the champion follows the first active root's confirmed path. Winners display first while other siblings retain relative order. The entire champion path uses the accent color; the leaf has 🏆. Accepted candidate/history/sibling changes request bottom-up reconfirmation. Preferences never become shared semantic events.

Commands

Rendered actions capture --identity <local-fips-key> to reject stale identity contexts. It never switches actors. There are no simulation peers, --peer, peer selector or simulation-reset commands/UI. Task commands do not record timeline entries.

Storage and transition

Verification

Targeted lint, registration generation and diff whitespace checks pass. The Update modal fix also passes the production web build and actual structured-handler checks. Repository TypeScript is blocked by FIPS vendor errors and an unrelated core plugin-publication publicationOptions error. A narrow in-memory capability-boundary check covered own-publication isolation, 20-event pages/cursor continuation, external-only staging, individual acceptance, 512-byte framing, large details, out-of-order/conflicting fragments and revocation. Additional checks covered dropped data and lost-final-ack retransmission, durable receipt evidence, revoked acceptance/local decline and stored chooser/UI contracts. Invitation checks cover pre-grant delivery, no grant/history on receipt, restart retry, unavailable apps, expiry, actual owner-approval transactions, stale/tampered scope, approval replay after revocation, duplicate packets/queues, metadata rejection, stable picker polling, protocol collisions and no data preflight before acceptance. Automatic-delivery checks cover multi-turn catch-up without recipient Sync, missed announcements/restart recovery from serialized store snapshots, unsent isolation, inbox-only delivery/individual board acceptance, queue bounds/coalescing/retry/shutdown and auto-refresh/list incoming-count/receiving-state UI schemas. This does not establish actual network or authenticated browser behavior: owner two/three-instance sharing/restart/recovery and chooser/modal acceptance remain open.

See architecture, implementation progress, schema contracts, command locality, and the superseded simulation record.