Define the canonical lifecycle audit envelope #104
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
Reference
Ting/Jostoph#104
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?
Objective
Define the normative, non-secret lifecycle event envelope shared by OpenBao, Vedanta, Kanidm integration, the Forge adapter, and Jostoph.
Scope
Specify event kinds, emitter identity, correlation IDs, generations, timestamps, outcomes, reason codes, retryability, provenance, and forbidden fields. This leaf changes the contract and fixtures, not the ingest service.
Acceptance criteria
Spec Delta
The former ingest-and-correlation issue is narrowed to the shared envelope contract. Implementation is split into #106-#108.
OpenSpec
OpenSpec 103
Ingest lifecycle events into an independent correlation chainto Define the canonical lifecycle audit envelopeClosed under audit 2026-09-19/20, G13. Merged PR#120 (merged 2026-09-06) delivers the canonical lifecycle audit envelope for this record. Residual D3 and the unrun nix flake check are split to successor issue #125 (#125): Residue of Session #103: D3 decision + nix flake check (audit G13).