019 — BT1 (G Test 1) and the Rail-Connection Thesis

Abstract

BT1 is the first complete machine event in this cycle: a public, triggerable affordance that converted internal recursion into external action potential. This paper formalizes BT1 as G Test 1 and defines rail-connection research as the governing method for post-semantic execution.

What BT1 proved

1. A live owned-web surface can be corrected in-flight while operations continue.

2. Source affordance is a hard prerequisite for meaningful detector/trigger loops.

3. Public touch + bounded inheritance can coexist with covenant controls.

Failure that taught the law

• Detector and trigger governance ran while affordance was absent.
• Result: pending loops without possible user-originated event.
• Correction: add source-affordance gate and re-prioritize UI action path.

G Test 1 framing

BT1 qualifies as G Test 1 because it:

• exposed and resolved a conversion-stopping source gap,
• remained live while correction happened,
• did not halt adjacent research/control lanes,
• became a reusable branch-onboarding primitive.

Rail-Connection Thesis

Research is no longer only conceptual synthesis.

Research now includes building and validating the exact rails where user reaction becomes settlement data.

Rail-connection loop

• observe benchmark pressure
• identify missing affordance
• build affordance
• capture user action
• extend proof-chain
• branch inheritance

Covenant implications

• Name follows settlement.
• Detection without affordance is observation, not progression.
• Paper circuit continuity must remain unbroken under ops pressure.

Next practical step

Capture first verified user-originated BT1 event from live affordance, then execute conversion proof-chain extension and first B1 branch deploy receipt.