Skip to content

Commit 0ae8213

Browse files
committed
P-037 A2.2: record the owner ruling on R (record-level absence)
Governance only, no code, census, schema or evidence change. docs/notes/p037-formal-kernel.md §10.6 records the ruling verbatim: - R is accepted as an explicit out-of-A2 precision boundary; - the A2.2 completeness claim is scoped to every relevant call inside every emitted functions[] record, and inside such a record a missing relevant call is still a defect; - no new records and no new carrier are authorized; - record absence is fail-closed: Phase B may never turn it into a positive semantic claim; - record-absence-boundary stays pinned and becomes a permanent Phase-B negative control; - R reopens only on measured value, through a separate kill-first comparison. The A2.2 note §9.4 and its status line now point to the ruling. Refs #304 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KmiyfrkaG9sJruTcshM2oq
1 parent 2fcd402 commit 0ae8213

2 files changed

Lines changed: 139 additions & 4 deletions

File tree

‎docs/notes/p037-a2.2-call-facts.md‎

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# P-037 A2.2 — honest call facts for every relevant call (pre-registered)
22

3-
> Status: **RESULT: stop point reached, with one escalated case-5 item (R),
4-
> see §9.** §§1–8 were pre-registered in `5daa6e3`, before any treatment
3+
> Status: **RESULT: stop point reached. R was escalated as case 5 and ruled
4+
> an explicit out-of-A2 precision boundary (§9.4; kernel note §10.6).** §§1–8 were pre-registered in `5daa6e3`, before any treatment
55
> code, and are left as registered. The contract, falsifiers, controls and
66
> evidence plan were committed before the extractor changes, so the result
77
> is judged against them rather than an impression afterwards.
@@ -257,8 +257,17 @@ job before commit, not a post-hoc patch.
257257
The measured cost at base is 1 relevant call on the repo tree
258258
(`FlowLocalsSample.DeferredHandoffNoFalsePositive`) and 0 on the corpus.
259259
It is pinned as the `boundary` census shape `record-absence-boundary`, so
260-
any accidental change is visible. **Owner decision needed** before phase
261-
B: accept R as an out-of-A2 boundary, or amend the contract for (a) or (b).
260+
any accidental change is visible.
261+
262+
**RULED (OWNER RULING, 2026-09-28): R is accepted as an explicit out-of-A2
263+
precision boundary**, verbatim in `docs/notes/p037-formal-kernel.md` §10.6.
264+
The A2.2 completeness claim is scoped to every relevant call inside every
265+
*emitted* `functions[]` record. Inside such a record, a missing relevant
266+
call is still a defect. Record absence is fail-closed: Phase B may never
267+
turn it into a positive semantic claim. `record-absence-boundary` stays
268+
pinned and becomes a permanent Phase-B negative control. Neither (a) nor
269+
(b) is authorized. R reopens only on measured value, through a separate
270+
kill-first comparison.
262271

263272
### 9.5 A census gap, closed after registration
264273

‎docs/notes/p037-formal-kernel.md‎

Lines changed: 126 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -747,3 +747,129 @@ After the semantic cut, a separate C+ checkpoint canonicalizes the temporary
747747
double representation of call facts. A stable call-site identity is introduced
748748
in A2 so the legacy and sidecar views cannot silently drift before that
749749
canonicalization.
750+
751+
### 10.6 Owner ruling on R, the record-level absence boundary (A2.2, #371)
752+
753+
A2.2 (`docs/notes/p037-a2.2-call-facts.md`) measured one boundary it did not
754+
close. A source method that gets no `functions[]` record has no carrier for
755+
`guarded_facts`. It escalated this as a case-5 item (§10.1). The owner ruled:
756+
757+
```text
758+
OWNER RULING — R / record-level absence (2026-09-28)
759+
760+
Decision: accept R as an explicit out-of-A2 precision boundary. Do not add a
761+
new carrier and do not create new "functions[]" records in A2.
762+
763+
A2.2's completeness claim is henceforth scoped as follows:
764+
765+
«Roslyn emits honest "guarded_facts" for every relevant call inside every
766+
emitted "functions[]" record.»
767+
768+
This is a scope clarification required by the measured record-level
769+
boundary, not authorization to weaken the per-record contract. For every
770+
emitted function record, the existing A2.2 rule remains absolute: every
771+
relevant call must appear, and absence is a defect.
772+
773+
R boundary
774+
775+
A source method for which the frontend emits no "functions[]" record has no
776+
"guarded_facts" carrier in A2.
777+
778+
Examples currently include:
779+
780+
- methods whose disposable locals all escape and that have no owned
781+
parameter;
782+
- methods whose lowered body is empty;
783+
- expression-bodied members not represented by the flow-function surface.
784+
785+
A2 does not create a flow record merely to host guarded facts, because that
786+
would change the MOS population and violate A2's zero-semantic-cut contract.
787+
788+
A2 also does not introduce a second top-level method/sidecar carrier. Doing
789+
so would change the frozen OwnIR layout and create two representations that
790+
Phase B/C+ would later have to reconcile.
791+
792+
"record-absence-boundary" remains an executable census boundary.
793+
794+
Phase B semantics
795+
796+
Record absence is fail-closed.
797+
798+
If no emitted "functions[]" record exists, the guarded engine has no
799+
evidence for that method. Absence must never be interpreted as:
800+
801+
- "must";
802+
- "no" / definite borrow;
803+
- an unconditional summary;
804+
- an eligible guard;
805+
- an "id" / "neg" transform;
806+
- proof that a call has no ownership effect.
807+
808+
It is simply outside the guarded fact domain.
809+
810+
Any implementation that converts record absence into a positive semantic
811+
claim is a defect.
812+
813+
What this decision does and does not claim
814+
815+
This ruling accepts a precision / recall boundary, not semantic completeness
816+
over arbitrary C# methods.
817+
818+
In particular, expression-bodied wrappers and other record-less methods may
819+
hide useful guarded-summary information. That is a known gap, not evidence
820+
that such methods are semantically irrelevant.
821+
822+
No claim is made that R is permanently acceptable.
823+
824+
Reopen condition
825+
826+
Do not expand the carrier pre-emptively.
827+
828+
Reopen R only when a bounded experiment demonstrates practical value that
829+
cannot be obtained through the existing "functions[]" surface, for example:
830+
831+
- a real or corpus-derived P-037 case whose required summary path crosses a
832+
record-less method;
833+
- a material missed finding / unresolved summary attributable specifically
834+
to R;
835+
- Phase B coverage showing that record absence forms a significant fraction
836+
of otherwise eligible guarded paths.
837+
838+
At that point run a separate kill-first experiment comparing:
839+
840+
1. extending the existing flow-function population; versus
841+
2. introducing a distinct fact-only method carrier.
842+
843+
Neither design is authorized by this ruling.
844+
845+
Acceptance consequence for #371
846+
847+
#371 may close A2.2 with R recorded as this boundary if all existing A2.2
848+
gates remain green:
849+
850+
- per-emitted-record call completeness;
851+
- sidecar inertness;
852+
- whole MOS unchanged;
853+
- public verdicts unchanged;
854+
- "record-absence-boundary" pinned.
855+
856+
After this ruling, Phase B may start from the #371 fact surface.
857+
858+
R is not to be silently removed from the census when Phase B begins.
859+
```
860+
861+
Consequences for Phase B (OWNER RULING, from the same decision):
862+
863+
- **Guardrail.** Phase B never reads a missing record or a missing sidecar as
864+
"no effects", borrow, unconditional, or "guard irrelevant". It means
865+
unknown: no guarded evidence.
866+
- **Negative control.** `record-absence-boundary` stops being a temporary A2
867+
boundary. It becomes a permanent Phase-B negative control: any mutant that
868+
draws a positive conclusion from absence must turn it red.
869+
- **Future kill-gate (not now).** After the first Phase-B shadow run, measure
870+
how many potential guarded paths break specifically because a
871+
`functions[]` record is missing:
872+
- near zero (0, or a handful in 10 000): the carrier stays as it is;
873+
- a material share (for example 15–20 % of real wrapper chains breaking
874+
at expression-bodied members): that is the basis for paying for an IR
875+
extension, through the kill-first comparison above.

0 commit comments

Comments
 (0)