FlowmemoryAI · FlowmemoryAI · May 13, 2026 · May 13, 2026 · May 13, 2026
diff --git a/AGENTS.md b/AGENTS.md
@@ -26,7 +26,7 @@ These instructions apply to every agent, assistant, script, and human operating
 - Use `docs/PR_PROCESS.md` for branch naming, draft PRs, merge order, dirty worktrees, and issue closing.
 - Use `docs/DAILY_HQ_RUNBOOK.md` for morning review, triage, monitoring, and handoff.
 - Use `infra/scripts/status-report.ps1` for read-only local worktree, PR, and issue status.
-- The immediate major milestone is the Rootflow V0 and Flow Memory V0 launch core. Do not reinterpret that as approval for production deployment.
+- The immediate major milestone is the FlowChain private/local L1 testnet package for second-computer validation, with Rootflow V0 and Flow Memory V0 kept green as the baseline. Do not reinterpret that as approval for production deployment.
 
 ## Engineering Rules
 

diff --git a/README.md b/README.md
@@ -61,7 +61,7 @@ FlowMemory is managed as a multi-agent program. The management layer is part of
 - `docs/MARKETING_CLAIMS_GUARDRAILS.md`: allowed and blocked launch claims for docs and marketing
 - `infra/scripts/status-report.ps1`: read-only local worktree, PR, and issue status report
 
-Immediate major milestone: keep the Rootflow V0 and Flow Memory V0 launch core green. This means local contracts/tests, FlowPulse fixtures, Uniswap swap-derived memory-signal fixtures, Rootflow transitions, Flow Memory schemas, verifier reports, crypto fixtures, dashboard-readable state, Base Sepolia testnet read/deploy commands, and local smoke-test gates. It does not mean production deployment.
+Immediate major milestone: keep the Rootflow V0 and Flow Memory V0 launch core green while packaging the FlowChain private/local L1 testnet path for second-computer validation. This means local contracts/tests, FlowPulse fixtures, Uniswap swap-derived memory-signal fixtures, Rootflow transitions, Flow Memory schemas, verifier reports, crypto fixtures, dashboard-readable state, Base Sepolia testnet read/deploy commands, Windows-first wrapper scripts, and local smoke-test gates. It does not mean production deployment.
 
 Run the local launch-core path:
 
@@ -79,6 +79,31 @@ npm run launch:candidate
 
 That command runs contract hardening, the launch flow, runtime schema validation, fixture drift checks, and claim guardrails.
 
+Run the current FlowChain private/local wrapper path:
+
+```powershell
+npm run flowchain:prereq
+npm run flowchain:init
+npm run flowchain:start
+npm run flowchain:demo
+npm run flowchain:export
+```
+
+Run the merged-surface smoke path when Foundry, Python, dashboard dependencies,
+and crypto dependencies are installed:
+
+```powershell
+npm install --prefix apps/dashboard
+npm install --prefix crypto
+npm run flowchain:smoke
+```
+
+Run the existing dashboard as the local workbench:
+
+```powershell
+npm run workbench:dev
+```
+
 Build the dashboard after regenerating launch data:
 
 ```powershell

diff --git a/apps/dashboard/public/data/flowmemory-dashboard-v0.json b/apps/dashboard/public/data/flowmemory-dashboard-v0.json
@@ -1993,12 +1993,12 @@
   ],
   "devnetBlocks": [
     {
-      "id": "0xf76ac3652230cae4a4b5afcd54b0dcec9219f20ad71e21c497264668fb30f235",
+      "id": "0x1e6f848e67c93fcd23091891ec704f5ed58989956789acd3368bce883ad493f9",
       "blockNumber": 1,
-      "blockHash": "0xf76ac3652230cae4a4b5afcd54b0dcec9219f20ad71e21c497264668fb30f235",
+      "blockHash": "0x1e6f848e67c93fcd23091891ec704f5ed58989956789acd3368bce883ad493f9",
       "parentHash": "0x0f23c892cbd2d00c10839d97ddab833698a83f8df8d6df27ceac03cfdd4b7bc9",
-      "stateRoot": "0x76ec5260c34184b6bb54ca406a43fc1f9591a47f37f71583a7620ef4a4065aff",
-      "receiptsRoot": "0x6962bd6dbf28c2361c1337c1d33d678a815cc4b961e0e50db5ccb401cc0fe076",
+      "stateRoot": "0xd92ec8176ad55060b37898d4235612d0874ae5da6a5edbf69717b704c484e016",
+      "receiptsRoot": "0x6393961b24d5db9f2984a39a98e827850b771f05c7f18005addb9a530af5a9b7",
       "timestamp": "2026-05-13T16:00:00.000Z",
       "observationCount": 8,
       "reportCount": 8,
@@ -2015,11 +2015,11 @@
       }
     },
     {
-      "id": "0x7515374a9b020a6d271820031738a5190cb0fc374adcd74a88a32c0fd0d5c7a6",
+      "id": "0x54ba8fe6b5d3781a91ebd45a2ab215dd51ff2f835afe1c72d1843384fffb3919",
       "blockNumber": 2,
-      "blockHash": "0x7515374a9b020a6d271820031738a5190cb0fc374adcd74a88a32c0fd0d5c7a6",
-      "parentHash": "0xf76ac3652230cae4a4b5afcd54b0dcec9219f20ad71e21c497264668fb30f235",
-      "stateRoot": "0x3e1f5fddd84f9d460ee30a380ff700b17611891b8c03eb320edf1baefe003ef9",
+      "blockHash": "0x54ba8fe6b5d3781a91ebd45a2ab215dd51ff2f835afe1c72d1843384fffb3919",
+      "parentHash": "0x1e6f848e67c93fcd23091891ec704f5ed58989956789acd3368bce883ad493f9",
+      "stateRoot": "0x75373cc47666ed9bcad605ce0f5d0aeb1bc8100a1087840d755205aef8a6bb50",
       "receiptsRoot": "0xa0407b9a8a55106d549e0f19b92fceaa7f7a25697e94ebf8a1fa74af7b9168f4",
       "timestamp": "2026-05-13T16:00:01.000Z",
       "observationCount": 8,

diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md
@@ -1,6 +1,12 @@
 # Architecture
 
-FlowMemory is a layered system for commitment-oriented AI memory, verification, local operator tooling, and bounded hardware research. Only the repository operating system and initial contracts foundation are implemented. Everything else is either specification, local fixture work, or research until explicitly merged.
+FlowMemory is a layered system for commitment-oriented AI memory, verification,
+local operator tooling, and bounded hardware research. The merged repo now has
+the V0 launch-core, local deterministic devnet prototype, fixture
+indexer/verifier, dashboard, crypto helpers, hardware simulator, and HQ wrapper
+layer. Native private/local FlowChain object lifecycle, control-plane coverage,
+long-running node behavior, and full workbench coverage remain in flight until
+explicitly merged.
 
 ## Layer Map
 
@@ -14,6 +20,7 @@ FlowMemory is a layered system for commitment-oriented AI memory, verification,
 8. Research lab
 9. Devnet/appchain research
 10. HQ program operating system
+11. FlowChain private/local testnet packaging
 
 ## Contracts
 
@@ -177,7 +184,8 @@ Boundaries:
 
 ## Devnet And Appchain Research
 
-Status: gated research only.
+Status: local no-value devnet prototype implemented; broader appchain/L1 work
+remains gated research.
 
 Responsibilities:
 
@@ -202,6 +210,28 @@ Responsibilities:
 - Maintain labels, milestones, review flow, and daily runbook.
 - Prevent agents from overlapping folders or expanding into gated work.
 
+## FlowChain Private/Local Testnet Packaging
+
+Status: Windows-first wrapper command layer implemented for merged surfaces.
+
+Responsibilities:
+
+- Provide one second-computer command path for prerequisites, init, bounded
+  start/stop, demo, smoke, export/import, and workbench dev mode.
+- Keep wrappers pointed at the existing Rust devnet, launch-core generator,
+  dashboard, hardware simulator, and guardrail scripts.
+- Record remaining subsystem blockers in `docs/FLOWCHAIN_TESTNET_ACCEPTANCE.md`
+  and `docs/ISSUE_BACKLOG.md`.
+
+Boundaries:
+
+- The wrapper layer does not create a second devnet, dashboard, crypto package,
+  verifier pipeline, object model, or setup path.
+- The current `flowchain:start` command is a bounded local CLI readiness path,
+  not a long-running node.
+- Production public-chain, token, bridge, and audited-cryptography claims remain
+  outside this milestone.
+
 ## Data Flow
 
 1. A local or future deployed contract action emits FlowPulse and updates compact on-chain state.

diff --git a/docs/CURRENT_STATE.md b/docs/CURRENT_STATE.md
@@ -6,15 +6,23 @@ This file is the beginner-friendly source of truth for what exists in FlowMemory
 
 ## Repo Phase
 
-FlowMemory is in launch-candidate V0 hardening.
+FlowMemory is in launch-candidate V0 hardening, with the next coordination
+target defined as a FlowChain private/local L1 testnet package for
+second-computer validation.
 
 The bootstrap repository operating system, contracts V0 foundation, crypto V0 foundation, local indexer/verifier fixture package, dashboard V0, FlowRouter hardware POC, local no-value devnet prototype, launch-core contract-event spine, and pre-production hardening guardrails have merged into `main`. The launch-candidate work added swap-derived memory signals, stricter launch validation, and Base Sepolia testnet deploy/read commands.
 
 On 2026-05-13 a small Base mainnet canary deployment was broadcast for V0 testing. It is documented in `docs/DEPLOYMENTS/2026-05-13-base-canary-v0.md`. A guarded Base mainnet canary reader now exists for those known canary addresses and small explicit block ranges. This is not a production launch and does not change the production/mainnet-readiness guardrails.
 
 The launch-core V0 stack now has a single runnable local command that connects contract fixtures, local indexing/verifier outputs, crypto schema vocabulary, Rootflow transitions, Flow Memory objects, generated dashboard state, local no-value devnet output, and hardware POC output without production deployment.
 
-Launch-critical direction: Rootflow V0 and Flow Memory V0 are the core of the next milestone. Rootflow defines memory-state transitions. Flow Memory defines the agent-facing memory objects derived from FlowPulse observations, receipts, verifier reports, and committed roots.
+Launch-critical direction: keep Rootflow V0 and Flow Memory V0 green while
+packaging the next private/local testnet milestone. Rootflow defines
+memory-state transitions. Flow Memory defines the agent-facing memory objects
+derived from FlowPulse observations, receipts, verifier reports, and committed
+roots. The FlowChain private/local testnet target must build on those surfaces;
+it is not approval for production mainnet, public validators, tokenomics,
+audited cryptography, or production bridge work.
 
 ## Implemented In The Merged Repo
 
@@ -104,11 +112,37 @@ Launch-core specifications:
 - `docs/ROOTFLOW_V0.md` defines the Rootflow V0 transition model, status vocabulary, agent ownership, and launch acceptance.
 - `docs/FLOW_MEMORY_V0.md` defines MemorySignal, MemoryReceipt, RootfieldBundle, AgentMemoryView, work-lane vocabulary, and dashboard display expectations.
 - `docs/V0_LAUNCH_ACCEPTANCE.md` maps the Rootflow and Flow Memory objective to concrete artifacts and evidence.
+- `docs/FLOWCHAIN_FULL_PRIVATE_TESTNET.md` defines the next private/local testnet package target and build-on-existing boundaries.
+- `docs/FLOWCHAIN_SECOND_COMPUTER_SETUP.md` names the current merged second-computer command path and the root-level FlowChain wrapper commands.
+- `docs/FLOWCHAIN_TESTNET_ACCEPTANCE.md` marks private/local testnet features as implemented, in flight, missing, or later gated.
+- `docs/FLOWCHAIN_AGENT_INTEGRATION_MAP.md` maps the next-wave worktree ownership and cross-agent handoffs.
+- `docs/FLOWCHAIN_TROUBLESHOOTING.md` and `docs/FLOWCHAIN_OPERATOR_CHECKLIST.md` provide the Windows-first second-computer troubleshooting and operator checklist layer.
 - `docs/DECISIONS/rootflow-v0.md` records the V0 decision and non-goal boundaries.
 - `docs/reviews/ROOTFLOW_FLOW_MEMORY_V0_ACCEPTANCE_AUDIT.md` tracks evidence and missing work for the active launch-core goal.
 - `docs/reviews/OPEN_PR_MERGE_READINESS.md` is now historical merge-readiness evidence for PRs that have merged.
 - `docs/LAUNCH_CORE_AGENT_GOALS.md` provides copy-ready goals for the contracts, crypto, indexer/verifier, dashboard, and review worktrees.
 
+FlowChain private/local testnet snapshot:
+
+- Implemented: V0 launch-core generation and validation, no-value deterministic
+  Rust devnet prototype, contract event/settlement spine, crypto V0 helpers and
+  vectors, fixture indexer/verifier, fixture-backed dashboard, hardware POC
+  simulator, Base Sepolia reader/deploy commands, guarded canary reader, and
+  Windows-first root wrapper commands for prerequisite checks, init, bounded
+  start/stop, demo, smoke, export/import, and workbench dev mode.
+- In flight: native private-testnet object lifecycle, local control-plane API,
+  private-testnet object IDs and envelopes, workbench extension, optional
+  hardware operator signal fixtures, and advanced L1 research gates.
+- Missing: long-running local runtime start behavior, private genesis/config
+  package beyond the deterministic devnet genesis, full native object
+  lifecycle coverage, full control-plane method coverage, full workbench entity
+  coverage, no-secret API checks, and second-computer smoke evidence for the
+  unmerged native object/control-plane/workbench surfaces.
+- Later gated: production L1/mainnet, public validators, tokenomics,
+  production bridge, production hook deployment, audited cryptography,
+  proof-circuit infrastructure, production hardware, and hosted production
+  services.
+
 ## Conceptual Or Not Implemented Yet
 
 - Production protocol deployment.
@@ -137,7 +171,10 @@ Closed issue notes:
 - #16 was closed as not planned because its scope was folded into other architecture/status issues.
 - #39 was closed; future on-chain verifier adapter work should stay gated behind accepted verifier and crypto boundaries.
 
-As of this update there are no open PRs in `FlowmemoryAI/FlowMemory`.
+As of the 2026-05-13 HQ review for the private/local testnet next wave, GitHub
+shows open draft PRs #71 and #73, plus open canary follow-up issues #76 through
+#79. Local sibling worktrees contain unmerged Local Alpha work; those changes
+are useful context but are not source of truth until merged.
 
 Recently merged PRs:
 
@@ -181,10 +218,14 @@ Before assigning agents, check for dirty worktrees and avoid overlapping folders
 ## Current Operator Priorities
 
 1. Keep the generated launch-core command stable in CI.
-2. Keep the guarded Base canary reader and dashboard canary artifacts fresh when canary smoke actions change.
-3. Exercise the Base Sepolia deploy/read path on explicit testnet contract addresses only.
-4. Continue contracts hardening without production mainnet deployment or token mechanics.
-5. Keep dashboard work fixture-backed until a production API is explicitly scoped.
+2. Keep the new root wrapper path usable on Windows: `flowchain:prereq`, `flowchain:init`, `flowchain:start`, `flowchain:demo`, `flowchain:smoke`, `flowchain:export`, and `workbench:dev`.
+3. Convert the remaining V0/local-alpha surfaces into one FlowChain private/local L1 testnet package for second-computer validation.
+4. Land the missing subsystem pieces behind the wrappers: long-running runtime behavior, control-plane serve/query coverage, native object lifecycle, and workbench entity coverage.
+5. Keep the guarded Base canary reader and dashboard canary artifacts fresh when canary smoke actions change.
+6. Exercise the Base Sepolia deploy/read path on explicit testnet contract addresses only.
+7. Continue contracts hardening without production mainnet deployment or token mechanics.
+8. Keep dashboard work fixture-backed until a production API is explicitly scoped.
+9. Keep production mainnet, public validator, tokenomics, audited-cryptography, and production bridge claims out of scope.
 
 ## Update Rule
 

diff --git a/docs/DAILY_HQ_RUNBOOK.md b/docs/DAILY_HQ_RUNBOOK.md
@@ -2,6 +2,10 @@
 
 This runbook is for the FlowMemory HQ operator. It keeps many Codex agents moving without overlapping folders or expanding into premature product work.
 
+Private/local testnet checklist companion:
+`docs/FLOWCHAIN_OPERATOR_CHECKLIST.md`. Troubleshooting companion:
+`docs/FLOWCHAIN_TROUBLESHOOTING.md`.
+
 ## Morning Review
 
 Run:
@@ -25,6 +29,41 @@ Check:
 - Evidence gaps in `docs/V0_LAUNCH_ACCEPTANCE.md`.
 - Current audit notes in `docs/reviews/ROOTFLOW_FLOW_MEMORY_V0_ACCEPTANCE_AUDIT.md`.
 
+## FlowChain Full-Testnet Push Checklist
+
+Morning:
+
+- Confirm GitHub open PRs and issues still match `docs/CURRENT_STATE.md` and
+  `docs/ISSUE_BACKLOG.md`.
+- Check all sibling worktrees for dirty changes before assigning agents.
+- Verify no two active agents are editing the same folder family or source-of-truth
+  doc without coordination.
+- Review `docs/FLOWCHAIN_TESTNET_ACCEPTANCE.md` for rows that changed from
+  missing to in flight or implemented after merges.
+- Verify root command aliases in `package.json` still match the scripts under
+  `infra/scripts/flowchain-*.ps1`.
+- Confirm the next assigned work extends the existing devnet, control-plane,
+  crypto, dashboard, contracts, hardware, or research surface instead of adding
+  a replacement system.
+- Keep production L1, tokenomics, public validator, production bridge, audited
+  cryptography, production hook, and production hardware claims blocked.
+
+Evening:
+
+- Record merged PRs, open PRs, dirty worktrees, blockers, and next smallest
+  actions for the private/local testnet package.
+- Update `docs/CURRENT_STATE.md`, `docs/ROADMAP.md`, and
+  `docs/ISSUE_BACKLOG.md` if a merge changes implemented, in-flight, missing,
+  or later-gated state.
+- Update `docs/FLOWCHAIN_SECOND_COMPUTER_SETUP.md` whenever a command lands or
+  a command name changes.
+- Check whether the second-computer path can now run farther than the previous
+  day, and name the first failing step.
+- Save or cite `devnet/local/smoke/flowchain-smoke-report.json` when full smoke
+  runs locally.
+- Require `git diff --check` in each PR summary and area tests where the touched
+  area has tests.
+
 ## Issue Triage
 
 For each issue: