You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`31bae2a`|**Wire MicrocalibrateAdapter into us.py pipeline — G1 unblocker**|
33
+
|`e46eb49`| Test zero_rate_per_column populated on every result |
30
34
31
35
Plus one commit on `main` archive: `archive/semantic-guards-wip-20260416` on microplex (core). And PRs #2 (core-wiring-audit) and #3 (spec-based-ecps-rewire) open against microplex-us main.
32
36
@@ -89,9 +93,44 @@ Branch is in good shape for review. No outstanding tasks block merge.
89
93
90
94
## What I did not do
91
95
92
-
-**No changes to main production pipelines.**`pe_us_data_rebuild_checkpoint.py` / `us.py` are untouched. The rewire lives on its branch as docs + harness + adapter, ready to wire in.
93
-
-**No v7 run.** With the stage-1 evidence now in hand, the next production run should use the rewired path (CPS scaffold + microcalibrate), not another v4/v5/v6-style invocation of the current pipeline.
94
-
-**No rerun on GPU.** ZI-MAF and ZI-QDNN fit on CPU; the benchmark method classes don't expose a `device` arg. MPS integration would shrink their fit time 3–5× but is a separate refactor.
96
+
-**No v7 run.** With the stage-1 evidence now in hand and
97
+
`--calibration-backend microcalibrate` wired, the next production run
98
+
should use that flag against the current pipeline. Expected outcome:
99
+
the v4/v6 OOM is gone.
100
+
-**No rerun on GPU.** ZI-MAF and ZI-QDNN fit on CPU; the benchmark
101
+
method classes don't expose a `device` arg. MPS integration would
102
+
shrink their fit time 3–5× but is a separate refactor.
103
+
104
+
## Second-half work (after initial summary)
105
+
106
+
After the stage-1 evidence landed, I continued with the open items:
107
+
108
+
1.**Microcalibrate wiring into `us.py`** (commit `31bae2a`) — 20-line
109
+
change plus dispatch test. `calibration_backend="microcalibrate"` is
110
+
now a valid configuration that routes to `MicrocalibrateAdapter`.
111
+
The existing `_apply_policyengine_constraint_stage` call site at
112
+
`us.py:2931` needed zero changes because the adapter matches the
0 commit comments