Skip to content

[codex] Add FlowChain local node runtime#116

Draft
FlowmemoryAI wants to merge 1 commit into
mainfrom
agent/full-l1-runtime
Draft

[codex] Add FlowChain local node runtime#116
FlowmemoryAI wants to merge 1 commit into
mainfrom
agent/full-l1-runtime

Conversation

@FlowmemoryAI
Copy link
Copy Markdown
Owner

@FlowmemoryAI FlowmemoryAI commented May 13, 2026

Summary

Adds the FlowChain private/local node runtime on top of crates/flowmemory-devnet:

  • Long-running local node mode with disk state, interval block production, manual tick, stop/status files, node identity, and local-file inbox processing.
  • FlowChain-native transaction intake plus local local-authorized transaction receipt metadata.
  • No-value local test-unit ledger with faucet records and balance transfers for transaction/faucet smoke coverage.
  • Static local-file peer reconciliation for two local node processes; LAN mode is explicitly not exposed.
  • Root npm wrappers for node start/stop/status, transaction submit, faucet, one-node smoke, multi-node smoke, and flowchain:full-smoke.
  • Docs and acceptance matrix updates for second-computer runtime commands and current remaining gaps.

Scope

Allowed folders touched:

  • crates/flowmemory-devnet/
  • infra/scripts/
  • package.json
  • docs/LOCAL_DEVNET.md
  • docs/FLOWCHAIN_SECOND_COMPUTER_SETUP.md
  • docs/FLOWCHAIN_TESTNET_ACCEPTANCE.md

No apps/dashboard/, services/, contracts/, crypto/, or hardware/ source changes are included.

Validation

  • cargo test --manifest-path crates/flowmemory-devnet/Cargo.toml passed.
  • npm run flowchain:node:smoke passed.
  • npm run flowchain:multi-node:smoke passed.
  • npm run flowchain:full-smoke passed after installing local root, dashboard, and crypto dependencies.
  • git diff --check passed.
  • Branch rebased on current origin/main before push.

Notes and Boundaries

  • Local balances are private/local test units only, not tokenomics.
  • Static peer reconciliation is local-file based for second-computer validation; LAN networking is not exposed.
  • Control-plane query coverage and dashboard/workbench runtime rendering remain subsystem follow-ups.

HQ Required Review Metadata (2026-05-14)

Issue status: Original #99 lane is closed on GitHub; needs new/open issue if work remains
Worktree / branch ownership: E:\FlowMemory\flowmemory-chain
Allowed folders: crates/flowmemory-devnet/, infra/scripts/, package.json, docs/LOCAL_DEVNET.md, docs/FLOWCHAIN_SECOND_COMPUTER_SETUP.md, docs/FLOWCHAIN_TESTNET_ACCEPTANCE.md
Forbidden folders: apps/dashboard/, services/, contracts/, crypto/, hardware/, unrelated docs
Exact checks recorded:

  • cargo test --manifest-path crates/flowmemory-devnet/Cargo.toml; npm run flowchain:node:smoke; npm run flowchain:multi-node:smoke; npm run flowchain:full-smoke after installing root/dashboard/crypto dependencies; git diff --check; GitHub CI checks listed below.
  • GitHub CI Repository hygiene: SUCCESS
  • GitHub CI Contracts: SUCCESS
  • GitHub CI Services and launch core: SUCCESS
  • GitHub CI Launch-core acceptance command: SUCCESS
  • GitHub CI Crypto: SUCCESS
  • GitHub CI Dashboard: SUCCESS
  • GitHub CI Local devnet: SUCCESS
  • GitHub CI Hardware POC: SUCCESS
    HQ readiness: Draft; merge state DIRTY; close as superseded or refresh against current main and a new/open issue.

Copy link
Copy Markdown
Owner Author

HQ review blocker, 2026-05-14: before merge readiness review, please update the PR body to include the linked issue #99, allowed folders, forbidden folders, worktree path, and exact checks run with results. The current changed-file scope includes crates/flowmemory-devnet/, runtime wrapper scripts, docs, and package.json; the PR body needs to state the intended scope and prove it with local checks, including git diff --check.

Copy link
Copy Markdown
Owner Author

HQ reconciliation note, 2026-05-14: GitHub now shows linked runtime issue #99 as closed. Before merge review, please either close this draft if it was superseded by merged main, or refresh the PR body with the exact remaining delta and a new/open issue reference for anything still needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant