core/workbench
2026-07-11 02:16:57 -07:00
..
__init__.py
api.py
apple_uma_report.py
calibration.py
construction_endpoint.py
construction_evidence.py
demo_narrative.py
evidence_bundle.py fix: add meta_rh_evidence to evidence bundle and replay fields 2026-07-11 02:16:57 -07:00
field_evidence.py
generalization_evidence.py
journal.py feat: integrate MetaRHEvidence into workbench schemas and journal 2026-07-11 02:16:57 -07:00
lived_life.py
logos.py Lane 4: Registry Consolidation (language_packs to packs) 2026-07-04 15:11:28 -07:00
pipeline_record.py
practice_endpoint.py
practice_evidence.py
proposal_artifact.py
readers.py Lane 4: Registry Consolidation (language_packs to packs) 2026-07-04 15:11:28 -07:00
README.md
replay.py fix: add meta_rh_evidence to evidence bundle and replay fields 2026-07-11 02:16:57 -07:00
schemas.py feat: integrate MetaRHEvidence into workbench schemas and journal 2026-07-11 02:16:57 -07:00
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.