Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions research/p104-rewrite-delta-commutator-exclusion/NOTICE
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
PR5660 typed rewrite-delta inverse-commutator exclusion

New contribution prepared with substantial OpenAI Codex assistance for the donor.
The local independent paper review also used OpenAI Codex. This notice makes no
claim of independent human scientific acceptance or novelty of the classical
commutator/transvection identity.

The unmodified files inputs/pr5660-construct.py, inputs/pr5660-WITNESS.json,
inputs/pr5660-PROOF.md and inputs/pr5660-SOURCES.json are retained from Ali
Romman's PR5660 publication at commit 3b0b4f37d5005f381ed9cfcccebfbe1ab35c71aa,
research/p104-contact-rewrite/. The constructor's original notice is preserved:

The A2 identity is from PR3998/4019 and zxv's PR5643 paid construction.
PR5644 supplies the three helper relations. Ali Romman prepared the new
four-gate construction with substantial OpenAI Codex assistance. Apache-2.0.

The retained PR5660 manifest preserves further source pins and predecessor
attribution for PR5627, PR5643, PR5644, PR5650 and PR5651. Their P104, native,
helper, caller, controller and compiler lineage is not claimed as new here.
Related scalar reassociation and bounded local screen work in Discussion5600
is credited in README.md. Later successor work receives no transferred claim.

This package and the copied source files are under Apache-2.0, consistently
with the repository contribution policy and retained source notice. The
repository-root LICENSE supplies the license text in the intended overlay.
Retain this notice and the original source notices when redistributing.
83 changes: 83 additions & 0 deletions research/p104-rewrite-delta-commutator-exclusion/PROOF.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,83 @@
# A typed exclusion for the fixed PR5660 delta

## The programs and edit

Let P and Q be typed public programs with the same frame inventory. A public role's required scalar contacts follow a nondecreasing chain of subspaces; a public MOVE either changes nothing or strictly increases the subspace. Every ADD uses a common chart for both operands. These are premises on both programs. Source code declaring or checking a condition is not by itself an independent replay of an actual word.

Work in the scalar-plus-owned skeleton: omit public MOVEs, retain owned MOVEs and every scalar, lifetime and protected observation event. Public transport remains governed by the typed path premise. An observer below means a skeleton event or protected observation touching a specified role; the public MOVEs required to reach the next chart are not forbidden observers.

Write `C=165`, `H=586`, `S=733`, `X=21`. The indices are zero-based indices in the old skeleton, not full-word event indices. The exact edit deletes:

| Label | Old index | ADD | Frame | Dimension |
| --- | --- | --- | --- | --- |
| O1 | 12513 | `H += -4 S` | 597 | 1 |
| O2 | 12753 | `C += 2 S` | 597 | 1 |
| O3 | 12754 | `C += -1/2 X` | 652 | 2 |
| O4 | 12755 | `X += H` | 652 | 2 |

At the old O4 position it inserts this consecutive skeleton block:

| Label | ADD | Frame | Dimension |
| --- | --- | --- | --- |
| E1 | `C += 1/2 H` | 3 | 0 |
| E2 | `H += -4 S` | 597 | 1 |
| E3 | `X += H` | 652 | 2 |
| E4 | `C += -1/2 X` | 652 | 2 |

The bases are exactly `[]`, `[82]`, `[82,268]` for frames 3, 597, 652. Every other skeleton event is preserved unchanged and in order. Every surviving event strictly between old indices 12513 and 12755 is disjoint from `{C,H,S}`. There is no assumed isolation for X. The exact indices imply that O2,O3,O4 are consecutive, stronger than merely asserting adjacency of the last pair.

These premises are bound to [the copied witness](inputs/pr5660-WITNESS.json) and [constructor](inputs/pr5660-construct.py): skeleton at lines 20–21; frame-preserving rebuild and public monotonicity at 24–58; exact anchors/roles/replacement at 92–110; isolation and final-pair adjacency at 111–115; ordered deletion/insertion at 117–123. The frame inventory is preserved by `deepcopy` and replacement of only `program` in `rebuild` (the later schema tag is irrelevant). The published code's replay and cost checks are not premises proven here.

Let φ be the order-preserving survivor map from old events outside `{O1,O2,O3,O4}` to their unchanged new occurrences. E1–E4 are new occurrences. In particular O1 and E2 are different provenance labels even though their instruction bytes agree. Equal-looking instructions elsewhere do not define φ.

## The motif and the meaning of new incidence

Let a,b,d be distinct public roles, and let α,β be nonzero exact coefficients. The motif has four ordered scalar anchors:

$$
\begin{aligned}
M_1 &: a \mathrel{+}= \alpha b && (\dim=1),\\
M_2 &: b \mathrel{+}= \beta d && (\dim=3),\\
M_3 &: a \mathrel{-}= \alpha b && (\dim=5),\\
M_4 &: b \mathrel{-}= \beta d && (\dim=7).
\end{aligned}
$$

The middle role b follows the complete absolute dimension-zero to dimension-nine route with five positive MOVE ranks `(1,2,2,2,2)`. The four anchors are its only interior required contacts. Extra scalar contacts to b before the corridor at its unchanged dimension-zero endpoint, and after it at its unchanged dimension-nine endpoint, are allowed. Every other skeleton event or protected observation strictly between M1 and M4 is disjoint from `{a,b,d}`. The absolute starting dimension zero is essential: the rank partition alone would not fix anchor dimensions 1,3,5,7.

The familiar scalar identity replaces these four gates by `a -= αβ d`, restoring b. We assert no novelty for that identity, and prove no positive native or economic realization of it. Other retained operand, endpoint, target and native conditions can only restrict this necessary typed motif class further.

A **new incidence under this edit** is a motif in Q satisfying either:

1. One of its four anchors is an inserted E event; or
2. All four anchors are survivors under φ, with the same old role/edge/coefficient pattern, and their old corridor failed the strict observer condition solely because at least one removed O event touched `{a,b,d}`.

An old valid motif, changed economics of an existing motif, newly excused surviving observers and changed route predicates are outside this definition.

**Proposition.** For every typed P and valid Q satisfying the fixed edit, frame, isolation and adjacency premises above, there is no new incidence in this motif class.

## Case 1: an inserted anchor

The inserted dimensions are 0,1,2,2. The motif anchor dimensions are 1,3,5,7. Thus only E2 could be a motif anchor, and it must be M1. This fixes `a=H`, `b=S`, `α=-4`.

The immediately next skeleton event E3 reads H=a and writes X. It cannot be M2 or M4, whose destination must be S. It cannot be M3, whose destination/source must be H/S at dimension five. No remaining anchors fit before the immediately following event. E3 is consequently a forbidden observer inside the unfinished motif corridor. This contradiction excludes every inserted-anchor incidence. Additional endpoint contacts and intervening public transport do not remove the E3 read.

## Case 2: a removed old barrier

All anchors now survive. Let R=`{a,b,d}`. Some deleted O touches R by the case definition. The union of roles touched by the deleted events equals the union touched by the inserted block, namely `{C,H,S,X}`. Hence at least one E event touches R.

The E block is consecutive in the skeleton and contains no motif anchor in this case. It cannot lie inside the new corridor, since its R-touching event would be a forbidden observer. Therefore all motif anchors lie before the block or all lie after it. If they all lay after it, their old preimages would follow O4; every deleted event would precede the old corridor and none could be its barrier. All four anchors must therefore precede the block.

The last possible surviving old index before O4 is 12752, because 12753,12754,12755 are consecutive deleted positions. O2,O3,O4 therefore cannot lie inside this old corridor. Only O1 can be the lost barrier. This closes X-only possibilities without assuming X isolation: both deleted events involving X are in the terminal cluster, outside the corridor.

For the old corridor to contain O1, M4's old preimage lies strictly between O1 and O2, hence within the isolation interval. M4 touches b,d and survives, so both b,d lie outside `{C,H,S}`. O1 touches R but only has roles H,S. Thus `a=H` or `a=S`.

M3 touches that a in `{C,H,S}`. Isolation prevents M3 from lying strictly between O1 and O4. It precedes M4 in that interval and is a survivor, so M3 must precede O1. But M3 requires a at dimension five and later O1 requires the same a at dimension one. The typed old public chronology forbids that decrease. This contradiction excludes the removed-barrier case.

The two cases exhaust the stated definition of new incidence. The proposition follows.

## What follows from the proposition

No occurrence lookup can discover a newly created motif in this closed delta class if the premises hold. This is the useful source-specific stop decision. It neither counts nor excludes motifs already present in P, and it says nothing about other rank partitions, translated starting charts, observer contracts, changed economics, changed scalar graphs or successor releases.

The proof needs no inversion of the final WORD. Although the declared edit has a deterministic skeleton preimage once a final E block is bound, invertibility does not identify that preimage with the historical PR5650 payload. No equality with that payload is claimed. Actual word custody, typing/native validity and whole-word coverage remain separate obligations.
39 changes: 39 additions & 0 deletions research/p104-rewrite-delta-commutator-exclusion/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# The PR5660 rewrite cannot create this typed inverse commutator

For any typed old program P and valid rewritten program Q satisfying the exact PR5660 edit premises, the edit cannot create an inverse-commutator motif whose middle role has the absolute dimension-zero to dimension-nine route with MOVE increments `(1,2,2,2,2)` and four interior anchor dimensions `1,3,5,7`. The proof covers a motif using an inserted anchor and a survivor-anchor motif made admissible solely by deleting an old observer barrier. It permits extra middle-role contacts at the unchanged endpoints. The [proof](PROOF.md) gives the quantified statement and all premises.

This is a conditional source-delta exclusion. It makes the proposed occurrence lookup for this exact historical delta unnecessary. It supplies no whole-word census, equality with the old PR5650 payload, absence of all commutators, paid-profile improvement, κ gain, full native replay or proof-kernel verification. The elementary commutator identity is classical. The contribution is the source-bound exclusion for the specified edit and typed route.

## Sources and evidence

The historical object is [PR5660](https://github.com/CrocSwap/integer-mult-bounds/pull/5660) at immutable head `3b0b4f37d5005f381ed9cfcccebfbe1ab35c71aa`. The four small text files in [inputs/](inputs/) are unmodified copies of that publication's constructor, witness, author proof and source manifest. [SOURCES.json](SOURCES.json) records their immutable paths, content hashes and Git blobs. The copied Python file is read as source text; this package does not import or run it. The copied author proof and manifest preserve provenance context; their construction/replay claims are author evidence rather than checks performed by this package.

| Layer | Evidence | Status and limit |
| --- | --- | --- |
| Text custody | Copied bytes match the SHA256, Git-blob and length records in the supplied authenticated PR5660 packet. | Recomputed as packaging bookkeeping; no new network authentication. |
| Declared source contract | Constructor lines 20–21, 24–58 and 92–123, plus the complete witness. | Read as text. These declare the skeleton, monotone public paths, fixed edit, frame bases and isolation predicate. |
| Mathematical statement | The two exhaustive incidence cases in [PROOF.md](PROOF.md). | A universal conditional paper argument. A supplied independent local review accepted this argument; review of the final publication bytes is still required. |
| Actual published programs | The PR5660 package describes source composition and author replay. | Neither old nor new WORD was decoded here. The typed-P/Q premise and actual-word instantiation have not been independently replayed by this package. |
| Whole-word coverage | Existing public discussion describes related scalar reassociation and broader local screens. | The complete matcher domain and its binding to final PR5660 remain unknown. This result does not close that question. |

This is an unregistered static proof package. Its custody manifest uses the explicitly named package-specific schema in `SOURCES.json`; it is not a declaration that the optional generic research-package runner has accepted metadata or run a verifier. No `VERIFY.json`, task-card claim or CI-ready hook is supplied.

No occurrence search, scientific numeric calculation, source import, constructor, native interpreter, endpoint replay, old-word comparison or math test was executed to prepare this package. No runnable checker, test receipt or `RESULT.json` is supplied. The paper proof does not need a scientific execution receipt. Any future automated qualification should report custody and source-contract checks separately from the theorem and actual-word validity.

## Attribution and nearby work

Ali Romman's [PR5660](https://github.com/CrocSwap/integer-mult-bounds/pull/5660) supplies the exact four-gate edit. Its constructor credits the A2 identity in [PR3998](https://github.com/CrocSwap/integer-mult-bounds/pull/3998) and [PR4019](https://github.com/CrocSwap/integer-mult-bounds/pull/4019), zxv's paid construction [PR5643](https://github.com/CrocSwap/integer-mult-bounds/pull/5643), and the three helper relations in [PR5644](https://github.com/CrocSwap/integer-mult-bounds/pull/5644). The retained source manifest additionally pins [PR5627](https://github.com/CrocSwap/integer-mult-bounds/pull/5627), [PR5650](https://github.com/CrocSwap/integer-mult-bounds/pull/5650) and [PR5651](https://github.com/CrocSwap/integer-mult-bounds/pull/5651). Their P104, native-chart, helper, caller, controller and compiler lineage remains credited through those retained sources.

Ali Romman's [Discussion5600 scope statement](https://github.com/CrocSwap/integer-mult-bounds/discussions/5600#discussioncomment-19184345) already describes corrected noncommuting transvection reassociation and disclaims novelty of the elementary identity. Later [boundary-resynthesis work](https://github.com/CrocSwap/integer-mult-bounds/discussions/5600#discussioncomment-19187633) and the [release of bounded scalar screens](https://github.com/CrocSwap/integer-mult-bounds/discussions/5600#discussioncomment-19188254) are relevant prior discovery work. This package neither repeats those claimed screens nor establishes what they exhausted. Its result is the two-case typed exclusion under the fixed published edit.

The later [PR5678](https://github.com/CrocSwap/integer-mult-bounds/pull/5678) construction at `af814f6f3c477fdd13b8f04380a33cf32004966b`, identified by the parent coordinator, is outside this theorem's edit premises. This exclusion does not transfer to that successor. No successor source or artifact is an input here.

Prepared for the donor's contribution with substantial OpenAI Codex assistance, including the local independent paper review. Source notices and the Apache-2.0 terms are retained; see [NOTICE](NOTICE). There is no human-independent scientific acceptance claim.

## Open next questions

1. **Can the exact historical words instantiate the typed premise?** This would connect the universal conditional statement to a fully replayed source object. The first step is authenticated old/new word custody and the published complete typing/replay procedure, under a separately scoped request. This package supplies no word payloads and does not require that stronger claim.
2. **What did the prior scalar screens cover?** A source-pinned matcher or tested-domain receipt should specify coefficient/role conditions, protected corridors, chart choices, paid-path eligibility and exact tested head. This can resolve duplication without another blind word scan. The public statements alone leave it open.
3. **Does a successor satisfy a related exclusion?** Start by identifying its actual edit and contact premises, then seek a new proof or bounded question. The PR5660 theorem provides no inherited result for a changed word or schedule.

The smallest useful follow-up for this submission is review of the final proof and source-premise bindings. No further occurrence lookup is justified for the exact delta class proved empty here.
Loading
Loading