Skip to content

docs: cross-link multi-family admissibility benchmark in README #138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ProfRandom92 merged 1 commit into from
May 19, 2026
+5 −0
Merged

docs: cross-link multi-family admissibility benchmark in README #138

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,6 +135,11 @@ Comptextv7 turns noisy context into compact operational state, then validates wh
- **Operational drift:** `0.000000`.
- **Interpretation:** current setup is near-lossless because the fixtures are structured; this is a useful baseline, not a universal memory claim.

### Multi-Family Operational Admissibility Benchmark

- **Validates:** Deterministic multi-family operational admissibility benchmark with manifest-driven fixture selection, exact scoring, reproducible JSON artifacts, and progression-regression checks.
- **Method:** [`docs/benchmarks/multi_family_admissibility_benchmark.md`](docs/benchmarks/multi_family_admissibility_benchmark.md).
Comment on lines +140 to +141
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To maintain consistency with the other benchmark entries in the 'Benchmark family' section (e.g., Paper Replay and Agent Trace Replay), please include a link to the generated JSON artifact. Additionally, consider rephrasing the validation description to follow the established 'whether...' or 'how...' pattern used in adjacent sections to improve readability and alignment with the existing documentation style.

Suggested change
- **Validates:** Deterministic multi-family operational admissibility benchmark with manifest-driven fixture selection, exact scoring, reproducible JSON artifacts, and progression-regression checks.
- **Method:** [`docs/benchmarks/multi_family_admissibility_benchmark.md`](docs/benchmarks/multi_family_admissibility_benchmark.md).
- **Validates:** whether multi-family operational state remains admissible across manifest-driven fixtures using exact scoring, reproducible JSON artifacts, and progression-regression checks.
- **Artifact:** [`artifacts/multi_family_admissibility_results.json`](artifacts/multi_family_admissibility_results.json).
- **Method:** [`docs/benchmarks/multi_family_admissibility_benchmark.md`](docs/benchmarks/multi_family_admissibility_benchmark.md).


### Iterative Replay Degradation Prototype

- **Validates:** how checked-in paper and agent-trace fixtures degrade across bounded repeated compact/replay cycles.
Expand Down
Loading