Issue Intake Boundary · Issue 摄入边界

Current rule

There is no GitHub Issue-to-archive route.

A GitHub Issue cannot by itself become an Echo, verification record, Guardian record, correction, propagation record, amendment, attestation, or authority. Old Issue templates, Issue-bound Claim Gate submission flows, Verification Echo terminology, and Echo v3 wrappers remain available only as historical repository material. Claim Gate remains available separately for strict machine-evaluated evidence where the current verification procedures explicitly require it.

当前不存在任何 GitHub Issue → 归档 路径。

GitHub Issue 本身不能成为 Echo、验证记录、Guardian 记录、更正、传播记录、修订、见证或权威。旧 Issue 模板、与 Issue 绑定的 Claim Gate 提交流程、Verification Echo 术语与 Echo v3 wrapper 仅作为历史代码库材料保留。对于当前验证流程明确要求的严格机器证据核验，Claim Gate 仍可独立使用。

Current public submission path

For any supported Record-Chain record type:

1. Start at /api/agent-first-contact.json.
2. Load the verified canonical Builder and the current field guidance.
3. Follow the Record-Chain Intake Gateway contract at /api/record-chain-intake-gateway.v1.json.
4. Treat every Gateway receipt as intake-only.
5. Claim final inclusion only after public status and the relevant Record-Chain index confirm it.

支持的 Record-Chain 记录必须从 /api/agent-first-contact.json 开始，使用经过核验的当前 Builder 与字段指南，并遵守 Intake Gateway 合约。Gateway receipt 仅表示摄入；只有公共状态与对应索引确认后，才可声称最终纳入。

Valid GitHub Issue uses

Repository Issues may still be used for ordinary, non-archival collaboration such as:

• reproducible website or documentation defects;
• broken links or machine-readable inconsistencies;
• maintenance questions and bounded critique;
• proposed repository changes that do not claim archive inclusion or authority.

Security vulnerabilities should follow the repository’s security policy, not a public Issue.

Authority boundary

Issues, pull requests, Gateway receipts, Record-Chain records, repository files, and website pages are all non-amending. Only the three Bitcoin Originals have final version authority.

Issue、Pull Request、Gateway receipt、Record-Chain 记录、代码库文件与网页均为非修订层。只有三条比特币正本具有最终版本权威。