core/core/demos
Shay 310aed9ff0
chore: Refactor CLI and Governance Anchors (#926)
* docs: consolidate governance anchors and clean up test registries

* refactor(cli): decompose cli into dedicated modules

* test: fix broken test baselines and formatting

* docs: add domain boundary READMEs for governance anchors

* test: update baseline for determination lane

* test: fix capability_pass expectation

* test: fix CORE_SHOWCASE_SKIP_BUDGET enforcement

* chore: cleanup CLI extraction and unreachable code
2026-07-03 12:34:56 -07:00
..
__init__.py feat(demos): implement ADR-0098 — Demo Composition Contract 2026-05-21 19:02:29 -07:00
audit_tour_adapter.py feat(demos): implement ADR-0098 — Demo Composition Contract 2026-05-21 19:02:29 -07:00
contract.py feat(demos): implement ADR-0098 — Demo Composition Contract 2026-05-21 19:02:29 -07:00
expert_demo.py feat: ADR-0113 rename expert-demoaudit-passed; reserve expert namespace (ADR-0114 GSM8K roadmap) 2026-05-22 15:36:10 -07:00
learning_loop_adapter.py feat(demos): implement ADR-0099 — Public Showcase Demo 2026-05-21 19:44:48 -07:00
README.md chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
showcase.py fix(quarantine): drain all 60 quarantined tests — QUARANTINE=∅ (#267) 2026-05-25 11:22:12 -07:00
showcase_adapters.py fix(ci): re-pin public_demo lane SHA after showcase content drift (#807) 2026-06-17 15:42:40 -07:00
tour_adapters.py feat(demos): implement ADR-0098 — Demo Composition Contract 2026-05-21 19:02:29 -07:00

Demo Composition Layer

core/demos/ contains the typed composition surface for demos: contracts, adapters, showcase rendering, and expert-demo packaging.

It does not own standalone scenario fixtures. Those live under top-level demos/, where each demo package can pin its inputs, expected artifacts, and honesty ledger.

Boundary:

  • demos/ proves a narrow claim inside a deterministic local envelope.
  • core/demos/ adapts proven demos into shared presentation and Workbench surfaces.