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
- Enable FIPS and Teams Todo. Pair the participating instances through
/fips. - Open
/teams-todo listand create a board. - 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.
- On the other instance,
/teams-todo listshows 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. - 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.
- 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
- Send updates (N) assigns durable per-board publication positions to your own unsent events and announces the new release to joined peers. They fetch it into Incoming automatically, without clicking Sync. Send completion is not durable remote receipt or acceptance. Unsent edits remain private.
- Automatic catch-up uses 20-event / 512 KiB pages, up to four pages per turn, then yields fairly and continues until caught up. Two workers and 128 queued jobs bound delivery work; failures retry with five-second to five-minute backoff. Manual Sync and automatic pulls share origin/board locks so they cannot race receipt cursors.
- Durable stream cursors advance with the inbox commit, independently of review. A receipt acknowledgement follows that commit. Startup/reconnect and rotating 15-second reconciliation recover missed release announcements and resume from the durable cursor. Accepted third-party history is never forwarded.
- List/board views automatically refresh every five seconds while visible/idle. The list shows incoming-review counts; an open board shows Incoming directly. The shared renderer pauses refresh while editing a field, preserving drafts. Receiving status replaces the routine Sync button. ⋮ → Sync now remains a manual check/retry. FIPS sync status shows checked times, receipt positions and errors. Zero known updates is not proof that an offline origin has no changes.
- Local shared edits and Send first Sync joined/authorized origins. Pending or declined invitation destinations are not data-sync targets; Send waits for an instance to join rather than timing out on setup fragments. Pending reviews or remaining pages block them. An unreachable authorized origin also blocks preflight; existing local work remains intact. Unshared boards need no remote check. Personal ordering/winner choices stay usable independently of semantic review. Joining an unreleased board says Waiting for the author to Send updates rather than asking you to accept a proposal that has not arrived.
- Incoming rows have contextual summaries and ✓ / ✗ controls. Acceptance writes the event and projection atomically; decline changes only the inbox. Conflicting title/details/status edits require an explicit resolution. A received resolution's missing context must be individually selected, never accepted implicitly.
- Delete/edit and hierarchy conflicts remain blocked. Causal links, rather than timestamps or arrival order, determine compatible edits and explicit merge needs.
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
list,new <title>,show <board>: local boards, shared topics and incoming review.share <board>: share or join an exact board topic through FIPS owner access review.decline-invite <invitation>/retry-invite <invitation>: local invitation decision and explicit delivery/status retry. Acceptance is exclusively an FIPS owner action.add <board> <title> [--parent <todo>],title,status,done,undone,delete: local semantic changes. Delete live children before deleting their parent.update <board> <todo>/details <board> <todo>: title/details editor.update … --save --title <title> [--details <text>] [--revision <hash>]saves the complete form; omitted/empty details clears them.send <board>,sync <board>,accept|decline <board> <event>,resolve <board> <event> [<value>] --heads <head> … [--clear]: publication/review.accept … --reviewed <event> …explicitly selects received resolution context.syncis a manual delivery check/retry; routine receipt is automatic after Send.order <board> --items <root> … --revision <hash>andwinner <board> <parent> <child> --snapshot <hash>: personal priorities.help: complete registered command summary.
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
data/local.sqlite: local/accepted boards, tasks, events and own publications.data/network.sqlite: separate incoming decisions, stream cursors, durable receipt evidence and private priorities. Both stores use WAL/FULL durability.- Generic invitation envelopes/queues/decisions live in FIPS's
fips_app_invitationstable, outside accepted app history. Existing member-selection rows migrate without losing grants or pairing. FIPS uses WAL/FULL for durable invitation receipts. - The network store is bound to the actual FIPS identity. A different key cannot silently reuse it; restore the original identity before continuing with its boards.
- The former
entities.sqlite,peer-b.sqlite,peer-c.sqlite,transport.sqliteare retained on disk unopened. Fixture history is not reattributed or published. This owner-approved transition starts with fresh real-identity state. - Stream identity changes/rollback/gaps fail closed and preserve received state. Distributed stream reset/recovery and board removal remain future work.
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.