Skip to content

Refactor responsibility boundaries and tighten dogfood debt - #976

Merged
akcorca merged 4 commits into
mainfrom
refactor/responsibility-boundaries
Aug 6, 2026
Merged

Refactor responsibility boundaries and tighten dogfood debt#976
akcorca merged 4 commits into
mainfrom
refactor/responsibility-boundaries

Conversation

@akcorca

@akcorca akcorca commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • split large evaluator, CLI, configuration, and test-support modules along explicit ownership boundaries
  • introduce a Promise evidence DSL and shared direct-call contract fixtures while keeping behavioral assertions local
  • consolidate only genuinely shared cross-frontend CST lowering policies and use a typed callee-dependency proof query
  • lower the self-dogfood budget to 20 and remove four resolved duplicate-family IDs
  • replay the Type-4 blind-attacker receipt for the new crates tree and synchronize the evidence inventory

Design notes

The reductions in file size come from moving cohesive responsibilities behind named modules or contracts. Language-specific lowering policy and consumer-specific test assertions remain local rather than being hidden behind broad helpers.

Validation

  • cargo test -p nose-frontend — 340 passed
  • cargo test -p nose-normalize — 282 passed
  • cargo test -p nose-semantics — 364 passed
  • focused Promise tests — 29 passed
  • cargo clippy --workspace --all-targets -- -D warnings
  • formatting, docs, file-length, evidence-lifecycle, and soundness gates
  • release-binary self-dogfood — 16 substantial families / budget 20
  • Type-4 blind attacker — 54 exact groups, 0 false merges, 0 canon violations

@akcorca
akcorca merged commit 9fdec12 into main Aug 6, 2026
23 of 24 checks passed
@akcorca
akcorca deleted the refactor/responsibility-boundaries branch August 6, 2026 11:20
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