Skip to content

#131: Define impact-validation methodology - #145

Open
justsml wants to merge 2 commits into
mainfrom
dan/issue-131-impact-validation
Open

#131: Define impact-validation methodology#145
justsml wants to merge 2 commits into
mainfrom
dan/issue-131-impact-validation

Conversation

@justsml

@justsml justsml commented Aug 27, 2026

Copy link
Copy Markdown
Owner

Split from the Wayfinder mega PR #137.

Refs #131

Scope

  • Add a deterministic promotion boundary from observations to finding-ready impact evidence.

Review notes

This PR is intentionally ticket-scoped. It does not close the referenced issue unless the issue is already complete; CI provides the final integration check.

@justsml justsml mentioned this pull request Aug 27, 2026
19 tasks
@justsml

justsml commented Aug 27, 2026

Copy link
Copy Markdown
Owner Author

Council of Dans review: repair/defer. Highest-priority gate: Derive any finding-ready transition from durable evidence/authority rather than self-attested booleans and IDs. Feature flags are not a substitute for authority, evidence-integrity, or durability fixes; use typed modes only where they provide a real rollout boundary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant