Campaign: Trusted delivery and evidence chain #83
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#38 Epic 1.1: The delivery record
Ting/Jostoph
#44 Epic 1.2: The evidence chain
Ting/Jostoph
Reference
Ting/Jostoph#83
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Outcome
Make Jostoph's rulings durable and verifiable: one replayable delivery record stream, signed/chained evidence, seal-aware retention, witness/key lifecycle, and telemetry sufficient to audit what the steward knew and ruled.
Existing linked work
First wave
Build the delivery record spine first (#38 and its fact slices), then layer signed/chained evidence (#44/#48/#50) and sealing/witness semantics. Telemetry can proceed in parallel where it does not alter the record contract.
Dependencies / decisions
The design law is already settled: steward state is derivable from the delivery stream. No owner decision blocks the first wave.