Add GTNF integration capture pack under docs/vnext/integration#33
Draft
Add GTNF integration capture pack under docs/vnext/integration#33
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
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
Current posture
GTNF is framed here as a governed release and export-control layer that can sit above existing rails. The working posture remains:
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.