Co-activation testing, new ways, vocabulary tuning#31
Merged
Conversation
, #29) Co-activation test infrastructure (#27): - Test harness supports array expected values for multi-way fixtures - New eval_scorer function with FULL/PARTIAL/MISS result types - 6 co-activation fixtures covering delivery, code, and architecture overlaps - Integration tests support comma-separated expected way IDs New ways (#28): - architecture/threat-modeling: STRIDE analysis, trust boundaries, attack surfaces - docs/standards: team norms, coding conventions, accessibility - Expanded design way vocabulary with RFC/proposal terms Vocabulary tuning (#29): - Fixed debugging description cross-talk ("errors" → "failures") - Removed generic "risk" from threat-modeling vocabulary (caused FP) - Removed generic "standard" from standards vocabulary (caused FP) - Added 2 new negative controls for the new ways - 0 FP maintained across 70 fixture tests and 34 integration tests
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
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.
Summary
Addresses #27, #28, #29 in a single branch. The three issues are tightly coupled — co-activation testing validates the new ways, and vocabulary tuning validates both.
architecture/threat-modeling(STRIDE, trust boundaries) anddocs/standards(team norms, conventions). Expandedarchitecture/designvocabulary with RFC/proposal terms.Test Results
Fixture tests (70 prompts, 20-way corpus):
Integration tests (34 prompts, real way files):
Test plan
bash tools/way-match/test-harness.sh --bm25-only→ 63/70, 0 FPbash tools/way-match/test-integration.sh→ 28/34, 0 FP