Skip to content

[hardware] Define FlowRouter v0 research scope and non-goals #11

@FlowmemoryAI

Description

@FlowmemoryAI

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/hardwareFlowRouter, Meshtastic, LoRa, hardware POC workdocumentationImprovements or additions to documentationpriority/p1Important next prioritytype/docsDocumentation or planning work

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions