Repository navigation
id phase-8: P8.1 time and witnesses is deferred with no tracking issue #802
Description
Finding
P8.1 (time and witnesses, task 09) is explicitly deferred in the phase record, but the deferral has no GitHub issue, so the remaining work can silently drop out of view.
Evidence
doc/2026-10-11T11-08-42Z_design_remaining_work/plan-phases.md§12 Phase 8: "P8.1 Time and witnesses (task 09, deferred)."- Phase 8 record
doc/2026-10-13T23-44-27Z_phase_8_open_design_items/...md: "P8.1 time and witnesses (task 09, deferred; causal validity only)." - The design exists at
doc/2026-10-11T11-08-42Z_design_remaining_work/task-09-time-and-witnesses.md.
Why it matters
Time-based validity and witness attestations are the one phase-8 item whose design is written but whose implementation is deferred with no issue carrying it. Phase 11/12 do not cover it (they are foundations/flexibility, not time/witness validity).
Suggested scope
Either reopen P8.1 as planned scope (implement time validity and witness attestations per task 09) or record an explicit decision that causal validity only is the permanent scope and close this.
Acceptance criteria
- A recorded decision exists: either P8.1 is reopened as planned scope (implement time validity and witness attestations per
task-09-time-and-witnesses.md), or causal-validity-only is recorded as the permanent scope in the phase record. - If reopened: implementation issues are filed for the task-09 design and this tracking issue links them.
- If closed as permanent-scope: the phase-8 record is updated so no future audit re-files this gap.
Activity
dezren39 commentedon Oct 26, 2026
Intake review
Related: Design at
doc/2026-10-11T11-08-42Z_design_remaining_work/task-09-time-and-witnesses.md; filed in the phases 0–10 review batch (PR #804). No merged PR resolves this (verified 2026-10-26).Notes: P8.1 is the one phase-8 item whose design is written but whose implementation is deferred with (until this batch) no tracking issue; phases 11/12 do not cover time/witness validity. The first acceptance step is a decision, not code — hence priority low / effort l for the full scope. Acceptance criteria appended by this intake pass; original body preserved verbatim above them.
Risks: Witness/time validity is foundational if later phases assume it; leaving the decision unrecorded is the failure this issue exists to prevent.
Suggested approach: Drew/owner records the scope decision in the phase record; if reopened, file implementation issues from the task-09 design in the same pass.
dezren39 commentedon Oct 28, 2026
🤖 Agent note · picked up
dezren39 commentedon Oct 28, 2026
🤖 Agent note · escalated
e561ab58ff76ea8e84f2b9a1f108770ebe44a734doc/2026-10-11T11-08-42Z_design_remaining_work/task-09-time-and-witnesses.mdTriage verdict: CONFIRMED — and the remaining step is an owner decision
Evidence at current HEAD (all checked fresh this run, not from the issue text alone):
witnessacross the repo returns only docs/research (the task-09 design, the §10 research findings, the design review), an unrelated cluster roadmap entry, and an ed25519 research dump. No source file implements time validity or witness attestations.task-09-time-and-witnesses.mdline 3: "Status: Deferred, as the owner decided. The design keeps causal order as the only order used for validity." Its goal line: "Later, give events a provable time, without making time decide validity. Claimed time stays display-only until this task lands."plan-phases.md§12: "P8.1 Time and witnesses (task 09, deferred)"; the phase-8 record (doc/2026-10-13T23-44-27Z_phase_8_open_design_items/) lists P8.1 asdeferred, "causal validity only (task 09)". Neither records causal-validity-only as the permanent scope, so a future audit would re-file this exact gap.Why this is escalated instead of routed
The issue's acceptance criteria offer exactly two branches, and choosing between them is a product/scope decision, not an engineering one:
My read / recommendation: (B), unless provable event time has become a product need since the deferral — nothing on current main suggests it has (claimed time is still display-only by design, and no downstream phase depends on witnessed time). If Drew picks (A), I will file the scoped implementation issues from task 09 and link them here; if (B), the docs update + close is a trivial follow-up.
Until then: task 2240 is blocked as
escalated-to-user; this issue stays open as the P8.1 tracking issue.16 remaining items
dezren39 commentedon Nov 3, 2026
agent-note:v1 — state: triaged (task 2240, OpenChamber scheduled lane)
dezren39 commentedon Nov 3, 2026
🤖 Agent note · picked up
docs(id): record permanent Phase 8 boundary for P8.1 time and witness…
dezren39 commentedon Nov 3, 2026
🤖 Agent note · done
doc/2026-10-13T23-44-27Z_phase_8_open_design_items/2026-10-13T23-44-27Z_phase_8_open_design_items.md) and the phased plan (doc/2026-10-11T11-08-42Z_design_remaining_work/plan-phases.md) now state that P8.1 time and witnesses is not reopened and causal-validity-only is the permanent Phase 8 scope, citing the 2026-11-03 owner ruling (id phase-8: P8.1 time and witnesses is deferred with no tracking issue #802 (comment)). Issue P8.1 time & witnesses: witness protocol design (task-09 + owner's 2026-10-28 direction) #1825 and issue P8.1 proof of concept: witness timekeeping in the core id app #1827 are closed as superseded in the same pass. No time/witness behavior was implemented.