Objective
Create a tight hardware scope note for FlowRouter v0 that separates research, field tests, firmware/electrical work, enclosure work, and operator controls.
Allowed folders
hardware/
docs/ARCHITECTURE.md only for a short cross-link
docs/SECURITY_MODEL.md only for hardware threat assumptions
docs/DECISIONS/ only if a durable decision is needed
Forbidden folders
contracts/
services/
apps/
crypto/
research/ except cross-link references
- Production hardware BOM procurement, production firmware, deployment procedures
Acceptance criteria
- A v0 hardware scope document exists under
hardware/.
- It names explicit non-goals, including no heavy data over LoRa/Meshtastic and no production device commitment.
- It identifies the smallest useful proof-of-concept questions.
- It includes open risks for identity, physical tampering, and operator controls.
Risk level
Medium
Recommended worktree/agent
E:\FlowMemory\flowmemory-hardware / Hardware Agent
Scope guard
Keep this research/specification-only. Do not start production hardware or deployment work.
Objective
Create a tight hardware scope note for FlowRouter v0 that separates research, field tests, firmware/electrical work, enclosure work, and operator controls.
Allowed folders
hardware/docs/ARCHITECTURE.mdonly for a short cross-linkdocs/SECURITY_MODEL.mdonly for hardware threat assumptionsdocs/DECISIONS/only if a durable decision is neededForbidden folders
contracts/services/apps/crypto/research/except cross-link referencesAcceptance criteria
hardware/.Risk level
Medium
Recommended worktree/agent
E:\FlowMemory\flowmemory-hardware/ Hardware AgentScope guard
Keep this research/specification-only. Do not start production hardware or deployment work.