Successor topology

Ownership does not move. Purpose does not move. What moves is the body that carries the work.

Prompted LLC
  owns and governs
Ubiquity Federation Canonical
  purpose and principles
        |
        v  first estate-scale operational body
OperationTorque
        |
        v  Harpoon into federation-scale Canonical
Ubiquity Federation / Canonical V1
        |
        v  successor-by-Harpoon
Canonical V2

Canonical V2 is therefore the same sovereign Ubiquity Federation, the same Prompted LLC ownership, the same root identity and telos, with a new native implementation body, fresh current-world actuality, and fresh runtime, model and capability standing.

A hard-forked sibling system has its own body and its own future. Canonical V2 owes it no parentage, support, replatforming, round-trip, bridge, convergence, upstream parity, or runtime compatibility.

A sibling does not enter V2's constitutional lineage merely because selected Canonical, Mount, CSL, or other Ubiquity mechanics were used to seed and construct it. When an external implementation is the strongest available takeoff surface, the provenance belongs on the artifact:

source_artifact:
  system: <external sibling system>
  exact_ref: <commit/path/hash>
  use:
    - comparative_baseline
    - implementation_springboard
    - negative_control
  standing_transferred: false
  compatibility_required: false
  support_obligation_created: false

That lets V2 leap past an external implementation in function and scope without erasing where the useful implementation appeared, and without making that system part of what V2 must carry. A generalized business configuration may learn from mechanics proven elsewhere. The external implementation is not the business configuration.

A Harpoon transformation mode for succeeding a work body without inheriting its runtime.

FROG_LEAP(source, target) =
  preserve:
    purpose
    semantic identity
    invariants
    apophatic boundaries
    scars
    proofs
    attribution
  permit replacement of:
    implementation
    UI
    provider
    model
    schemas
    repository structure
    runtime topology
    domain vocabulary
  require:
    declared advancement vector
    exact baseline comparison
    visible regressions
    actual-work proof
    human admission
  default:
    authority transferred     = false
    support obligation        = false
    compatibility required    = false
    legacy runtime dependency = false

A frog leap does not need to beat the source on every scalar. It must name the dimensions being advanced and may not conceal the dimensions that regress. The declared advancement vector for V2:

• work usability
• functional breadth
• world-model fidelity
• causal-loop closure
• source/currentness integrity
• authority precision
• provider and model optionality
• local-model sovereignty
• human agency
• correction reach
• rollback and restore
• training/evaluation quality
• surface parity
• cross-domain expression
• operational simplicity

OperationTorque was already a broad, real-work operating body: Fusion Core, audit-first learning, real-time ingestion, provider orchestration, domain adapters, Boris execution, Epitaphs, Ghost Chorus, conformations, tics, agent boundaries, an Observatory, and actual meeting, podcast, solar and intelligence work. Its transform law is stated in its own source — WRAP + PROJECT + GATE, not replace — and becomes a source principle rather than a demand to preserve exact dimensions.

No maintenance commitment on the old runtime is implied by any row of this table.

Pre-genesis may inspect, apprehend, source-lock, port, compile, simulate, test and restore. The first real client or external effect governed by the V2 kernel opens V2:T0.

That eliminates the shadow-polity problem, where a system performs months of actual work under PG-* while claiming not to have started. Status: candidate rule. Tic 0 has not been admitted.

Current head is an observer-indexed reading, not a global fact. Each observing surface — canonical source, human mobile, human desktop, accessibility, agent contract, route registry, restatement registry, static crawler — reports what it reports, at a time, from a runtime. Divergence is recorded with its cause rather than silently corrected. The measured register lives at /head-conformation.json, generated by the discovery-parity gate.