You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+30-8Lines changed: 30 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,29 @@ workspace.
37
37
38
38
See [`spec.md`](./spec.md).
39
39
40
-
The design is not production-ready, but it now selects a v1 implementation path to validate: platform EOA/KMS payer, FOC session-key coordinator, hosted coordination, onchain request/object/usage/receipt state, and a Token Host Builder-first scaffold for the generated app, admin/read surfaces, upload adapters, manifests, and sponsored transaction wiring. The workspace includes a local registry artifact/read model, a dev-only upload spine test that exercises request, start, deterministic mocked receipt finalization, object reads, usage reads, and log projection, plus read-only admin/reconciliation projections for object, usage, dataset, provider, coordinator, and mismatch views. The next admin/dashboard buildout targets direct onchain registry pagination: list/count views enumerate objects, accounts, coordinators, relayers, and dataset keys, while detail views fetch the current contract state. Event projections remain audit/fixture/fallback inputs rather than the current-state dashboard source of truth. A partial Phase 0 Calibration run has deployed and verified the registry bytecode on chain `314159`; see [`docs/phase0-calibration-report.md`](./docs/phase0-calibration-report.md). The full FOC/Synapse/session-key compatibility matrix remains open, so future payment and coordinator modes remain compatibility-gated by Phase 0 evidence. The current security and operations boundary is captured in [`docs/production-hardening-runbook.md`](./docs/production-hardening-runbook.md).
40
+
The design is not production-ready, but it now selects a v1 implementation path
41
+
to validate: platform EOA/KMS payer, FOC session-key coordinator, hosted
42
+
coordination, onchain request/object/usage/receipt state, and a Token Host
43
+
Builder-first scaffold for the generated app, admin/read surfaces, upload
44
+
adapters, manifests, and sponsored transaction wiring. The workspace includes a
45
+
local registry artifact/read model, a dev-only upload spine test that exercises
0 commit comments