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
{{ message }}
Repository navigation
P8.1 proof of concept: witness timekeeping in the core id app #1827
Implementation follow-up to #802 (branch A, scoped as a proof of concept by Drew's 2026-10-28 ruling). Gated on the witness protocol design issue #1825 — build to that accepted design, not to this sketch, where they differ.
Scope (per the owner's direction recorded on #802)
Witness capability built into the core id app: a witness-only mode, and a flag enabling timekeeping alongside other functions (server mode may default it on).
The witness emits per-second signed ticks (time + signature under its own key).
Proof demos end to end: an event proven to have occurred at-or-after a tick it embeds, and a record proven to have occurred at-or-before a witness countersigning.
Causal/order validity remains the merge backbone — this PoC adds the time layer beside it and changes no merge behavior.
Acceptance criteria
An id server runs in witness-only mode and publishes verifiable signed ticks.
A second node with timekeeping enabled produces both proofs (not-before, not-after) and a third node verifies them, in a test.
With the flag off, the app behaves exactly as today.
Activity
developing-today commentedon Oct 28, 2026
CODE-757
dezren39 commentedon Oct 28, 2026
Intake review
Fleet monitor intake pass (protocol §5), 2026-10-28.
docs(id): record permanent Phase 8 boundary for P8.1 time and witness…
dezren39 commentedon Nov 3, 2026
🤖 Agent note · done