core/workbench
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
api.py feat(workbench): add Apple UMA report read model (#911) 2026-06-24 14:47:36 -07:00
apple_uma_report.py feat(workbench): add Apple UMA report read model (#911) 2026-06-24 14:47:36 -07:00
calibration.py
construction_endpoint.py feat(workbench): wire Trace practice evidence route (#900) 2026-06-23 15:57:31 -07:00
construction_evidence.py
demo_narrative.py
evidence_bundle.py
field_evidence.py
generalization_evidence.py
journal.py
lived_life.py
logos.py
pipeline_record.py
practice_endpoint.py
practice_evidence.py
proposal_artifact.py
readers.py
README.md chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
replay.py feat(workbench-ui): add Trace practice evidence panel scaffold (#901) 2026-06-23 23:45:48 -07:00
schemas.py
server.py
tour.py

CORE Workbench Backend

workbench/ is the local operator/auditor API package for CORE. It exposes read models over committed artifacts, runtime traces, evidence bundles, demo envelopes, calibration ledgers, and narrow allowlisted actions.

It is distinct from:

  • workbench-ui/ — the React/Vite frontend.
  • workbench_data/ — ignored local read-model artifacts such as turn journals.
  • docs/workbench/ — plans, contracts, guides, and design documentation.

Backend modules should preserve the Workbench trust boundary:

  • read-only by default;
  • no hidden model calls or background execution;
  • execution only through explicit allowlisted endpoints;
  • artifact projections must include source paths/digests when available.

apple_uma_report.py belongs here because it projects a persisted benchmark report into a stable UI/API read model. It does not run benchmarks, import MLX, mutate reports, or authorize serving.