[dashboard/app data model] Define operator and explorer state model

[FlowmemoryAI]

Objective

Define the first app-facing data model for an operator dashboard and protocol explorer, based only on observed, committed, verified, pending, failed, and reorged states.

Allowed folders

• apps/
• docs/ARCHITECTURE.md only for a short cross-link
• services/indexer/ or services/verifier/ only for terminology cross-links

Forbidden folders

• contracts/
• hardware/
• crypto/
• research/
• UI implementation, frontend scaffolding, production APIs, deployment config

Acceptance criteria

• A small app data model note exists under apps/.
• It defines entities/views needed by dashboard and explorer without building UI.
• It distinguishes observed, verified, pending, failed, unsupported, and reorged states.
• It does not invent service APIs or production infrastructure.

Risk level

Medium

Recommended worktree/agent

E:\FlowMemory\flowmemory-dashboard / Apps Agent

Scope guard

Spec only. Do not build dashboard, explorer, hardware console, or production API routes.

[FlowmemoryAI]

Codex scope reconciliation on 2026-05-13: this issue was originally opened as a spec-only dashboard/app data model task. The current assigned goal expands it into a local FlowMemory Dashboard V0 implementation within apps/dashboard/, fixtures/dashboard/, docs/DASHBOARD_MVP.md, and package files needed for the app. The implementation will keep the original state-model constraints, avoid production/live-data claims, and stay out of contracts/services except fixture shape documentation.