GaiaFTCL v2 — sovereign mesh (keyed distribution)¶

Channel: v2-sovereign-mesh · App channel key: v2-sovereign
DMG: GaiaFTCL-v2-Sovereign.dmg — separate from v1; not aliased to GaiaFTCL-latest.dmg

Rebuild in progress. The mesh may still serve an older v1-era DMG at legacy paths. The gated v2 build (embedded operator public key + activation panel) ships only after the current operator rebuild completes and publishes new bits + SHA-256 to /downloads/. Check version.json channels.v2.build_status and the sidecar before you mount.

v2 is the live substrate build: mainnet mining narrative, QCF-004 parent circuits, research.v4 peer validation, and L7 disposition (learning | realized | idle). It does not ship v1 toy demonstration shortcuts or the v1 narrator “god-rail” guardrail pack as operational bypasses.

Full gate spec: v2 activation gate.

v1 vs v2 (operator table)¶

	v1 public demo	v2 sovereign mesh
Download	Open on apex	Email gaiaftcl@gmail.com → DMG when issued
First run	Open app	Paste email access code (Mac-bound optional)
Revocation	N/A	Operator list at `/downloads/v2_revoked_codes.json`
DMG name	`GaiaFTCL-v1-Public-Demo*.dmg`	`GaiaFTCL-v2-Sovereign*.dmg`
Toy Shor / demo wallets	Yes (labeled demonstration)	No — live paths only
BTC mining circuit	Documented in wiki; demo DMG	`QC-020-CIRCUIT` + BTC mining narrative map
Research export	Optional	`gaiaftcl.qc_vm.research.v4` + peer scripts

Request v2 access¶

v2 is not a public hotlink.

Email gaiaftcl@gmail.com — include your Mac binding hash from the activation panel if you want a machine-locked code.
Receive a signed access code (gftcl2.v1.…) and the v2 DMG by reply when the rebuild is published.
Verify SHA-256, mount, launch, paste code at Activate GaiaFTCL v2.

We never attach v2 to the v1 demo filename. Two DMGs, two manifests, two SHA-256 files.

Runtime activation gate¶

The v2 DMG itself is keyed delivery. The v2 app also refuses to load anything past this panel until you paste an operator-issued access code:

v2 activation panel on first install

The code is Ed25519-signed by the operator, bound to your Mac's serial-derived hash, and verified offline. Once it activates, the wallet UI loads:

Wallet UI after activation

End-to-end walkthrough with operator + recipient commands, refusal-mode table, and revocation: v2 activation gate.

BTC mining ↔ circuit (v2)¶

Human mainnet pipeline (seven steps) is exported under circuitGraphs[].narrativeSteps for QC-020-CIRCUIT:

GBT → coinbase → QC-002 Grover law → QC-020-U preimage → QC-020-M measure → submitblock → L7 reward

Seal	Meaning
`graphOK`	QCF-004 edges discharged
`narrativeCompleteOK`	All narrative steps `wired`
`rewardLayerStatus: learning`	Miner running — not audit failure
`allRewardClaimsOK`	Only when L7 realized

Full map: BTC mining circuit narrative.

Validation (v2)¶

cells/xcode/scripts/registry_consistency_check.sh
cells/xcode/scripts/export_quantum_vm_research.sh
python3 cells/xcode/scripts/validate_research_v2_peer.py
STRICT_COMPOSITION=1 STRICT_NARRATIVE=1 cells/xcode/scripts/leak_audit_pass.sh
swift run -q M8QC020OnChainRewardEval

Build (operator — after pubkey embed)¶

gaiaftcl admin v2-keygen          # once
gaiaftcl admin show-v2-pubkey     # embed in V2ActivationGate.embeddedPublicKeyHex
bash scripts/build_dmg.sh --channel v2-sovereign --version 2.0.0

Publish only to the v2 manifest slot — never overwrite v1 or GaiaFTCL-latest.dmg.

Federation cosignature: pending

This page is not yet in the signed manifest. Run gaiaftcl wiki sign --all.