Repository navigation
Repository Map
bend2-agentic-eda-research-design.md the protocol (v0.4). Normative. Appendices G-J carry the authoring, proof and public-repo standards
README.md the study in one page, plus quickstart
bendeda/ the harness
cli.py all 16 commands; planned ones exit 3
metrics/core.py §10 definitions as pure functions
plugins/interfaces.py LawLanguage, Translator, Gate, Oracle, HardwareBoard
schemas/ run, event, task, policy, provenance
tests/ stdlib unittest; known-answer metric tests
tools/ hygiene checkers (secrets, locked files, SPDX, whitespace, DCO, oracle absence, site)
tasks/<tier>/<task>/ task packages; see tasks/README.md for the file contract
bv/ BendBV: U32 + mask(w) bit-vectors, with proofs (planned)
docker/ pinned build definitions; Dockerfiles only, no prebuilt images
experiments/ run matrices (pilot, trackA, ablations, B, C, D)
results/ small aggregates only; bundles are release assets
docs/ research notes, wiki source, protocol sources
site/ GitHub Pages developer site
amendments/ dated amendment records and the template
locked/ LOCKED.json hash manifest (empty until the first freeze)
prereg/ (created at Phase 3) frozen protocol, thresholds, analysis plan
The design document is at the root. It is the artifact the study is judged on, not a secondary doc.
tasks/ holds law and oracle material side by side but with different owners. Physical proximity is convenient; the barrier is the mount and the provenance file, not the directory. The oracle's content lives outside the repository entirely.
bendeda/schemas/ is inside the package so python -m bendeda validate works after pip install, without a checkout-relative path.
results/ is small by policy. A repository full of logs becomes unreviewable and unfetchable; bundles are release assets with checksums.
locked/ can be empty and still be meaningful. The guard, the amendment template and the manifest format exist before the first lock, so locking is a decision rather than an improvisation.
docs/wiki/ mirrors the GitHub wiki. The wiki is the living log; keeping its source reviewable in git means a decision can be reviewed like code, and a wiki outage does not lose the history.
| Question | File |
|---|---|
| Why is C2 needed if C1 exists? | design doc §5.2, §3.1 H2 |
| What exactly is "false assurance"? | §10.2, bendeda/metrics/core.py
|
| Who wrote these laws? |
<task>/provenance.yaml, Appendix J |
Why does canary exit 3? |
wiki Running-the-CLI, decision log 2026-11-21 |
| What stops me editing a locked law? |
tools/check_locked.py, CODEOWNERS
|
| How is the oracle hidden in a public repo? | Appendix I.4, wiki Contamination-Controls |
Code Apache-2.0 · documents and task data CC BY 4.0 · this wiki records decisions, not the current state of the code — the design document and the repository are normative.