Conclave Job Ledger

Conclave Job Ledger

Conclave coordinates registered local work through a persistent SQLite job ledger. It is not an autonomous agent framework and does not grant shell, network, or unrestricted database access to modules.

See Agent Orchestration for the staged integration model and configurable operating rules.

Job Lifecycle

queued -> running -> completed
                 -> failed -> requeue
                 -> needs_review
                 -> cancelled -> requeue

Each job stores its input hash, active agent-registry configuration hash, attempt count, bounded result, and immutable event envelopes. Re-submitting the same case, topic, agent, input, and configuration returns the existing job rather than creating a duplicate.

Registered Routes

• evidence.ocr_requested routes to glyphwatch-ocr.
• evidence.depth_requested routes to glyphwatch-depth.
• Other registered topics can be queued, but they require an explicitly added local handler before execution.

POST /api/jobs/{job_id}/execute is an operator action. It currently runs only the OCR and depth routes, and both retain their normal confirmation requirements. Without the required confirmation, the job becomes needs_review and no model is run.

API Surface

GET  /api/job-queue
GET  /api/cases/{case_id}/jobs?state=queued
POST /api/cases/{case_id}/jobs
GET  /api/jobs/{job_id}
GET  /api/jobs/{job_id}/events
POST /api/jobs/{job_id}/transition
POST /api/jobs/{job_id}/execute

Job state and event trails are included in case JSON and PDF exports.