Skip to content

Add GTNF integration capture pack under docs/vnext/integration#33

Draft
mdheller wants to merge 7 commits intomainfrom
feature/gtnf-capture-pack-20260409-clean
Draft

Add GTNF integration capture pack under docs/vnext/integration#33
mdheller wants to merge 7 commits intomainfrom
feature/gtnf-capture-pack-20260409-clean

Conversation

@mdheller
Copy link
Copy Markdown
Member

@mdheller mdheller commented Apr 9, 2026

What this PR does

Adds a focused GTNF capture pack under docs/vnext/integration/gtnf/ so the work is reviewable inside the TriTRPC repository without mixing in unrelated runtime artifacts or branch-local noise.

Included in this capture

  • canonical GTNF index and positioning summary
  • concise GTNF white paper capture
  • concise ASI / SingularityNET integration manual
  • math-forward external overview
  • validation summary
  • runtime validation protocol summary
  • first Cosmos / IBC runtime summary
  • minimal runtime manifest for the IBC handoff path

Why this shape

This is intentionally a curated capture subset, not the full local artifact dump.

The goal is to preserve the doctrine, integration posture, validation posture, and first runtime target inside the repo in a way that is easy to review and discuss publicly.

Explicitly not claimed here

  • no live Hermes validation result yet
  • no exact Hermes tag lock yet
  • no observed ASI(FET)+MPE payment trace yet
  • no claim that this repo subset is the full GTNF local corpus

Current posture

GTNF is framed here as a governed release and export-control layer that can sit above existing rails. The working posture remains:

  • agree with live rails where they already work
  • wrap them with stronger proof and policy boundaries
  • extend them where witness, contradiction, reserve, and export control are missing
  • defer substrate rewrites until validation proves them necessary

Follow-on work

The next real hardening step remains runtime validation in a network-capable environment, especially the first Hermes / IBC pass against the locked Classic baseline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant