Skip to content

CVN-N001-EK-S02 — Derivations workspace (scaffolding)

Workspace for the D2 derivations. Analysis-only (runbook, architecture): each value is produced by a read-only notebook/script and recorded as a signed derivation (or a typed INFEASIBLE). No training, no Airflow launcher, no Phase-2 run, no model selection — STOP and ask the operator if any step would require a run. This page is scaffolding: structure + templates, nothing executed.

Locations & naming (resolves runbook §5)

Item Location / convention
Derivation record (per value) derivations/<value>.yaml (from _TEMPLATE_derivation.yaml)
Typed INFEASIBLE record derivations/INFEASIBLE-<reason>.yaml (from _TEMPLATE_infeasible.yaml)
Charter values (unlocked) charter draft §2 placeholder table
Validation evidence matrix derivations/validation_evidence_matrix.md
MLflow (provenance-only) experiment cvn-n001-ek-s02, run <value>-<YYYYMMDD>

Status table (fill as derivations land)

Value File Plan ref Status Lockability
Reference capacity reference_capacity.yaml §9.1 BLOCKED (record) — no local OHLCV/liquidity
P90 cost (+ tier) p90_cost.yaml §9.2 BLOCKED (record) — no observed fills; only model-defined sweep non-lockable
E_econ_min / E_pred_min (mapping) e_econ_e_pred_mapping.yaml §10 pending
Power → MDE / N_min power_mde.yaml §11 pending
Primary null-gate null_gate.yaml §12 pending
Budgets proposal budgets.yaml §14 pending
Sortino R1 note sortino_r1.yaml §13 pending

How to fill (per value)

  1. Run the pre-flight checklist (runbook §3).
  2. Derive in a read-only notebook/script over existing inputs (no launcher).
  3. Copy _TEMPLATE_derivation.yaml<value>.yaml, fill + sign (provenance fields).
  4. If undefendable → copy _TEMPLATE_infeasible.yamlINFEASIBLE-<reason>.yaml (a successful outcome).
  5. Record the result in the status table above and the evidence matrix.
  6. On completion, assemble the S03 handoff package (runbook §12).

Definition of scaffolding-done

Structure + templates + per-value stubs + evidence matrix exist; runbook §5 locations are concrete; no value derived yet, no run performed. The next step (each derivation) is implementation work under the analysis-only boundary.