FIPS implementation progress

Status: experimental implementation; local UDP roundtrip exercised, deployment and interoperability verification pending. This record distinguishes existing code from the intended design.

Active next phases

The owner-approved next increment is now the owner-setup and app-invitation revision, coordinated with core C3 and Teams Todo R0–R7. Existing F1–F3 code/local evidence does not establish those new features or successful deployed synchronization.

The app-access and messaging record owns F1 soft grants / protocol routing, F2 binary/text messaging, and F3 health/recovery. Their code is implemented with local checks; real network/UI acceptance remains open. The user authorized completing all implementations together, without a compatibility bridge. See the core record and Teams Todo MVP record.

The numbered phases below are historical progress categories, not the new execution order. Existing checked items remain evidence of their original scope. New app permissions are unsigned, owner-managed DB records; signed FIPS pairing is unchanged. Use protocol/topic terminology for new app messages. Subscriptions, publication fan-out and project membership belong to consumer apps, not FIPS.

Present implementation

Remaining work

Instance identity and web management

Verification: targeted ESLint (--fix), plugin generation and whitespace checks passed. In-memory checks covered legacy migration/idempotence, preserved peer IDs/data/indexes/triggers, multiple same-owner instances, correct UPSERT identity, ambiguous master-only delivery, signed same-master pairing, self-instance and owner-rebinding rejection, one-time completion, alias trimming/validation/rename, alias and seed preservation on re-pairing, web schema/control/action validity and updated removal output. No real database or relay was used. TypeScript reports only the three previously documented vendored Noble/WebRTC errors, with none in the changed plugin code. Deployment/UI and live connectivity remain unverified.

Phase 1 — signed manual pairing (implemented; deployment verification pending)

The ping form's invalid number field kind was corrected to integer after a user-reported save_timeline_form failure. This failure happened before transport execution. Plugin TypeScript checking previously also reported three vendor errors: core identity references Noble's removed ProjectivePoint, and two WebRTC calls pass strings where Noble v2 requires bytes. Those vendor errors remain unresolved. Transport hardening below remains unimplemented.

Phase 2 — bounded and authenticated connection establishment

Phase 3 — application isolation and operations

Connectivity follow-ups

Application-specific sync/merge, storage-engine selection, and bunker-backed application signing remain separate work owned by consumer apps or signing services. They are not transport-plugin exit criteria.