Dashboard/Intelligence-Research-OS/wiki/decisions/2026-05-21-local-file-gated-workbench.md
Intelligence-Research-OS

wiki/decisions/2026-05-21-local-file-gated-workbench.md

ADR: Local File-Gated Workbench

Date: 2026-05-21 Status: Accepted

Context

Intelligence Research OS needs a working browser UI, but ResearchModule already has a strong file-gated pipeline with validated artifacts and resumable state. Creating a separate database-backed UI state model would duplicate truth and risk breaking provenance guarantees.

Decision

The first local web app uses existing file-gated artifacts as the source of truth.

Rationale

  • Preserves strict source/evidence/citation discipline.
  • Keeps CLI, skill, API, and UI wrappers aligned.
  • Avoids premature database and sync complexity.
  • Makes local browser testing possible immediately.

Alternatives Considered

Option Why rejected
Database-backed app state Too early; duplicates artifact truth.
CLI-only UX Does not validate the six-screen workbench.
Dashboard mockups only Not executable.

Consequences

  • API endpoints read/write mission and run artifacts.
  • Empty states must handle missing downstream artifacts cleanly.
  • Future production app may add a database, but it must mirror artifact contracts rather than replace provenance.