Skip to main content

​
Idea intake

Enoch does not require ideas to originate in the control plane. An upstream LLM-assisted scouting process can review technical signals, frame candidate experiments, and write structured idea cards. The current preferred intake path is control-plane native: write idea, project, queue, and event rows together so the control plane can dispatch from one database-backed workbench. In production that database is local Postgres on enoch-core; Supabase-era wording is historical migration terminology. For current runtime topology and storage authority, see current runtime snapshot. Notion was an earlier intake and prioritization surface. Treat it as legacy compatibility unless you have explicitly enabled the Notion sync units for an older workflow.

​
Intake stages

Research Facility (source scan -> candidate -> dedupe -> score -> admission)
  -> control-plane idea row
  -> control-plane project + queue item
  -> Enoch control-plane execution
See Research Facility for the full candidate generation, admission, and promotion flow.

​
What an idea card should contain

  • working title
  • hypothesis or question
  • expected mechanism
  • evaluation sketch
  • hardware/software constraints
  • expected evidence type
  • failure or kill criteria
  • why the experiment might matter
  • source metadata and dispatch priority

​
Control-plane intake

A dispatch-ready intake write should create or update the related records as one intentional batch:
  1. enoch.ideas stores the idea text, scoring metadata, source payload, target machine, model, and sandbox.
  2. enoch.projects gives the control plane a stable project identity and project directory.
  3. enoch.queue_items makes the idea dispatchable when its status is queued and dispatch safety allows work.
  4. enoch.idea_events records provenance for the intake event.
Use the control-plane API dry-run path first where available. If you must use direct SQL, run a rollback dry-run before committing rows, and verify the result in enoch.idea_workbench.

​
Legacy Notion sync

The code repo still includes enoch-notion-sync systemd units and a Notion sync helper for older deployments. Configure Notion credentials through environment files, not committed config. Do not enable Notion sync in a current control-plane deployment unless you intentionally want that legacy projection path. 
NOTION_TOKEN=replace-with-token
# NOTION_DATABASE_ID=replace-with-database-id
# NOTION_DATA_SOURCE_ID=replace-with-data-source-id
NOTION_SYNC_MAX_UPDATES=25

​
What not to overclaim

The scout does not prove novelty, a weight matrix is prioritization rather than objective truth, generated papers are still AI-generated artifacts, and runtime safety comes from the control plane and worker checks.