Repository navigation
Commit e6f8fcb
committed
CR-150 batch-C: base fix, wiring W1-W3 + L22P, and the .bin selected-window capability
This is the single-parent proof/squash commit for batch-C on a35a64c. It
supersedes d43257f (the earlier proof head of the same base fix, tree
06abb8c) and carries that tree plus everything the batch-C branch assembled
after it: merges of W1 (2995a52), W2, W3 and L22P, the .bin bar input spec
(637816a, fafb2c6) and the selected-window capability commit e0f2086
(core/cr150-swcap, CORE-TOP's order of 2026-10-20 22:23), all on top of the
base fix below. Tree 2099d0d; branch head e0f2086.
The batch-C base (3af3e3c, on a2f3dfd) is red in the lab preflight in four
stages, and every lane on it inherits the red. This commit fixes the three
mechanical stages in place; the fourth is settled by naming, per CORE-TOP's
ruling of 2026-10-20 20:03 (no history rewrite; a single-parent proof commit
with this tree and parent a35a64c carries the block below in its own message).
Counts, each re-derived from the check scripts rather than typed:
- EXPECTED_PUBLIC_DECLARATIONS 106 -> 107 and EXPECTED_RUNTIME_IMPLEMENTATIONS
86 -> 87 in scripts/test_ci_verify.py:1206-1207, matching
scripts/check_c_abi_runtime.py (107 across the runtime headers, 87 runtime
implementations, 96 C declarations in pineforge.h, which this change does not
touch) and the "87 above" comment the same script carries.
- The five pages with stale counts (docs/pages/index.md:142/:153/:175,
docs/coverage.md:135, docs/design/native-feature-parity.md:178/:330,
docs/pages/abi-stability.md:73/:132) were renumbered to the derived values
(95->96 declarations, 86->87 implementations).
- 63 stale file:line anchors across nine documents were re-anchored to the
symbol that actually sits on the cited line, and each edit names the symbol
next to the number so the citation is checkable by reading.
Checks run on this tree (pure-Python doc checkers only; nothing was compiled,
built or run on the Mac):
- scripts/check_doc_anchors.py rc 0: 2173/2173 anchors resolve to their symbol
(re-measured on this tree, which carries the .bin spec's citations).
- scripts/check_doc_lint.py rc 0: 0 offenders.
- scripts/check_c_abi_runtime.py rc 0.
- scripts/check_doc_reverts.py: rc 1 on the batch-C branch (17 unnamed
deletions there, 16 of them eadd9b3's and one introduced by 637816a;
none from e0f2086); rc 0 on the single-parent squash of this tree, whose
judged range collapses the branch's intermediate commits. The deletions the
squash diff still shows are named in the blocks below, copied verbatim from
lanes/core-cr150-batchc/DOC-REVERTS-NAMES.txt.
Not verified here: verifier-tests, the build, and the corpus. The lab
preflight on the single-parent proof commit is the next step.
DOC-REVERTS NAMES (copy this block verbatim into the body of every proof commit and the squash body that carries the arena-bound documentation)
Documentation sentences named as removed on purpose. The sentences were introduced by d7d8bd3 (CR-150 certified bound: one pure arena_bound function, its derivation doc, vectors, harness and corpus census) and deleted by eadd9b3 (CR-150 certified bound round 3: childPrivate is reported, not routed; escalation policy; compiler-facts table). They are in docs/design/arena-bound.md and docs/design/arena-bound-corpus-census.md. Cause: the rulings of 2026-10-20 17:17 (COMPUTE-TOP and L6), applied by that round: (1) childPrivate stays reported but leaves unboundedTerms, the top-level unbounded flag and its reason; (2) interim 1.7.0 sizing is COMPUTE's escalation policy (attempt 0 default arena, a typed arena_exhausted re-places up the ladder, escalation cap 2, never charged), and an unbounded term does NOT route a run to the largest rung and disk; (3) nothing is run on the Mac, so the census reproduction block no longer names a ctest command and instead gives a reading-only re-run recipe. The removed sentences, by their opening words:
1. "The engine HEAD inspected is" (census intro; rewritten as "The original census inspected engine HEAD" plus a round-3 paragraph).
2. "currently unavailable facts, each known probe has all four names in" (census; now "the three sizing names").
3. "Term | Flagged unbounded/unknown for routing | Proved unbounded | UNCLASSIFIED" (census table header; now "Sizing term | Flagged unbounded/unknown ...", routing wording removed by ruling 2).
4. "certificate. Thus even a later finite arena proof does not automatically make an entire invocation bounded." (census; now says the three-term verdict needs OHLCV and finalizer-stream facts, private diagnostics do not prevent it).
5. "Extra feeds, output/trace/hash counts and private RSS/AS proofs are classified independently, and each missing proof names its term." (census; private RSS/AS is now a separate informational term).
6. "probe list, and counts for each name in unboundedTerms. Missing input or unclassified coverage makes the full lab test fail." (census; now three names plus an informational childPrivate count; the harness still fails on missing input or unclassified coverage, tests/test_arena_bound.py corpus_run).
7. "Linux lab reproduction, after the pinned corpus is available locally:" and the line "ctest --test-dir build-arena -R '^test_arena_bound_corpus$' -V" (census; replaced by the reading-only re-run section, ruling 3).
8. "The first command only reads sources/sidecars and prints classifications. It exits nonzero on unclassified entries. The second performs the real arena-attached runs and writes census/measurements under build-arena/arena-bound/; it does not pass an all-unknown census. Neither command was run by this edit-only lane." (census; replaced by the expanded description of the census-only command and a link to arena-bound.md for lab verification).
9. "M={arena,ohlcv,finalizerStream,childPrivate}. Unknown is not yes." (census; now M={arena,ohlcv,finalizerStream} plus a separate childPrivate note).
10. "unboundedTerms: [arena?, ohlcv?, finalizerStream?, childPrivate?]," (arena-bound.md result shape; childPrivate removed by ruling 1).
11. "unboundedTerms uses the displayed order and contains every term whose own flag is true. reason is empty when every term has a certified finite value." (arena-bound.md; now only the three sizing terms and an independent informational childPrivate flag).
12. "APP routes any true top-level flag to its largest rung and disk backend, as the owner requires. It must retain the named unresolved terms in its plan." (arena-bound.md; removed by ruling 2).
13. "That routing decision does not prove that an arbitrarily chosen finite disk arena suffices for a mathematically unbounded computation. No such disk-size guess is returned here. Resolving that case without capacity refusal requires an owner/runtime policy: RETURN TO CORE-TOP." (arena-bound.md; replaced by the escalation-policy paragraphs, ruling 2).
14. "P_rss, P_as | Child private resident / address-space terms; each needs its own proof." (arena-bound.md table row; now "Informational child private ... Neither affects sizing routing").
15. "flag is false." and "the term remains unbounded. A vector with 4096/8192 private bytes tests only arithmetic/flag transport under a hypothetical trusted proof; those numbers are explicitly not real engine coefficients." (arena-bound.md; vectors recomputed in round 3 without the childPrivate toy proof).
16. "RETURN TO CORE-TOP: obtain the applicable post-port measurements and an AS/strategy-private bound before claiming a fully finite invocation." and the rows "All terms | Same Unicode arena. Primary one-page RSS/two-page AS ..." and "Unbounded emitting loop | Null arena inputs except E=2; no finite guessed size. Other absent term proofs remain separately named." and "and cause incomplete coverage to fail. Every measured run prints actual," (arena-bound.md vector tables and verification text, recomputed or reworded in round 3).
Each of these deletions was intended by round 3 of lane core-cr150-l22u (design change above); none is a silent revert.
SECOND NAMES BLOCK (four further deletions in the proof range a35a64c..this commit)
Relative to the integration commit a35a64c, this proof commit's diff also
shows four sentence-level rewrites that check_doc_reverts reports as unnamed
deletions. Each was an intended replacement by batch work, not a silent revert:
A. docs/pages/run-failure-codes.md: "The engine could not create or write the
report sink." and "The run has no completed sink or valid trailer." were
introduced by 39a718b (cr150 L6b-1, #431) and replaced in commit
573fa74 (CR-150 catalog: report_sink_failed is class engine_fault) by the
expanded row, which states the same meaning, keeps the closing words "the
run has no completed sink or valid trailer", and adds the optional arguments.
B. docs/design/cr150-contracts.md: "A selected sink performs one presentation
of the full selected curve, preserving the hook's published-length changes
before the selected writer emits the anchor and final window observations."
was introduced by 76e2310 (CR-150 L6b-2, #435) and replaced in commit
83fda84 (CR-150 L17b: streamed selected capture with a bounded tail
window W=2) by the tail-window contract under CORE-TOP's ruling A; that
commit's own body already names this sentence.
C. docs/design/native-feature-parity.md: the hash-pinned citation unit
beginning "`sha256:H` c_abi.cpp:N, `sha256:H` check_c_abi_runtime.py:N, ..."
was introduced by d3cca9e (5c3c9ae) and rewritten by this branch's
count/anchor refresh: every affected row keeps its claim and its evidence and
updates the citations to the lines that hold the named symbols now.
None was a silent revert. Each replacement is named by the commit that made it;
this proof commit names them again because the single-parent proof collapses
the branch's intermediate commits out of the judged range.
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>1 parent a35a64c commit e6f8fcb
126 files changed
Lines changed: 22325 additions & 877 deletions
File tree
- docker
- docs
- adr
- design
- pages
- include/pineforge
- detail
- source
- scripts
- src
- source
- tests
- cr150.d
- data
- fixtures
- arena_bound
- flat_memory
- ownership
Some content is hidden
Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
98 | 98 | | |
99 | 99 | | |
100 | 100 | | |
| 101 | + | |
101 | 102 | | |
102 | 103 | | |
103 | 104 | | |
| |||
155 | 156 | | |
156 | 157 | | |
157 | 158 | | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
158 | 162 | | |
159 | | - | |
160 | | - | |
| 163 | + | |
161 | 164 | | |
162 | 165 | | |
163 | 166 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
33 | 33 | | |
34 | 34 | | |
35 | 35 | | |
36 | | - | |
| 36 | + | |
37 | 37 | | |
38 | 38 | | |
39 | 39 | | |
| |||
519 | 519 | | |
520 | 520 | | |
521 | 521 | | |
522 | | - | |
523 | | - | |
524 | | - | |
| 522 | + | |
| 523 | + | |
| 524 | + | |
525 | 525 | | |
526 | | - | |
| 526 | + | |
527 | 527 | | |
528 | 528 | | |
529 | 529 | | |
| |||
552 | 552 | | |
553 | 553 | | |
554 | 554 | | |
| 555 | + | |
555 | 556 | | |
556 | 557 | | |
557 | 558 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
4 | 7 | | |
5 | 8 | | |
6 | 9 | | |
| |||
232 | 235 | | |
233 | 236 | | |
234 | 237 | | |
235 | | - | |
| 238 | + | |
| 239 | + | |
| 240 | + | |
236 | 241 | | |
237 | 242 | | |
238 | 243 | | |
| |||
242 | 247 | | |
243 | 248 | | |
244 | 249 | | |
245 | | - | |
| 250 | + | |
246 | 251 | | |
247 | 252 | | |
248 | 253 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
0 commit comments