Agents work step by step and explain the outcome
Datarim helps coordinate agents, continue work without constant prompting, and choose a suitable mode through Jev, and handle tiny tasks through /dr-quick. You set the goal; requirements, verification, and permission boundaries remain in force at every stage.
Agent orchestration
Planning, implementation, and review are assigned to the corresponding roles. The optional dr-orchestrate runner continues a terminal workflow from state snapshots and checks each action against the allowed policy.
/dr-plugin enable /path/to/plugins/dr-orchestrate
dr-orchestrate run --dry-run
The runner is installed separately and requires tmux. Unknown state or a disallowed action stops automatic continuation; new learned rules require confirmation.
Set up orchestration
Autonomous staged work
/dr-auto starts a new task or resumes an existing one, delegates its stages, and resolves small gaps from available evidence. Each stage reports its outcome and open limitations in plain language.
/dr-auto task description
On the full route, /dr-auto stops after successful compliance review (/dr-compliance) and its internal reflection. Archiving remains a separate action. Ambiguity and protected actions retain their required gates.
Start staged work
Jev classification and model advice
Jev classifies a prompt through the configured model API and recommends a working mode and model tier. In a Datarim project it also recommends catalogue artifacts. This helps match the task complexity to the executor. Use it with Datarim or independently.
jev doctor --agent=codex --api
Classification requires configured API access; advice does not automatically change the active session model. The command safety floor works without a key; when the API is unavailable, the session continues without advice.
Install and verify Jev
A fast lane for tiny tasks
/dr-quick handles a tiny self-contained edit or a read-only lookup. It skips the full requirements, planning, design, QA, and compliance stages, while retaining mandatory evidence for mutations.
/dr-quick "tiny task"
An edit needs a falsifiable success condition, live execution evidence, and delivery reachability from origin/main before a short archive. A lookup creates no task files and stays UNCERTIFIED: informational, without a certified completion claim. If scope grows, use the full cycle.
Choose the fast lane
In 4.2, reporting connects the outcome to the original request and evidence. If the explanation is unclear, /dr-explain restates it without executing work. Human Outcome Reporting.
Use your preferred reply language while creating documents in the project language. Independent language.replies and language.artifacts settings both default to en, including standalone reporting without Datarim. Configure languages.
8-Stage Pipeline
Not every task goes through all stages. A simple fix: init → do → archive (reflection runs at /dr-compliance, or /dr-archive regenerates it if absent). A major project: all 8 stages with multi-agent review.
init
→
prd
→
plan
→
design
→
do
→
qa
→
compliance
→
archive
/dr-init
Analyze task or scaffold project, determine complexity (L1-L4), create tracking
/dr-prd
Product requirements with research phase (1.3) and discovery interview
/dr-plan
Detailed implementation plan with strategist review
/dr-design
Architecture exploration for complex features (L3-4)
/dr-do
TDD implementation with gap discovery for unknowns
/dr-qa
4-layer quality check: PRD, design, plan, code
/dr-compliance
Adaptive post-QA hardening by task type + reflection (lessons + evolution proposals)
/dr-archive
Archive the task (reflection regenerated only if missing)
8
Autonomous Agent Operating Rules
Eight canonical rules (FB-1..FB-8) under Supreme Directive Laws 1-5 — the contract Datarim ships, the canonical text lives in the consumer ecosystem AGENTS.md.
FB-1
rule-based
Research available solution options
FB-2
rule-based
Compare options for security and maintainability
FB-3
subagent
Run a role-based consilium when needed
FB-4
rule-based
Choose an option and record the reason
FB-5
rule-based
Execute safely reversible work without the operator
FB-6
rule-based
Keep decisions reversible under uncertainty
FB-7
rule-based
Provide correction and rollback after testing
FB-8
escalation
Escalate only genuinely blocking questions
Hard-gated actions NEVER auto-execute regardless of FB-5: production deploy, secret rotation, irreversible DB operations, public communication, finance/legal actions, force-push to main, git history deletion, multi-user-visible actions, publishing consilium-selected content.