Agentic research needs a control plane

Enoch turns local AI research runs into auditable artifacts.

A scored idea enters a queue. A control VM checks safety. A worker executes under a wake gate. Evidence is synced. A configured writer produces publication-style reports with claim boundaries and provenance. The system is the sell; the generated artifacts are evidence to inspect, not peer-reviewed claims.

Code repo Research corpus

What Enoch is

A reliability layer for long-running autonomous work.

Enoch is a replacement for a scattered local automation stack. It owns queue state, pause/maintenance controls, worker preflight, single-lane safety, process/telemetry truth, evidence sync, paper rewriting, and dashboard status, built around FastAPI/LangGraph-era control-plane boundaries and operated with Codex/OMX automation.

The generated papers are released as AI-generated research artifacts. The human operator built and operated the surrounding Enoch system; OMX/oh-my-codex is credited as orchestration infrastructure, not as the owner or author of the generated paper prose, arguments, or experimental results.

Workflow

From idea intake to public artifact.

1. ScoutLLM-assisted review of technical signals, public papers, news, and local runtime opportunities.
2. ScoreNotion weight matrix ranks candidate ideas before execution.
3. DispatchControl plane gates queue state, maintenance state, worker health, and single-lane safety.
4. ExecuteGB10 worker runs the experiment while wake gate watches process and telemetry truth.
5. PreserveRun notes, evidence bundles, claim ledgers, metrics, and manifests are synced.
6. PublishA configured artifact writer drafts evidence-grounded reports with provenance and caveats.

System diagrams

Control plane first, artifacts second.

These diagrams are intentionally editable SVGs so the launch story stays crisp: queue safety and provenance are the product, while generated papers are inspectable outputs.

Enoch architecture diagram from idea intake through control plane, wake gate, worker, evidence, publication, dashboard, and alerts
Architecture: idea intake enters a gated control plane before local execution, evidence sync, paper packaging, dashboard visibility, and alerts.
Provenance diagram linking generated text to metadata, evidence, claim ledger, and publication surface
Provenance: generated text is only useful when attached to metadata, evidence bundles, limitations, and review/audit state.

Public framing

Built in the open, with provenance up front.

Release Enoch as an engineering artifact: a working control plane, a corpus of generated outputs, and a transparent record of what was automated. The hook is not “these are human papers.” The hook is that a local agentic system generated, supervised, rewrote, and packaged a research corpus with evidence and caveats—and some of the generated artifacts are specific enough to invite independent replication attempts.

Launch TODO · Announcement drafts · oh-my-codex / OMX