[hq/security] Define release gates before real-value public-network pilot work

[FlowmemoryAI]

Objective

Define explicit release gates before any PR claims or enables real-value public-network operation, token launch/tokenomics, open validators, formal cryptographic review, production bridge behavior, or real-funds bridge readiness.

Context

Draft PR #129 introduces a real-value pilot goal pack. That PR may remain prompt/launcher-only, but it must not be treated as approval to merge public-network or real-funds functionality without accepted gates and evidence.

Acceptance criteria

• Document the allowed scope for a capped owner-only pilot versus prohibited public readiness claims.
• Define required approvals and evidence before any Base public-network observer, supported-asset deposit, bridge release path, token launch, DEX liquidity/swap smoke, or validator/open-network claim can merge.
• Name required local checks, CI checks, no-secret scans, emergency stop/revoke evidence, cap enforcement evidence, and rollback/recovery evidence.
• Require PR bodies to list allowed folders, forbidden folders, exact checks run, issue linkage, and unresolved blockers.
• Require source-of-truth docs to keep production L1/mainnet, public validators, tokenomics, audited cryptography, and real-funds bridge claims out of scope until the release gates are accepted.

Out of scope

• Implementing contracts, relayers, wallets, runtime, dashboard, or hardware code.
• Approving production public L1 launch, tokenomics, open validators, audited cryptography, or production bridge custody.

[FlowmemoryAI]

HQ update after PR #132 audit:

• Draft PR [codex] Add real-value pilot HQ gate #132 adds docs/FLOWCHAIN_REAL_VALUE_PILOT.md, flowchain:l1-e2e, and flowchain:real-value-pilot:e2e on agent/real-value-pilot-hq.
• Completion audit is recorded at docs/agent-runs/real-value-pilot-hq/COMPLETION_AUDIT.md.
• Current origin/main still lacks both new scripts, so the full goal is not complete.
• npm run flowchain:real-value-pilot:e2e fails clearly by default until dedicated proof commands exist for contracts, bridge relayer, chain runtime, wallet/operator, control-plane/dashboard, and ops.
• npm run flowchain:real-value-pilot:e2e -- -AllowIncomplete passes as a coordination report.
• Local npm run flowchain:l1-e2e and npm run flowchain:product-e2e currently fail under local Slither in contracts:hardening on existing BaseBridgeLockbox.releaseNative findings; owner is contracts/static-analysis policy.
• PR [codex] Add real-value pilot HQ gate #132 CI is green and the PR remains draft.

Next release-gate need for this issue: define the accepted boundary and required approvals before any owner pilot work can move beyond capped validation.

[FlowmemoryAI]

HQ update from agent/l1-loop-hq-review:

This branch now drafts the #130 release-gate criteria in docs/PRODUCTION_READINESS_CHECKLIST.md and tightens matching blocked-claim language in docs/MARKETING_CLAIMS_GUARDRAILS.md.

The draft gate requires, before any blocked real-value/public-network claim can merge:

• accepted GitHub gate issue with scope, owners, rollback authority, and go/no-go reviewer;
• PR body with allowed folders, forbidden folders, exact checks, issue linkage, unresolved blockers, and public-network/custody/bridge/token/validator/crypto-review impact;
• local and CI evidence, no-secret scan evidence, emergency stop/revoke evidence, cap enforcement, rollback/recovery evidence, and source-of-truth doc updates.

Checks from this HQ branch after the doc update:

node infra/scripts/check-unsafe-claims.mjs
git diff --check

Both passed; git diff --check emitted only Windows line-ending warnings.

This is a draft gate, not release approval. Keep #130 open until reviewers accept the gate text through PR review or a follow-up decision.

[FlowmemoryAI]

HQ branch update from PR #132 (agent/real-value-pilot-hq, commit d1198ff):

Added a release-gate boundary proposal in docs/FLOWCHAIN_REAL_VALUE_PILOT.md#release-gate-boundary that maps required evidence and approval owners for:

• Base public-network observer reads;
• supported-asset deposits;
• bridge release/recovery;
• local credit application;
• control-plane/dashboard display;
• out-of-scope token launch/tokenomics/broad DEX/open-swap claims;
• out-of-scope open validators, public L1/mainnet readiness, audited cryptography, and production bridge custody.

Verification after adding the boundary:

• node infra/scripts/check-unsafe-claims.mjs passed.
• git diff --check passed with Windows line-ending warnings only.
• npm run flowchain:real-value-pilot:e2e -- -AllowIncomplete passed as an incomplete report with the expected six missing subsystem proof commands.

Do not close this issue yet: the boundary is branch-local until PR #132 is reviewed and merged.

[FlowmemoryAI]

Closed by merged PR #132 at merge commit 14f378b7f2dee9bfd29aec691ebda41e2b6fa101.

Post-merge evidence:

• origin/main:docs/FLOWCHAIN_REAL_VALUE_PILOT.md contains the capped owner-pilot release-gate boundary.
• origin/main:package.json contains flowchain:l1-e2e and flowchain:real-value-pilot:e2e.
• node infra/scripts/check-unsafe-claims.mjs passed on the merged main-equivalent tree.
• git diff --check passed on the merged main-equivalent tree.
• npm run flowchain:l1-e2e passed on the merged main-equivalent tree; report path devnet/local/full-smoke/flowchain-full-smoke-report.json.
• npm run flowchain:real-value-pilot:e2e -- -AllowIncomplete passed as an incomplete coordination report.
• npm run flowchain:real-value-pilot:e2e fails clearly with the expected six missing subsystem proof commands.

The release boundary is now on main. The owner pilot remains no-go until issues #133, #138, #134, #136, #137, and #135 land and the final pilot gate passes without -AllowIncomplete.

[FlowmemoryAI]

HQ post-merge reconciliation after PR #132 merged to main as 14f378b at 2026-05-14T02:19:55Z.

What is now true on origin/main:

• docs/FLOWCHAIN_REAL_VALUE_PILOT.md#release-gate-boundary exists on main.
• npm run flowchain:real-value-pilot:e2e -- -AllowIncomplete passes as a coordination report.
• The strict npm run flowchain:real-value-pilot:e2e fails closed with the expected six missing subsystem proof commands: contracts, bridge relayer, runtime, wallet/operator, control-plane/dashboard, and ops.
• node infra/scripts/check-unsafe-claims.mjs passed.
• git diff --check passed with Windows line-ending warnings only.

This means main now has a release-boundary baseline, but this issue should stay open until reviewers explicitly accept the gate as sufficient or add any missing approval requirements. The owner pilot remains no-go until the strict pilot gate passes without -AllowIncomplete.

[FlowmemoryAI]

HQ reconciliation note: GitHub source of truth now shows this issue closed after PR #132 merged. The release-boundary baseline is on main at merge commit \14f378b. Remaining pilot work is not release-approved; strict owner-pilot readiness is still blocked by proof-command issues #133, #134, #135, #136, #137, and #138 and by the strict
pm run flowchain:real-value-pilot:e2e\ gate passing without -AllowIncomplete.