You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Derive organization BTD posture from registry ownership and read-license rows, require owner-read or licensed-read evidence for MCP and ChatGPT App write admission, and cover the registry access-policy templates in BTD tests.
Keep Terminal-facing copy on registry, range, ownership, license, and proof posture without price-appreciation, dividend, copyright-transfer, or marketplace-royalty framing.
- Terminal copy avoids price-appreciation, dividend, copyright-transfer, or marketplace-royalty promises.
677
677
678
+
Implementation posture:
679
+
680
+
- Organization `$BTD` posture is a registry projection. Read models must collect member wallet bindings, then read ownership events and read-license rows from the BTD registry. Aggregate compatibility balances may remain contextual but must not admit organization, MCP, ChatGPT App, or read-license actions.
681
+
- MCP admission may require current owner-read or licensed-read evidence for one or more AssetPacks. Deprecated aggregate holding gates must fail closed and point callers to registry-derived read-access requirements.
682
+
- ChatGPT App write-capable connected-interface tools must require explicit user confirmation and typed read-access evidence carrying AssetPack id, wallet id, owner-read or licensed-read decision, policy hash, and reason.
683
+
- Access-policy templates must remain source-readable and test-covered for owner-read, licensed-read, derivative use, redistribution, confidentiality, dispute, and takedown posture.
684
+
- Active Terminal and Auxillaries copy must describe registry, range, ownership, license, and proof posture without implying price appreciation, dividends, copyright transfer, or marketplace royalties.
685
+
678
686
### Gate 7: Terminal Operations And Testnet Readiness
0 commit comments