Skip to content

[codex] Add FlowRouter control-plane signal handoff #117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
FlowmemoryAI merged 1 commit into from
May 18, 2026
Merged

[codex] Add FlowRouter control-plane signal handoff #117

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 14 additions & 3 deletions fixtures/hardware/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,21 +7,32 @@ This folder contains local-alpha hardware projections that can be consumed by da
## Fixtures

- `flowrouter_local_alpha_seed42.json`: deterministic FlowRouter-to-FlowChain operator signal projection generated from `hardware/fixtures/flowrouter_sample_seed42.json`.
- `flowrouter_control_plane_handoff_seed42.json`: read-only optional hardware handoff shaped for local control-plane ingestion.
- `flowrouter_negative_validation_seed42.json`: deterministic report proving malformed hardware/operator handoff cases are rejected.

## Shape

The fixture is a `flowmemory.hardware_operator_signals.local_alpha.v0` document. It includes:

- `signalEnvelopes`: one envelope for heartbeat, receipt relay, verifier digest relay, offline alert/challenge input, and NFC memory cartridge metadata.
- `hardwareSignals`: direct workbench/control-plane signal records for the same five envelopes.
- `hardwareNodes`, `workReceipts`, `verifierReports`, `artifactCommitments`, `memoryCells`, `challenges`, `finalityReceipts`, and `alerts`: control-plane-friendly local fixture collections.
- `signalEnvelopes`: envelopes for operator metadata, heartbeat, receipt relay, verifier digest relay, offline alert/challenge input, bridge alert, and NFC memory cartridge metadata.
- `hardwareSignals`: direct workbench/control-plane signal records for the same envelopes.
- `operatorMetadata`, `hardwareNodes`, `workReceipts`, `verifierReports`, `bridgeAlerts`, `artifactCommitments`, `memoryCells`, `challenges`, `finalityReceipts`, and `alerts`: control-plane-friendly local fixture collections.
- `workbenchRecords`: ready-to-render records grouped by workbench section keys, including `hardwareSignals`.
- `boundary`: explicit local-only, advisory, optional-hardware limitations.

The handoff fixture is a `flowmemory.hardware_control_plane_handoff.local_alpha.v0` document. It mirrors the stable control-plane state keys under `collections`, declares read-only merge id fields, and carries an optional full-smoke row:

```powershell
python hardware/simulator/flowrouter_sim.py --smoke
```

## Validation

```powershell
python hardware/simulator/flowrouter_sim.py --smoke --seed 42
python hardware/simulator/flowrouter_sim.py --validate-operator-file fixtures/hardware/flowrouter_local_alpha_seed42.json
python hardware/simulator/flowrouter_sim.py --validate-handoff-file fixtures/hardware/flowrouter_control_plane_handoff_seed42.json
python hardware/simulator/flowrouter_sim.py --validate-negative-report-file fixtures/hardware/flowrouter_negative_validation_seed42.json
```

These fixtures are local-only and advisory. They do not prove hardware trustlessness, production field deployment, or receipt/verifier finality.
Loading
Loading