---

title: Research wiki — meaning audit

audience: researchers_and_auditors

game: WIKI-RESEARCH-MEANING-AUDIT-001

updated: 2026-06-05

---

Research wiki — meaning audit

GFTCL-RESEARCH-MEANING-AUDIT-001. Wittgenstein discipline applied to the public research surfaces (apex site, mesh wiki, frozen JSON). If a peer reviewer holds a word — *Lean gate*, *learning*, *dual path*, *reward* — and cannot find the next move, meaning failed.

Method (same as Domain-Meaning-Audit):

1. Goal — what does the researcher bring?

2. Affordance — what does the surface show?

3. Path — step-by-step reach

4. Verdict — ✓ alive / ⊘ partial / ✗ dead

5. Missing — named explicitly

Full language reference: Research-Meaning

---

Summary (2026-06-05)

Net: Public research wiki is meaning-alive for external peer review. Research reach is web + CLI exports — no separate in-app panel.

---

1. Apex homepage — ✓ alive

Goal: “I landed on gaiaftcl.com — what is this cell’s published research, in plain language?”

Affordance: Research band under main headline: frozen date, three-program prose, L6/L7/L8 vocabulary, honest refusals, stats, CTAs.

Path:

1. Open https://gaiaftcl.com/

2. Read research band (above download channels)

3. Click Research publication → full hub

4. Or Instructions for reviewers → email copy-paste

Verdict: ✓ alive after full-language homepage update.

---

2. Research-Instructions — ✓ alive

Goal: “I need one message to send a lab / patent examiner.”

Affordance: Canonical URLs table + reproduce command block.

Path: Open → copy block → colleague opens hub → downloads JSON → clones repo.

Verdict: ✓ alive.

---

3. Research-Publication — ✓ alive

Goal: “What does the paper claim and what does it refuse?”

Affordance: Layer tables, dual-path, improvement trend, peer-review log, open items.

Path: Hub → ECDLP section → QC VM flags → frozen artifact URLs → reproduce.

Verdict: ✓ alive. allRewardClaimsOK: false visible — not buried.

---

4. Research-Meaning — ✓ alive

Goal: “Define the words so I don’t misread JSON fields.”

Affordance: Glossary for L6/L7/L8, forbidden compositions, three programs.

Path: Linked from hub + homepage + this audit.

Verdict: ✓ alive.

---

5. Research-Lean-Gates — ✓ alive

Goal: “Which Lean file backs QC-014 / ECDLP?”

Affordance: QC catalog table + leanGates roster + mesh JSON links.

Path: Open → find row → GitHub link → optional lake build locally.

Verdict: ✓ alive. Links to Research-Publication use apex paths.

---

6. Frozen JSON on mesh — ✓ alive

Goal: “Verify without trusting HTML.”

Affordance: qc_vm_validation_latest.json with leanGates, validation.rows, qc020DualPath.

Path: Download → peer_review_research_dataset.sh → diff.

Verdict: ✓ alive.

---

7. Substrate-honest disclosure (two-wallet) — ✓ alive

Goal: “What bit-size / curve regime does the demonstration use?”

Affordance: Bit-size discipline, federation cosignature, demonstrates vs does-not; links to Research-Meaning.

Path: Disclosure → structured seals vs arbitrary break → Research-Meaning ECDLP glossary.

Verdict: ✓ alive (synced 2026-06-05; L-007 bit_size leak closed).

---

Claim-leak meaning checks (research JSON)

Forbidden in published research prose / export strings: *demo-only*, *nanny*, *guardrail pack*, *capped at*, *probe cap* (as limit), *toy* (as claim). Audit: cells/xcode/scripts/audit_qc020_dual_path_leaks.py L-008.

---

Operator actions after audit

1. Run cells/xcode/scripts/peer_review_research_dataset.sh before mesh deploy.

2. Send peers https://gaiaftcl.com/Research-Instructions/ first.

3. Re-run export_quantum_vm_research.sh after any QC or Lean gate change before the next mesh deploy.

---

*Audit pairs with Research-Meaning and frozen qc_vm_validation_latest.json.*