FIPS: App Access, Binary Messaging and Connection Recovery

Status: F1–F3 code implemented and locally checked; authenticated UI and deployed network acceptance remain pending. The user authorized implementing the phases together. The initial implementation did not perform agent commits, publication or Git hook execution. The owner has since committed the implementation and begun deployed acceptance.

The owner has now approved the revision below: authenticated direct-origin delivery, a real member chooser, integrated owner create/join grants and bounded direct app invitations. The stored exact-scope chooser, paired-only pre-grant invitations, durable delivery/ decision state and owner Accept & join are now implemented and locally checked. Close returns to the app with a scoped refresh. Deployed authenticated onboarding acceptance remains open. See wire/ownership/bounds.

See architecture decisions, core contracts, Teams Todo and the earlier transport progress record.

First deployed consumer feedback

The Teams Todo owner reported an empty Add grant form and raw validation errors. Source inspection confirms this path starts with empty peer/topic arrays and no protocol, rather than a board-scoped stored request. The local saved Teams Todo scope has no grants/requests and records permission denial. A real owner peer chooser, actionable setup state and readable grant validation remain UX gaps; the current management view is not an implemented picker. See the consumer investigation and recommendations. No grants were changed, and successful post-approval exchange is still unverified.

Approved revision — owner setup and app invitations

Contracts are owned by core C3. Consumer integration is owned by Teams Todo R0–R7. Implement after precise envelopes/owner handoffs are pinned. No compatibility layer is required for this research-stage v1 change.

Authenticated origin and named owner selection

The SQLite/event decision defers the earlier per-entity signature and generic node-signing proposal. Apps can trust direct-origin FIPS delivery and persist that provenance; it is not independently verifiable authorship after arbitrary forwarding.

Integrated exact-scope grants

Bounded pre-grant invitation carrier

Diagnostics and verification

Exit: paired owners can complete app setup with contextual create/join approval, while normal app data remains grant-gated. FIPS owns authenticated carriage/policy; the consumer still owns working state, publication, membership and durable receipts.

F1 — soft grants and selective protocol routing

Local checks: scope/union/denial, management parsing/render schemas, stored request isolation/approval and batch behavior, protocol collision/provider disappearance.

F2 — bounded text and binary P2P messages

Wire format and operational limits

magic "AWFP" (4 bytes)
version 1 (u8), kind 0=text / 1=binary (u8)
protocol length (u16), topic length (u16), payload length (u32)
UTF-8 protocol, UTF-8 topic, unchanged payload bytes

Integers are big-endian. Protocol/topic encoded lengths are capped at 128/256 bytes; payload is 512 bytes; the largest frame is 910 bytes, conservatively below the 1,200-byte FSP path budget. get-limits advertises 8 concurrent sends and 50,000ms send timeout. Apps must chunk larger data using these advertised limits. Send completion is not proof of remote application acceptance or persistence.

Local checks: frame/schema validity, binary byte preservation, malformed/oversized input, policy scope and bounded operation paths. Root native/JSON binary checks pass.

F3 — health and recovery

Local checks include overlapping-publication behavior and bounded ownership/ notification paths. They do not establish real outage recovery.

Current limitations and later work

Verification / publication

No automated tests were added/run, no live application payload was published by the agent, and no authenticated browser session was assumed. Future checks should target failures/new changes rather than repeatedly rerun already-passing scenarios.