You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add durable audit provenance for Guided Setup analysis and acceptance #184
Follow-up to #175 and PR #182. Durable auditability was explicitly deferred from PR #182; this work must remain separate and must not widen that PR or change its immutable acceptance boundary. Define durable, verifiable records linking proposal analysis and source/binding lineage to explicit acceptance. Capture the proposal/candidate identity, source and binding revisions, scoped/ALL/unbound binding decisions, analysis/review outcome, explicit acknowledgement, and prior/result accepted-generation identities or hashes. Proposal analysis must remain read-only with respect to accepted state. Do not retain raw source payloads or secret-bearing/tokenized URLs. Acceptance criteria: a fresh disposable analysis with two playlists and three guides (News→News, Sports→Sports, one unbound) reports 2 exact matches, 0 review, 0 unmatched playlists, and 1 unbound guide without changing accepted state; explicit acknowledgement creates a correlated acceptance record; restart/recovery preserves record integrity; no unacknowledged analysis is represented as accepted.
Done and merged on main (Milestone 1). Four PRs: #266 (audit record writer, reader and schema guided-setup/audit/v1), #267 (acceptance writes the record after publish; response gains Audit = RECORDED or NOT_RECORDED; an audit failure never blocks or rolls back acceptance), #268 (single-source v1 acceptance test), #269 (developer guide section).
What it does: one hashes-only record per accepted generation under state\guided-setup-audit, never replaced; reader reports AUDIT_OK, AUDIT_MISSING, AUDIT_INVALID or AUDIT_MISMATCH and never repairs or changes accepted state; analysis never writes records. Frozen contracts and accepted-state code untouched.
Tested (pwsh 7, Pester): audit, web server, enrollment and schema tests all passed with 0 failures at each PR. Not tested: Windows PowerShell 5.1, GUI tests, the full suite outside CI. Hosted checks (quality-gates, secret-scan) passed on each PR before merge.
Activity
Add durable audit record writer and reader for Guided Setup (#184 sli…
Record an audit entry when Guided Setup is accepted (#184 slice 2) (#267
Test the single-source Guided Setup acceptance audit (#184) (#268)
Document the Guided Setup acceptance audit record (#184 slice 3) (#269)
Jumpstile commentedon Nov 17, 2026
Done and merged on main (Milestone 1). Four PRs: #266 (audit record writer, reader and schema guided-setup/audit/v1), #267 (acceptance writes the record after publish; response gains Audit = RECORDED or NOT_RECORDED; an audit failure never blocks or rolls back acceptance), #268 (single-source v1 acceptance test), #269 (developer guide section).
What it does: one hashes-only record per accepted generation under state\guided-setup-audit, never replaced; reader reports AUDIT_OK, AUDIT_MISSING, AUDIT_INVALID or AUDIT_MISMATCH and never repairs or changes accepted state; analysis never writes records. Frozen contracts and accepted-state code untouched.
Tested (pwsh 7, Pester): audit, web server, enrollment and schema tests all passed with 0 failures at each PR. Not tested: Windows PowerShell 5.1, GUI tests, the full suite outside CI. Hosted checks (quality-gates, secret-scan) passed on each PR before merge.
https://claude.ai/code/session_01NzHAcjThVoUGWWfXrYWsNh