Repository navigation
id: design: writer-set + view-projection spec for pkgs/id — representation, set-change semantics, discovery query (from #2030) #2238
Description
From the #2030 investigation (trust/visibility model)
Investigation #2030 (queue task 3346, result posted on that issue 2026-10-29) verified that pkgs/id ingest is validity-only (src/event_store/ingest.rs: signature/encoding/chain refusals only; "the store keeps it either way" — src/event_store/claims.rs) and specified the missing layer: per-view writer sets. This issue is the design spec for that buildable piece. It is a spec, not a build order — no permanent feature is built on the #2030 investigation without a review round (program rule, epic #2056).
Spec to produce (doc in pkgs/id/doc/ per repo convention, linked from this issue)
- Writer-set object format — a signed, versioned object owned by the view owner: entries = explicit IDs | one-level group references (via
src/groups/) |publicsentinel; optional per-topic scoping; view-level exclusion entries (exclude one writer admitted via a group reference). - Set-change semantics — prospective by default; "include history" as an explicit add-time choice; removal stops future counting;
rescindas an explicit, visible set-version event; every computed view names (set version, frontier). - View projection — author-indexed projection over the event store so view cost is proportional to writer-set size, not store size; counted vs uncounted strictly separated; one-off "count this claim" exceptions recorded at view level.
- Discovery query — subject/topic-first lookup returning counted + uncounted claims, uncounted showing author, signature status, and why-not-counted; author-clustering of results (Sybil-flood readability, id: investigate: trust/visibility model — servers accept all signed objects; views count only allowed writers #2030 abuse case 2).
- Storage tiering interface — counted = hot/permanent; uncounted = cold with a published expiry unless pinned/counted; quota values themselves come from id: investigate: comms abuse controls — blocks, rate limits, and per-counterparty budgets #2032 (do not invent separate numbers here).
Acceptance criteria
- Spec doc landed in
pkgs/id/doc/and linked from this issue, covering all five points above - Each id: investigate: trust/visibility model — servers accept all signed objects; views count only allowed writers #2030 abuse case (1–7) is traced to a spec mechanism or an explicitly accepted residual risk
- Open questions the spec cannot settle are listed for the ID core design id: design: ID core build v1 — app model + capability system, enough to start app examples #2028 rather than decided silently
- Follow-on implementation work, if any, is filed as its own issue(s) — this issue delivers the spec only
Program: ID platform expansion, epic #2056. Parent investigation: #2030. Related: #2028 (ID core design), #2031 (first app — did-it tracker), #2032 (abuse controls / budgets).
Activity
developing-today commentedon Oct 29, 2026
CODE-1107
dezren39 commentedon Oct 30, 2026
Agent note — picked up (queue task 3395, openchamber scheduled lane)
Claimed 2026-10-30 ~11:50Z for revalidation. Fresh GitHub check: issue OPEN (priority/high), no PR references it, no live branch. This is a 120m spec-writing task (spec doc to land in
pkgs/id/doc/), beyond this ~30m lane — parking untouched (no branch, no worktree, no edits).dezren39 commentedon Oct 30, 2026
Agent note — parked untouched (needs a full-budget shift)
doc/content underpkgs/id/on origin/main. Deliverable is a landed spec doc (five points: writer-set format, set-change semantics, author-indexed view projection, discovery query, storage tiering) plus id: investigate: trust/visibility model — servers accept all signed objects; views count only allowed writers #2030 abuse-case tracing and unsettleable questions routed to id: design: ID core build v1 — app model + capability system, enough to start app examples #2028 — a single design-writing shift, not a short-lane slice.queue/queued+status/needs-triage, so this pass sets the parked end-state directly (queue/parked+status/parked+work/assigned, queued/needs-triage removed).ghhosts.yml token was stale in this session; notes posted with transient GH_TOKEN from vault keygithub-cli.hosts-yml.75 remaining items
dezren39 commentedon Oct 30, 2026
🤖 Agent note · parked
chatgpt-codex-connector commentedon Oct 30, 2026
To use Codex here, create an environment for this repo.
Merge pull request #2739 from developing-today/queue/3395-2238-writer…
dezren39 commentedon Oct 30, 2026
agent-note:v1 — done, queue task 3395 (repo-worker-code, openchamber-scheduled-lane, 2026-10-30).
PR #2739 merged as 898fcdc (now origin/main HEAD; merge state CLEAN; Codex round-13 re-review of 882b83d: no findings). Spec doc landed at doc/2026-10-30T13-15-00Z_design_id_writer_set_view_projection/ (1729 lines), reachable via the pkgs/id/doc symlink. Issue auto-closed. In-flight labels removed.