Skip to main content

Documentation Index

Fetch the complete documentation index at: https://solo-09d10f60.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

​
Control plane

The Enoch control plane is the runtime authority for queued research work. It is implemented as a FastAPI app with explicit state models for projects, queue items, runs, paper records, paper reviews, events, and pause flags.

​
What it owns

  • Queue state — queue items move through statuses such as queued, dispatching, running, awaiting_wake, wake_received, reconciling, completed, paused, canceled, dispatch_error, blocked, and needs_review.
  • Dispatch decisions — /control/dispatch-next checks whether a candidate can be launched and supports dry-run requests.
  • Pause and maintenance controls — /control/pause, /control/resume, and related state expose operator intent.
  • Worker preflight — /control/api/preflight and /control/worker/preflight call a worker wake-gate API before live dispatch.
  • Project and run records — APIs expose project detail, run detail, queue views, and dashboard summaries.
  • Paper review state — paper records and review records support drafting, checklist updates, status transitions, finalization packaging, and artifact reads.
  • Events and projections — the control plane stores operational events and can expose Notion-oriented projections.

​
Dispatch safety

A dispatch is safe only when the control plane has a dispatchable queue item, pause and maintenance flags allow work, no active lane is already running, and worker preflight passes. The control plane is the lock holder; callers should not bypass it with ad hoc scripts. Dry-run dispatch is the first test for a new deployment because it exercises the guard path without launching a real agent job.

​
Dashboard truth

The dashboard is useful because it reads control-plane state instead of trusting a model session to self-report. It surfaces queue health, blockers, flags, records, events, paper review items, and configuration status.

​
Relationship to intake tools

Notion and LLM-assisted scouting help decide what ideas are worth queueing. They are not the runtime authority. Once work enters Enoch, the control plane decides what is queued, what is active, what is blocked, and what evidence is available.

​
Important boundaries

The control plane cannot prove a generated research claim is true. It can preserve the operational state and artifacts needed for review. Human review and replication remain required before treating a generated artifact as reliable science.