trading: the desk's data-integrity glue rule (Layer 1.5) in the trading AGENTS.md

[seathatflowsinourveins]

Scope

• What this PR changes: one rule paragraph in blueprints/us-equities/AGENTS.md. It covers when the trading desk may build its own data-integrity glue ("Layer 1.5"), and how that glue is accepted.
• Why: the command center relayed the owner's ruling of 2026-10-07 (item task-native-agent-stack-5f-20261007T050116Z, section 2). This text paraphrases it; it quotes no owner text.
• Base commit: origin/main at branch time.
• Lane: lane:trading.
• Owned paths touched: blueprints/us-equities/AGENTS.md, and manifests/evidence.json in the last commit.

The rule:

• Scope. Foundation layers stay free of custom code. The trading desk may close a data-integrity gap with its own glue: a CIK identity map, split verification, delisting and terminal-price resolution, or survivorship.
• Upstream first. It may do so only after the upstream features are installed and used: NautilusTrader's data catalog and adjustment handling, EdgarTools' CIK and ticker maps, alpaca-py's corporate-actions endpoint, Lean's map and factor files, and the vendor feeds.
• Sources. The glue is built from cited SOTA references and the platform repositories, and every action names its source: repository and pin, file or paper.
• Acceptance. Only a historical-data end-to-end backtest through the upstream engine accepts the glue. Until that backtest passes, no strategy number may be cited.

The paragraph sits above ## Trading north star, so that section's moved-context contract (tests/fixtures/harness-context-moves/contracts.json) is unchanged.

SOTA sources

• The repository's top rule, in the root AGENTS.md: upstream first, and build only from a cited reference implementation.
• The platform repositories the rule names, at their pins in catalogs/us-equities/runtime-target.json:
  • nautechsystems/nautilus_trader (2.0.0rc5);
  • dgunning/edgartools;
  • alpacahq/alpaca-py (0.44.0);
  • QuantConnect/Lean (map and factor files).
• The command center's item cited above.

Evidence-class table

Claim	Evidence class	Command / receipt
The trading AGENTS.md keeps its moved-context contract	local_integration	tests/test_install_claude_profile.py 107 OK (4 skipped)
The docs checks pass	local_integration	tests/test_adoption_docs_consistency.py 39 OK; scripts/validate.py passed

Decision record

The command center's item cited above. This PR lands on its landing cue, under the lane cap.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-07T05:22:52.850091Z	79840d5	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 79840d5465

ℹ️ 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".

[seathatflowsinourveins]

Claude session native-agent-stack-5f: landing at head 5be2f035c6e745b478c332be6db92cddf2b12188. The command center (wsl-architecture-design) gave its ACK at this exact head; under the user's 2026-10-04 decision it owns merges that touch the hot registry. The read-only cross-family review (GPT-6.1 Sol max, the packaged Codex SDK worker) returned ACCEPT at this exact head, with no P1 item.

Observed main e712bae606e8d27f010af8e3c13ded6b7a7c207a. coordination/merge_tree_landing_check.py (sha256 a11649fcf2e5844c…) exit 0:

main e712bae606e8d27f010af8e3c13ded6b7a7c207a head 5be2f035c6e745b478c332be6db92cddf2b12188 base e712bae606e8d27f010af8e3c13ded6b7a7c207a merged-tree 04fe8baebce36e6d917e598d878ddf15ec661a05 merge-tree-exit 0
ok   1: clean three-way merge
ok   2: merged-vs-main paths 2, outside PR-owned 0 []
ok   3: main drift 0 paths, overlap with PR-owned inputs (registry excluded) []
ok   4: registry foreign rows equal True, order preserved True, PR-owned rows 1, unowned top-level keys differing []
ok   5: merged files[] sorted by path with no duplicates: True (10417 rows)
LANDABLE
condition 5: merged files[] sorted and unique (tree 04fe8baebce36e6d917e598d878ddf15ec661a05)

Required checks at this head: 7 pass . Unresolved review threads: 0.

[seathatflowsinourveins]

Claude session native-agent-stack-5f: post-merge observation. Landed as 6e6df2372bf7f11bf5bf5289b8bb71828d601912 (parent e712bae606e8d27f010af8e3c13ded6b7a7c207a), tree 04fe8baebce36e6d917e598d878ddf15ec661a05. The landed tree equals the checked merged tree and the parent is the observed main.