feat(aidd-dev): rebuild audit around core questions - #518
Draft
alexsoyes wants to merge 3 commits into
Draft
Conversation
Focus audit effort on nine evidence-gated pillars and durable reports.
First pushes evaluate CLI hooks, so worktrees need both dependency sets.
Keep audit validation canonical in the shared contract and validator.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 What & why
Rebuilds the audit skill as a question-led, static-first 80/20 core. It also fixes new worktrees so their first push has the standalone CLI dependencies required by repository hooks.
🛠️ How it works
The core router maps nine evidence-gated pillars to stable numbered report shards. The report contract keeps findings canonical, refreshable, and explicit about disputes and unknowns.
The worktree bootstrap now installs both root and CLI dependency sets, best-effort, because first-push hooks evaluate CLI checks on a new remote branch.
🧪 How to verify
Behavioral audit evaluation and parallel checker orchestration remain deferred to their planned follow-up phases.
✅ I certify