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
[Calls] Ship reusable class discovery and re-audit the same frozen 200-class population #498
Priority: P0 foundation / final integration gate. all 200 decisions and reproducible expansion of admission.
Preserve sealed v7. Do not assume fixing a first gate admits a class or that all 200 are executable supported programs.
Implementation scope
Promote the current experiment-only source-surface/domain discovery into reusable tested tooling, reusing Calls catalog/prepare/preflight/cell contracts. First ship the current supported subset and its exact diagnostics; capability extensions can then land independently. Re-run the same 48 selected classes and 152 preordered reserves after each relevant milestone, with unchanged source identities/full member surfaces and explicit frozen revised domain policies. Keep first-gate and later failure stages separate.
Acceptance criteria
Baseline tooling reproduces all 200 v7 decisions with class identities, ordering, first diagnostics and explicit preparation/native/IR/engine/replay stages.
Each subsequent audit records before/after gates, next newly exposed limitations and exact supporting revision/tests; rejected cases remain in the ledger.
No HashMap/HashUtils replacement corpus, function/member dropping or result-driven specialization is used to inflate admission.
A final supported representative pilot uses class-only native replay coverage, all four profiles and 30/120s with preserved failures and actual search/extraction/replay accounting.
The task can ship baseline discovery before the other tasks; the final readiness claim waits for the evidenced supported population and protocol checks.
Use the frozen v7 200-class ledger and the source-linked reproducer; do not overwrite sealed experiment output. Reuse existing loaders, domain projection, source instrumentation, candidate/replay contracts and bounded observations. Keep original class members and independently frozen domain policies. Run focused source/native checks for the changed contract and leave broad suites to CI; unsupported and newly exposed later gates remain recorded.
Local evidence: iccq2026-paper/experiments/class-coverage-round-robin-20261002/real-class-campaign-20261014/{original/selection-ledger-v7.json,V7_INFRASTRUCTURE_FRONTIER.md} and real-class-machine-diagnostic-20261014/revised-protocol-v8/README.md.
Activity