Initial MVP evidence and superseded implementation plan
ARCHIVED: this file preserves original implementation evidence and the earlier signed-entity/xitdb revision proposal. Its pending checklists are not active work. The owner subsequently chose SQLite with explicit change events, direct FIPS attribution and dependency-aware incoming review. The current authoritative plan is implementation-plan.md. No historical checkmark establishes completion of the new design. Relative links below remain for historical context.
Status: initial MVP implemented and locally checked; the owner approved the revised
product/architecture below after first deployed review. Revision work is not yet
implemented. Successful deployed sync remains unverified. App alias:
teams-todo, title Teams Todo, protocol teams-todo.sync.v1. Earlier notes
called it todo-teams; use teams-todo consistently for the new scaffold.
Dependencies: core C3 contracts, then FIPS signing/owner-setup/invitation revision, building on the existing F1–F3 baseline. The agreed boundaries and soft-grant policy are in the architecture.
This plan moved into the independent app repository after scaffolding. The core docs retain a short entry point. All checked boxes below describe code/local checks, not authenticated-browser or real-network verification. R0–R7 below are the active execution plan. The original M0–M5 record is retained as historical implementation evidence; its draft-every-edit, unsigned events, automatic publication and manual descriptor/grant setup policies are superseded, not requirements for new work.
First deployed review
See UX and sync investigation for the user's reported setup difficulties, source findings, read-only local state evidence and proposed improvements. The inspected local board has no Teams Todo grants/requests and a saved permission-denial error; no app contact/durable sync is recorded. This is a confirmed local blocker, not proof of a binary transport/storage defect. VPS state and actual post-approval replication remain unverified. The owner subsequently approved node signatures, manual publication, integrated create/join grants, direct invitations, separate board/task views, diagnostics and explicit reset tools. Only the shortcut icon correction has been implemented from this review so far.
Approved product decisions
- Ordinary authenticated owner edits save locally immediately; no draft/accept cycle per add, title edit, checkbox toggle or task deletion. Keep existing automation review semantics where applicable; do not add AI features in this increment.
- Send updates explicitly publishes the captured local changes. Incoming published history and retries/catch-up of already-published history are automatic. Startup, reconnect, Sync now and remote pulls must never publish working changes.
- Use the existing FIPS node key for signed application events/configuration. No bunker, human signing prompt, new app key or private-key copy. Display human names via verified node-owner bindings; distinguish creator/editor from assignment.
- Use NIP-01 event IDs/signatures and one immutable signed event per mutation (event sourcing). Teams Todo owns all entity/mutation schemas and interpretation; core/FIPS know only the generic signing/transport envelope. Parent/relationship semantics and task hierarchy are deferred from these initial phases.
- Create & share and Accept & join are authenticated owner approval surfaces that save the required exact local grants as part of setup. No separate manual grant screen in the normal flow, and no background app self-approval capability.
- Invitations travel directly between already-paired instances. Receipt alone neither joins a board nor creates grants. Retain manual commands/export/import as administrative fallbacks. No automatic FIPS pairing of unknown members.
listshows boards only.show <board>has a board header outside the task tree; task rows follow personal Todo's compact interaction/layout patterns.- UI shows local save, unsent changes, peer receipt/setup and readable activity. Technical IDs, transfer details and error stages belong in diagnostics/logs.
- Explicit clear/remove/fresh/reset operations support repeatable acceptance without rewriting a known replicated history or replacing FIPS identity/pairing.
Execution order and gates
R0 pins the contracts/storage boundary; R1 depends on the core/FIPS signing work; R2 builds the publication boundary on signed data. R3 depends on FIPS owner setup and invitation transport. R4/R5 integrate the new UI and diagnostics, R6 reset lifecycle, then R7 deployed acceptance. Work on presentation must use the confirmed structure below; propose any substantial departure before coding.
This plan authorizes documentation of the direction, not implementation, publishing, commits, pushes, hooks or automated tests. Future implementation follows explicit user instructions and the existing targeted lint/one-off-check rules.
R0 — pin contracts, state model and reset transition
- Coordinate generic contracts in the core plan and provider work in FIPS.
- Specify canonical signed envelopes, immutable identities, working vs published persistence, invitation lifecycle, owner-approval handoff and structured status before implementing callers. Pin sequence/clock/hash rules, working-to-published change reduction and message budgets; local working IDs must not create gaps or require rewriting an already-published writer sequence.
- Keep
xitdb@0.30.0for published per-board/per-origin histories and tracking replicas; keep local working/outbox/control data outside replicated files. Confirm the library API/commit boundary for the revised slice rather than treating a byte watermark on a live working database as sufficient isolation. - Document a deliberate fresh-data transition for the research-stage schema. No unsigned-event fallback, old invitation bridge or migration layer is required. Preserve current data until the owner explicitly runs a reset/transition.
Exit: a concrete signed schema, staged-publication/crash-recovery design and bounded onboarding contracts, with unresolved details recorded before code depends on them.
R1 — independently verifiable node-authored data
Owning files: model.ts, storage.ts, app.ts; FIPS owns the signing key/service.
- Store each mutation as a NIP-01 signed event. Calculate
idas lowercase hex SHA-256 of UTF-8JSON.stringify([0, pubkey, created_at, kind, tags, content]), then BIP-340-sign the hash assig. Use publicnostr-toolshelpers where practical; no custom event hash/signature algorithm or Nostr relay requirement. - Teams Todo defines the typed mutation payload (protocol/schema version,
board/task identity, operation/data, originating FIPS node, sequence and logical
clock) and its deterministic JSON encoding into
content, with app-defined signed tags as needed. Pinkindand domain/type/version conventions in R0. Do not put meaningful app fields only at top level: NIP-01 would not sign them. - FIPS signs generic event templates with its existing key and does not interpret
app entity content. Teams Todo verifies fresh received/deserialized events with
the standard hash/signature rules, then validates its payload and app authority.
Treat verified event objects as immutable; do not rely on a cached verification
flag after mutation. Bind 32-byte x-only event
pubkeyto the 33-byte compressed originating/paired FIPS key. A valid transport sender and signed author are separate facts, even while direct-origin policy requires them to match. - Sign board descriptors/membership revisions and app invitations as well as task events. Only the established creator authorizes membership revisions; valid signatures alone do not grant membership or transport access.
- Keep stable task identity distinct from mutation hashes and transport transfer IDs. Preserve signed creation/mutation records in persistence; the materialized task is a projection of potentially different authors, not one creator-signed current snapshot. Cover any independently persisted shared entity by signed source records or a defined signed envelope.
- Retain deterministic logical-clock/author/hash tie-breaks and permanent deletion
tombstones. Signed Unix-second
created_atis for activity/display, not merge authority; check malformed timestamps without assuming synchronized clocks. - Keep parentId, task hierarchy and other app-specific relationship semantics out of the first phases. Only the board/task references necessary for flat task mutation sourcing belong in the initial app schema, never shared core contracts.
- Resolve human labels from verified FIPS owner bindings, with node fallback when unavailable. Do not claim the human signed the edit or introduce assignment ownership. Local aliases remain display data, not cryptographic authorship.
- Validate canonical hashes/signatures, changed fields, wrong author/board, descriptor revision authority, duplicate/conflicting history and attribution after replication. Signing must work without a live remote connection.
Exit: stored shared source data is independently node-verifiable, even outside the connection that delivered it. Human/bunker signatures and forwarded histories remain out of scope; direct-origin replication is retained for this increment.
R2 — immediate local edits, explicit publication
Owning files: app.ts, storage.ts, network.ts, model.ts.
- Replace ordinary owner edit drafts with durable local working changes. Persist their signed records locally and project them with published/received history; display the local unsent count. Define how received changes merge with pending local edits using the same deterministic rules.
- Implement Review changes and Send updates. Capture a bounded set of pending changes, commit it idempotently to the origin's published xitdb log, then notify peers. Later edits remain unsent even if a transfer is in progress.
- Make the review describe exactly what will be shared, allow discarding unsent work and keep intermediate working history local. Pin coalescing/net-change rules in R0, including an unsent create followed by delete, rather than copying the whole local edit audit into a supposedly final/latest publication batch.
- Recover interruption between xitdb commit and local-outbox bookkeeping without duplicate events, lost changes or an unintended release. Show publication failure separately from local-save failure. Publication is durable release eligibility; it does not require all peers online at that moment.
- Serve only published source bytes/cursors/checksums. Audit sync-state/start, chunks, notifications, startup/reconnect, periodic reconciliation and Sync now; none may expose working data. No stopping-notifications-only workaround.
- Automatically receive/retry already-published changes, persist per-peer durable acknowledgements and keep transport success separate from receipt. Rename or clarify Sync now as published-history reconciliation, not implicit publication.
- Verify edit-without-send, peer pull before send, restart before send, offline Send, concurrent later edits during transfer, repeated Send and recovery.
Exit: a user can edit freely while peers cannot retrieve those edits until Send updates. Published history remains immutable; corrections are new events.
R3 — guided create/join and direct invitations
Owning files: app.ts, init.ts, network.ts, storage.ts, definition.ts, view.ts.
- Use the FIPS-owned owner chooser to select named paired instances, including ungranted ones only through this explicit owner surface. Include local creator automatically; do not require typed keys or expose the full roster to ordinary app enumeration. Show unknown/unpaired members as actionable prerequisites.
- Create & share reviews title/members and exact access in readable language, signs/saves the descriptor, saves required local grants through the approved owner workflow, and sends invitations. A local-only board needs no remote grant.
- Persist invitation delivery/acceptance separately from board membership policy. Show invited/awaiting acceptance/joined/declined/expired states; selected keys are not evidence that another instance has accepted or installed the app.
- Receive bounded paired-node invitations through the new bootstrap path; verify creator signature, intended recipient, board and revision. Render a readable inbox preview without auto-joining, auto-installing or auto-granting anything.
- Accept & join explicitly approves the displayed descriptor/members/scope, installs the board and exact local grants, acknowledges acceptance and starts subscriptions/published-history catch-up. Decline does not grant or join.
- Make both workflows retryable across independent app/FIPS databases and network failure: record durable stages, make repeats idempotent, expose incomplete setup, and never report complete when board or grant persistence failed.
- For three members, display and authorize the required pairwise scopes on each instance; prompt for missing local pairings. Creator-signed membership updates that widen access require new explicit owner review, not silent expansion.
- Preserve manual new/members/review/access/export/import fallbacks with useful output and plain-language validation. They must obey the same signatures and owner authority; manual import is not an unsigned bypass.
Exit: paired owners can create and join from the app without copying descriptors, protocol IDs, board IDs or grant JSON. Each owner makes one contextual setup approval.
R4 — boards-only navigation and focused task UI
-
list: board tree only, showing title, small task count, human-readable sharing/ publication summary and visible Open/New/Join/setup actions; no task nesting. -
show: board title/header and back navigation outside the tree; compact tasktreeItemrows with checkbox, title, minimal pending indication and actions. Study personal Todo's list/tree patterns without importing its private code. - Visible contextual Share/Send updates/setup actions, inline add/title controls, human-readable activity and optional member/sharing panels. Task expansion is useful user detail, not an event/log dump. Keep raw IDs and clock/byte fields in explicitly opened technical diagnostics.
- Preserve current board/filter/expansion context on actions and refresh. Separate
list/show renderers and refresh targets instead of always refreshing
list. - Show Created by/Last edited by with friendly owner/instance labels and time; do not equate task creation with assignment ownership or human signing.
- Verify generic tree/form/menu schemas and compact desktop/mobile layouts. Authenticated browser acceptance is user-assisted unless access is confirmed.
Exit: the board is understandable without knowing any ID, and task interaction resembles personal Todo while sharing metadata is available without dominating it.
R5 — truthful status, activity and bounded diagnostics
- Add structured per-board/per-peer setup, subscription and transfer state: local save/unsent, invitation state, local access blocked, connecting, awaiting response, transferring, received commit, remote acknowledgement and failure.
- Replace misleading green/pending defaults with an actionable summary. Stable subscription acceptance survives refresh attempts with explicit freshness; known permission denial is blocked, not forever connecting/pending.
- After owner setup/approval, recheck local grant coverage and resume immediately; retain periodic recovery without resetting readable state on every refresh.
- Separate contact, received durable head and acknowledged published local head. Only claim up-to-date for the verified last exchange; do not infer remote approval, missing board or remote grant denial from silence.
- Emit bounded structured diagnostics with board/peer/transfer correlation, stage, direction, attempt, bytes, duration and typed cause. Surface relevant FIPS provider rejection results. No task bodies, secret keys or raw payloads in normal logs; public identifiers may appear in explicit diagnostics, never secrets.
- Provide compact Activity and explicit Diagnostics/Copy diagnostics views. Record installed versions and enough per-side evidence to locate the first failed stage without requiring full databases or constant timestamp churn.
Exit: UI answers saved/sent/received/blocked/next-action; logs explain failures at the correct layer without claiming a transport write is durable app receipt.
R6 — clear, remove and repeatable fresh-start workflows
- Clear tasks stages signed deletions in the existing board; normal Send updates publishes them. This is shared task deletion, not history truncation.
- Remove local board stops/cancels that board's jobs, transfers, subscription intent and callbacks before removing its local files/control state. Prevent late messages from reinstalling it; joining again requires explicit action.
- Start fresh board uses a new board ID and new logs; never reuse a known writer/log identity with rewritten bytes. Old peers keep their old board.
- Reset Teams Todo data is an explicit owner destructive action with a clear scope summary, stopping app work before removal and returning to onboarding. Preserve FIPS identity/pairings; do not touch other apps or remote copies.
- Offer explicit removal of the relevant local Teams Todo grants/requests through FIPS owner management when resetting permissions too. Show retained grants otherwise; do not silently clear shared/overlapping records or global FIPS data.
- Document a two-instance reset procedure for full create/invite/join/grant acceptance after each release. Record both sides' versions and reset scope.
Exit: repeatable clean setup is available without deleting unrelated data or allowing retained remote histories to repopulate a removed board silently.
R7 — revised acceptance and release handoff
- Two real paired nodes: named create/share → direct invite → accept/join with integrated grants; no manual key/descriptor/grant entry and no silent grants.
- Add/edit/check locally without drafts; prove no peer sees changes before Send, including periodic pulls and restart. Send, verify signatures, durable receipt, readable attribution and identical projected state in both directions.
- Verify macOS/Linux raw-byte exchange; record architecture, Bun/core/plugin/ dependency versions and actual size/latency limits. Existing simulated-peer evidence does not establish the new signed publication behavior.
- Verify duplicate/expired/declined invites, offline delivery retry, unknown members, partial setup failure, grant revocation/reapproval and unrelated app/ board isolation. Replayed acceptance must not recreate revoked grants.
- Verify three direct peers, concurrent published edits/deletes, unsent working changes during remote catch-up, stop/restart, missed hints and partial receipt.
- Exercise clear/local remove/fresh board/app reset and repeat full onboarding on both nodes. Check stale messages cannot restore removed data automatically.
- Review user-facing list/show/access/activity/diagnostics, icon, README/help and retained administrative commands. Targeted lint/type/schema checks and required generation; document existing vendor failures separately.
- Return changes and evidence for owner commit/push/release. Do not publish, configure/run hooks, or add/run automated tests without explicit request.
Historical initial MVP record
The following evidence and M0–M5 checklists describe the original implementation, not completion of R0–R7. Where they conflict with the approved revision above, the revised decisions are authoritative.
Implementation evidence
- Source history: pinned
xitdb@0.30.0per board/writer; SQLite stores local-only board descriptors, drafts, subscriptions and sync status. SQLite is never replicated. - Local Bun 1.4.4 / darwin-x64 checks covered three simulated direct peers, concurrent title/done edits, tombstones, reversed/duplicated chunks, incremental resume and failed full replacement. One scenario used 98 messages with a 512-byte maximum.
- Library replication resumed from committed size 445 to 639 bytes; interrupted transfers retained the prior usable state. Binary header is 21 bytes, leaving up to 491 raw bytes under the current FIPS 512-byte payload limit.
- Limits: 4 MiB / 10,000 events per writer-board log, four incoming transfers, two outgoing transfers, bounded reorder buffers and 120-second transfer deadlines.
- Fixed the list toolbar's missing Import descriptor / Drafts icons using the supported copy/checklist icons; action labels remain available as tooltips.
- Targeted lint, generation and UI/schema checks passed. Root TypeScript checking still reports only the three documented FIPS vendor errors. No automated test suite, live relay publication or authenticated browser check was run.
- Linux/other-architecture file portability, real FIPS messaging, outage/recovery and user-facing board interaction remain acceptance work, not demonstrated results.
- Shortcut icon correction:
webWidget.iconnow referencesicon.svgrather than the generic UI glyph namechecklist. Targeted ESLint, plugin generation and a one-off source/path check passed; the expected asset is/plugin-icons/teams-todo/icon.svg. Deployed UI confirmation remains pending.
Original product slice (superseded where noted)
Mimic the personal Todo interaction style with only:
- A local-first board with a stable random ID and explicit FIPS-node members.
- Flat tasks: add, edit title, mark done/undone, delete. Stable task IDs, no ID reuse.
- Tree/treeItem board/task/details UI, checkboxes and overflow menus, with text command equivalents. Reuse public generic widgets and study Todo's patterns; do not import its private DB/runtime or copy its large renderer wholesale.
- Node selection through the explicit owner peer picker; app-owned grants shown as trees with protocol, peers and exact topic IDs; Review access when missing.
- Persistent local edits, incoming replication, immediate update hints, periodic / reconnect reconciliation and Sync now.
- Three-member direct topology supported, not a hard-coded two-peer demo.
No AI task generation, subtask hierarchy, priority duels, dependencies, attachments,
comments, notifications to humans, role hierarchy, billing, generic sync framework,
automatic peer introductions or routed mesh in this MVP. Paid teams-* apps are a
future product direction, not a licensing implementation prerequisite.
The app owns membership, data validation, subscription state, conflict resolution and optional future Git-style review. None are FIPS/capability responsibilities.
M0 — pin storage and validate the replication slice
xitdb-ts is the first candidate, not an unverified promise. Pin a concrete release /
commit and inspect its documented/source behavior before designing file-level sync.
- Verify package/API and license and local Bun support. Use
the real
replicaState,replicationStart,committedSize,readCommitted,openReplicatedAPIs; note committed-size/checksum/log-ID semantics. - Exercise a tiny single-writer history and a separate read-only tracking replica with interrupted incremental transfer and full-replacement recovery. Use staging for full replacement; preserve the last usable replica on failure.
- Confirm binary chunks can fit provider-advertised payload limits after app framing; synchronous DB work must not monopolize the bot event loop.
- Check logs produced on local macOS and Linux VPS replicate/read correctly; include a different architecture if available, otherwise record it unverified.
- Record findings and fix the storage choice before M2. If feasibility fails, present a scoped alternative; do not silently substitute a different sync model.
Exit: evidence for resumable committed-byte replication and explicit limitations, not a claim that immutable moments automatically provide event sourcing or merge.
M1 — scaffold and local Todo slice
Use the existing helper, inspected at
src/plugin-lifecycle/scaffold.ts:219:
createPluginScaffold({
dmBotRoot: <AppWeaver root>,
alias: "teams-todo",
title: "Teams Todo",
description: "Local-first shared todo boards over FIPS",
coreApiVersion: <current core range>,
createDraftCommands: true,
runGenerator: true,
configureGitHooks: false
})
The helper creates the independent Git repository, adds the local manifest entry and generates registration. This invocation explicitly skipped hook configuration; no hooks were run. It does not publish the app or approve networking. This invocation is complete; do not rerun over the existing plugin directory. Replace template sample behavior rather than exposing scaffold demo tools as app features.
- Load the new plugin's generated instructions; move this owning plan into it.
- Add package metadata/icon and capability declarations: consume peer-network, provide peer-channel protocol handlers; regenerate after declaration changes.
- Implement board registry and flat task events/projection using the M0 choice. Keep durable source events separate from a rebuildable view. Local-only metadata/subscriptions live in the app's DB, never in FIPS SQL.
- Keep per-board/per-writer source files and per-board tracking replicas. A raw file transfer for board A must not include board B, grants, secrets or local subscription/administration metadata.
- Implement add/edit/done/undone/delete and offline list rendering, following existing explicit-owner/draft-accept behavior. AI automation is not needed.
- Build a compact board/task tree with form/menu actions and text equivalents. Show local save independently of any network/sync outcome.
- Implement local access to the app's grant list / explicit Review access flow, displaying all records without editing provider SQL or auto-opening prompts.
- Check local restart persistence and deleted-task behavior; lint/type/generate as required, update README and return the local MVP for user publication.
M2 — board membership and deterministic event model
These are proposed small-MVP policies, not requirements imposed on other apps:
- Board creator manages membership; all accepted members may edit tasks. Store a stable creator node, board ID, exact member FIPS keys and membership revision. Only accept configuration changes authorized by the app's established board policy. An arbitrary peer cannot make itself a member by naming a topic.
- Start with an app-specific, explicitly reviewed board descriptor/invitation exchange among already-paired nodes. It identifies board/protocol/topic/members; it never inserts FIPS peers or grants automatically. Owner selection/review is required on each node. Extra signing or an automatic invitation system is not required for the first app; do not confuse this with signed FIPS pairing codes.
- Missing grants are normal pending state. Request only the board topic and chosen peers, and let the owner approve through FIPS management. Subscription setup waits until both app membership and access are valid.
- Each node writes one identified log per board. Identify events by stable UUID, writer/log ID, writer FIPS key, per-writer sequence and logical clock; include task ID, operation and data. Include protocol/schema version and board ID.
- Persist the event before notifying. Use deterministic per-field ordering by logical clock with stable writer/event tie-breaks, not wall-clock arrival order. Independent title/done edits can merge. Deletion is a persistent tombstone and wins over edits; MVP has no undelete, so task IDs are never reused.
- Retain all source events; no automatic log compaction/reset in the MVP. Detect duplicate IDs/sequence positions with conflicting contents instead of silently replacing known history. Observe received clocks when advancing a local clock.
- The first MVP automatically materializes valid authorized events under this policy. Git-style incoming review/merge/revert is a later app feature; local command drafts are not a remote-review protocol. Surface conflicts/history enough to explain deterministic outcomes rather than promising full review UI now.
Checklist:
- Define/validate board descriptors, membership changes, events and projections.
- Bind direct remote writer histories to their authenticated FIPS source. No third-party forwarding of someone else's logs or unverifiable master authorship.
- Confirm identical projections from different delivery orders, duplicate events and concurrent edits; document the precise tie-break/delete rules.
- Check project permission failures, duplicate names/different FIPS nodes and membership removal. Removing a member stops app subscription authorization and fan-out but leaves owner-managed FIPS grant records untouched.
- Present the concrete MVP merge/membership behavior with checks for user review.
M3 — direct incremental sync over binary messages
Protocol teams-todo.sync.v1; exact topic is the board ID. Every request/response
uses an explicit peer FIPS key and the same protocol/topic grant boundary.
App-owned message families:
| Message | Meaning |
|---|---|
sync-state |
Writer/log identity and current committed replica cursor |
sync-start |
Validated source identity, byte range, transfer ID and size bounds |
sync-chunk |
Transfer ID, expected offset and unchanged source bytes |
sync-complete |
Transfer end; validate and commit the replica |
sync-ack |
Confirm durable committed position, not UI acceptance/merge |
sync-error |
App-protocol failure with bounded diagnostic reason |
Use a small app binary header for chunk identity/offset plus raw xitdb bytes; control messages can use text. This is above FIPS framing, not a second transport.
- Implement origin-writer-only replication: initial full copy and incremental catch-up after the library's actual cursor. Do not use updated_at as a cursor.
- Keep writer/log generation and per-writer heads distinct. Equivalent tasks in two independently built databases do not imply binary identity.
- Bound transfer size, chunk size, concurrent transfers, buffered bytes, timeouts and retries; advertise/obey the FIPS message budget including app headers.
- Persist checkpoints only after durable replica commit. A transport
sentresult does not advance remote durability; resume from validated replica state. - Handle duplicate/out-of-order chunks, timeout, peer restart and interrupted full replacement. Preserve the last good view; never write local edits into a remote replica. Reject a reset/rewrite of known history without defined handling.
- Serialize/coalesce sync per board/writer and rebuild/update the projection from committed histories. No unbounded receive-handler work.
- Add Sync now and separate last-contact, last durable sync, pending edits and app errors. Do not equate connected with synchronized.
- User verifies two-node raw-byte catch-up and offline edits across restart; record exact versions, payload sizes, failures and durability behavior.
M4 — app-owned subscriptions and near-real-time hints
- Define subscribe / subscription-result / unsubscribe / history-changed messages inside the app protocol. They are normal grant-checked P2P sends.
- Persist subscriber and outgoing subscription intent in Teams Todo's own DB, keyed by peer/protocol/topic. Do not create FIPS subscription tables or capability publish/subscribe operations.
- For board members A/B/C, each requests subscriptions to the other two. B only records A after checking current membership and accepting its request. Incoming registration is not implied by physical connection or by A subscribing elsewhere.
- Fan out hints only to accepted, still-authorized member subscribers. One FIPS send means one peer result; aggregate failures in the app without blocking local commits. Do not push data to uninterested or removed members.
- Publish history-changed only after commit, carrying origin-writer change hints. The receiver compares its state and schedules incremental sync, not blind apply.
- Debounce bursts; one sync runs per board/writer and another hint marks it dirty for an additional pass. Prevent subscription restoration and update loops.
- Re-exchange subscriptions and reconcile on connection-change hints/startup. Run bounded periodic reconciliation and keep Sync now so missed hints recover.
- Retain blocked intent after grant removal and show Review access; never open background approval. Unsubscribe/leave does not delete FIPS grants.
- Refresh the board view on persisted updates using existing generic web refresh mechanisms. Near-real-time behavior is measured, not a promised fixed latency.
M5 — three-node acceptance and MVP publication
- User verifies A/B/C subscribe to one board, all pairwise directly paired and granted, and every member receives each origin's new events without duplicates.
- Check concurrent title/done/delete, member addition/removal, one offline node, missed hints, reconnect/restart and Sync now. Compare projected state after all required source writers are reachable again.
- Check missing/narrowed/deleted grants, multiple records, topic isolation and an unrelated installed app. No raw replication of another board's file.
- Check three nodes with the same master where possible: routing/authorization are per FIPS node, not a single matching master. No grant auto-cleanup.
- Record local-save / notification / durable-sync / UI-visible timings separately; ensure transfer chunks don't freeze unrelated bot/web interactions.
- Finish compact tree/menu/forms and text fallbacks, README/help and progress. Run targeted lint/type/schema checks and required plugin generation.
- Return app changes for owner review/push/publication; do not publish automatically.
No automated test suite is added/run unless requested. Narrow in-memory validation and user-assisted deployed scenarios supply initial evidence; authenticated browser automation requires user-confirmed access. Document existing vendor failures separately from new code errors.
Later app work
Git-style incoming change review, shared acceptance/resolution events, selective project roles, retained-history/compaction policy, cross-peer forwarding of writer logs with verifiable original authorship, AI features and paid licensing can follow. Do not equate network forwarding with database-history forwarding.
Progress
- Inspect scaffold helper, personal Todo UX and current networking capabilities.
- Record minimum feature set, proposed merge policy and dependency order.
- M0 local storage feasibility and recorded choice; cross-OS check remains open.
- M1 local app scaffold and task UI.
- M2 membership and event projection implementation; owner review remains open.
- M3 binary replication implementation; real-network check remains open.
- M4 subscriptions and update hints implementation.
- M5 user-assisted three-node acceptance and publication.