Gate 6 registry access policy

[geraldarthurdavis]

Summary

• derive organization BTD posture from registry ownership and read-license rows
• require owner-read or licensed-read registry evidence for MCP admission and ChatGPT App write-capable tools
• add source-readable access-policy templates and test coverage for owner-read, licensed-read, derivative use, redistribution, confidentiality, dispute, and takedown posture
• align Auxillaries and interface documentation around registry/range/license/proof posture

Validation

• pnpm -C packages/btd test
• pnpm -C packages/btd run typecheck
• pnpm -C packages/orm build
• pnpm -C packages/orm exec jest --runTestsByPath src/tests/btd-registry.test.ts --runInBand
• pnpm -C packages/chatgptapp exec jest --runTestsByPath src/tests/tools.test.ts --runInBand
• pnpm -C packages/chatgptapp exec tsc -p tsconfig.json --noEmit --pretty false
• pnpm -C packages/executions-mcp/src/mcp-server exec jest --config jest.config.mcp.js --runTestsByPath src/tests/unit/auth.test.ts --runInBand
• pnpm -C packages/executions-mcp/src/mcp-server run type-check
• pnpm -C uapi exec jest --runTestsByPath tests/auxillariesWalletPane.test.tsx --runInBand
• pnpm -C uapi exec tsc --noEmit --pretty false
• node --test scripts/verify-v28-pipeline-readback.test.mjs
• pnpm run check:canon-posture-drift
• git diff --cached --check
• staged diff credential scan for the previously exposed staging secret patterns

Known pre-existing failure

• pnpm run check:spec-quality still fails in the V27 promoted spec-family subcheck because the current promoted V27 family lacks required promoted-family status/catalog sections. Gate 6 changes only V28 draft posture and registry access implementation; the V28 canon drift/readback validations pass.

[vercel]

Deployment failed with the following error:

There is no GitHub account connected to this Vercel account.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
engi-uapi	Ready	Preview, Comment	May 19, 2026 9:43am

[chatgpt-codex-connector]

💡 Codex Review

https://github.com/engineeredsoftware/ENGI/blob/0ab88c0aeeb8d750f3b625fd11fc2985545d7154/packages/orm/src/models/btd-registry.ts#L86-L90
Derive current ownership before granting owner-read

In a rights-transfer scenario, this query returns every historical inbound btd_ownership_events row for the wallet. Since that table also records transfers with from_wallet_id and keeps the original mint/allocation event, a wallet that later transferred the AssetPack range away will still be returned here, and the new MCP read-access path grants owner_read from that stale row. Please derive current range ownership by accounting for outgoing/latest transfer events before using these rows for read admission and organization holdings.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".