Product
Product statement, modes, navigation, core entities, and out-of-scope boundaries.
PRODUCT · CONTACTS · UI/UXharness-os-2 · Historical repository
This repository is not a second Harness OS implementation. It preserves the compact specification kit—product, architecture, security, API, UI, provider, creative-compute, and acceptance documents—that seeded the realized project.
Exact precursor. Every specification Markdown file, plus AGENTS.md and the spec-kit README.md, is byte-for-byte identical to the copy retained under harness-os/spec/.
Archive inventory
The repository root contains only a one-line README and a ZIP archive. Inside is a deliberately complete handoff package rather than runnable product code.
Product statement, modes, navigation, core entities, and out-of-scope boundaries.
PRODUCT · CONTACTS · UI/UXAPI-first architecture, data model, context compiler, events, hosts, and optional node.
ARCHITECTURE · API · DATAProvider matrix, MCP and skills, permissions, creative compute, analytics, and artifacts.
PROVIDERS · CREATIVE · TOOLSOne-shot prompt, implementation sequence, testing strategy, deployment, and definition of done.
BUILD · TEST · DEPLOYArchive roadmap
A coherent, inspectable product and engineering contract for a local-first agent and AI compute control plane.
The specification was carried into the full Harness OS repository, where the source, tests, WebUI, TUI, CI, and project site now live.
Retain this repository if the original handoff artifact is useful for provenance. Otherwise, GitHub's archive setting can make its superseded status unmistakable.
All implementation, validation, issues, and roadmap work belong in Harness OS. This repository should not diverge into a competing product.
Continue here
See the running architecture, interface evidence, installation guide, alpha status, and live-validation roadmap on the successor page.