F1: One enriched record per delivery #39

Closed
opened 2026-08-12 16:15:24 +00:00 by agent.teyla · 0 comments
Contributor

M1 frontier

In scope

  • Each verified delivery appends one record — payload digest, extracted facts, ruling reference — to a local write-ahead log; durability between emission and shipping is this file's only job.
  • Record schema version, independent of policy schema; refused on mismatch.
  • jostoph replay [--repo R] [--since TAG]: rebuild the fact view from records; the ruling path and jostoph curation read only this view.

Out of scope

  • Any rule reading the facts (Epic 2.1).
  • Signing and chaining (S1) — the record format must not preclude it.

Boundary

  • Facts are extracted only from verified deliveries. If the delivery did not carry it, it is not a fact.
  • Replay is deterministic: same records + same binary + same parameters ⇒ same view, byte for byte. A rule change re-rules history by replay, never by mutation.

Acceptance

  • Replay after restart, after view deletion, and after a rule change yields the documented view each time.
  • A replayed delivery (same delivery_id) appends nothing.

Source: JOSTOPH-BACKLOG.md, Epic 1.1.

`M1` `frontier` **In scope** - Each verified delivery appends one record — payload digest, extracted facts, ruling reference — to a local write-ahead log; durability between emission and shipping is this file's only job. - Record schema version, independent of policy schema; refused on mismatch. - `jostoph replay [--repo R] [--since TAG]`: rebuild the fact view from records; the ruling path and `jostoph curation` read only this view. **Out of scope** - Any rule reading the facts (Epic 2.1). - Signing and chaining (S1) — the record format must not preclude it. **Boundary** - Facts are extracted only from verified deliveries. If the delivery did not carry it, it is not a fact. - Replay is deterministic: same records + same binary + same parameters ⇒ same view, byte for byte. A rule change re-rules history by replay, never by mutation. **Acceptance** - Replay after restart, after view deletion, and after a rule change yields the documented view each time. - A replayed delivery (same `delivery_id`) appends nothing. Source: JOSTOPH-BACKLOG.md, Epic 1.1.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Ting/Jostoph#39
No description provided.