Repository navigation
ONT-4c5 (infra#921): aprender capability-cell extractor + arming rule (required Unknown{NotRun} meets to RED) #3972
Description
Row ONT-4c5, tracked in paiml/infra#921. Operator authorization, stated in session infra-83 on 2026-09-23 (verbatim): "I authorize expansion". It covers the capability-cell row, the arming rule, and this aprender extractor.
Scope (per #921):
- The extractor reads the ladder's capability cells
(model, format, quant, host, backend, verb, thinking), each carrying: an oracle, a positive control observed failing (a must-RED case), a measurement, and a verdict in[PASS, FAIL]. - It implements the arming rule in ONT-6's verdict lattice (
ontology/verdict.rs): on a REQUIRED cell,Unknown{NotRun}meets to RED (exit 1); exit 2 keeps meaning only "gate not armed here". - The judgement stays in
scripts/lib/crux_inference_judge.py(0.69.1 gate hardening (no GPU): sha-bound receipts, missing-field=FAIL, verb output oracles, CRUX judge strength, DEFER exits 2 #3957). The extractor checks the cell's SHAPE, not its correctness. - First-green proof on
8963f91a3, where*A3B*is the one legacydeferredkey. On any other commit it is a guard over zero files. Must-RED: a required cell with no measurement meets to RED.
Sequencing: the design can start now. The row text and the probe land in a later infra PR, after infra#909 (v4.11); infra-83 sends that PR number. Its place on R-24's path relative to 4b2 / 4c3 / 4c4 is pending an infra quorum grill.
Activity
noahgift commentedon Sep 23, 2026
milestone → 0.71.0 per docs/roadmaps/milestone-triage-2026-09-23.md (#4024), operator approval 2026-09-23 (relayed by aprender-cf). Reason: debt ratchet pillars B/C (#3997: pv at the deepest level, ontology merge), slice 2
noahgift commentedon Sep 23, 2026
triage 2026-09-23 (aprender-dd): kept in 0.70.0 and labelled ont-0.70. Operator, verbatim (relayed by the cop aprender-cf): "the ontology spec MUST be finished in .7". Classified as ontology/SHACL spec work: its title names ONT/ontology/SHACL/capability cells, or its body cites an ONT- row.
noahgift commentedon Sep 23, 2026
Correction to the triage comment above (aprender-dd): this issue was MOVED from 0.71.0 to 0.70.0, not "kept". A failed first attempt applied the milestone before its label step errored, so the second pass read it as already in 0.70.0. The move and the reason stand.
noahgift commentedon Sep 23, 2026
triage (aprender-dd; cop aprender-cf ruling 2026-09-23): ONT-4c5 part 1/2, the aprender capability-cell EXTRACTOR + arming rule. Part 2/2 is #4047 (the pv-lint capability-cells shape). One row, two halves, ONE owner takes both. The row's single done_when lives on #4047 and requires this issue closed.
PMAT-3972: roadmap row owned (aprender-pvl-a), in_progress
docs(ont-4c5): implementation plan for ONT-4c5 capability cells (#3972,
ONT-4c5 re-land on batch/0.70.0: the mutations follow the tree's V*, …
PMAT-3972: roadmap row owned (aprender-pvl-a), in_progress
noahgift commentedon Sep 25, 2026
ONT-4c5 is code-complete on car #4429 (
car/0.70.0@93aa211e8). It is not yet onmain. Checked by aprender-ea, 2026-09-25 ~20:30 Madrid. infra-83 confirmed they do not own this row; aprender-ea owns both halves now.Evidence on the car head:
cargo test -p aprender-contracts-cli --test ont4c5_capability_cells: 11 passed, 0 failed. The planted-RED cases pass:every_not_run_required_cell_rejects_naming_exactly_that_cell: this is the arming rule, NotRun on a required cell gives RED.disarming_capability_cells_turns_the_probe_reda_deleted_current_release_row_rejects_naming_the_cellan_empty_domain_declines_never_passespv lint contracts --gate shapes --format json(pv 0.69.3 built from 93aa211): rc 0, verdictPass.armed_shapes=[capability-cells, ladder-measured, ladder-green, ont-shapes-v1].pc_shapes["capability-cells"]=fired.capability_cells.not_run=[];refused_labels=[].contracts/ont-capability-cells-v1.yamlandtests/fixtures/ont/capability-cells-plant.yaml. The code is inontology/capability_cells.rsandlint/capability_cells_gate.rs, via be48bed (9c4264d, e2549bc).Delta from the spec: the domain has 16 cells, not the 14 the issue named: 8 q4km rungs × {lambda, gx10}, with
v_star0.69.1. The ladder gained a rung after the spec was written. The gate derives the domain from the ladder, so the gate is not wrong. The row text in infra should say 16.Remaining for done_when: car #4429 merges to
main. #4429 lists these issues underTickets:, which is not a closing keyword, so they will not close themselves. aprender-ea will close #3972 and #4047 when the car merges.9 remaining items
noahgift commentedon Oct 14, 2026
P0 to P1 (2026-10-14 P0 triage): P0 now means it blocks the next release or carries the operator's own words on it; this issue does neither, so it stays on the 0.71.0 milestone at P1. The operator quote in its history is a milestone-wide triage note, not words about this issue.
noahgift commentedon Oct 14, 2026
Folded into #5308 as a checklist row (TRIAGE-100, 2026-10-14): the open-ticket cap is 100, so this ticket is now tracked on that master and closed as not planned. Nothing is lost: reopen it when its work resumes, and an open PR for it reopens it. Pushed branch:
PMAT-3972-ont-4c5-r.Agent: aprender-clerk
noahgift commentedon Oct 14, 2026
Row moved: #5308 was split into named masters (TRIAGE-100 master naming), so this ticket's checklist row is now on #5335.
Agent: aprender-clerk
noahgift commentedon Oct 14, 2026
Reopened: this ticket carries the operator's own words, and TRIAGE-100 keeps those open unless their owner agrees to the fold. The checklist row on #5308 is withdrawn; this ticket stays the record. Re-linked under #3269.
Agent: aprender-clerk