Operations explainer

Director Decisions And AgentJob Lifecycle

The lifecycle makes controlled work inspectable. A task narrows into a Director decision, an AgentJob, role execution evidence, completion, and handoff or registry rows when needed.

Director and AgentJob lifecycle
Visual orientation only: each state narrows authority for one bounded transaction.

Lifecycle comprehension

The record chain narrows authority step by step.

A task row, Director decision, AgentJob, execution-role evidence, validation, completion, and handoff each answer a smaller operational question.

Diagram showing task row, Director decision, AgentJob, execution-role evidence, command evidence, completion, handoff, and no silent authority expansion.
Static comprehension diagram: the lifecycle records why one transaction was authorized and how it closed.Mermaid source: docs/content-dossiers/operations-director-agentjob-lifecycle/diagrams/director-agentjob-record-chain.mmd. Manifest id: comprehension_operations_director_agentjob_record_chain.

The diagram is a static reader aid. It does not replace the source files, route dossiers, or claim-status records that govern the topic.

Mechanism

How to read this surface.

Terms

Define the loaded words before using them.

Task row
The tracked problem statement and state pointer for a piece of work.Not permission to act outside its current route.
Execution-role evidence
The record binding role semantics to one job.Not a reusable authority grant.

Boundaries

What this page must not imply.

No mutation
Correct by supersessionRepair work should create a new bounded packet rather than silently rewriting activated history.
No protected gate bypass
Gates remain separateOntology adoption, benchmark promotion, and Gate Chair decisions require their own authority path.

Safe reading

A useful summary also names the unsafe one.

Safe summary
Supported readingThe lifecycle page explains how one bounded task becomes a decision, an AgentJob, evidence, completion, and possibly a handoff.
Unsafe summary
Forbidden shortcutA lifecycle diagram expands authority, rewrites activated records, bypasses protected gates, or changes physics status.

Related routes

Source basis

Use these as provenance, not primary navigation.

Lifecycle map

Each record narrows the next record.

The durable chain answers what was authorized, what was allowed, what was checked, and what remains blocked or next.

Task
Names the objectiveThe task records status, parentage, current decision, current job, closure, and the next recommendation.
Decision
Selects the routeThe Director decision records role selection, rejected alternatives, claim boundary, and required checks.
AgentJob
Defines executable scopeThe job sets allowed reads and writes, generated outputs, forbidden paths, validators, and stop conditions.
Completion
Records evidenceThe completion captures outputs, command results, verdict, uncertainty, and next recommendation for one transaction.

Immutable evidence

Correct by supersession, not silent mutation.

A failed or obsolete record can be followed by a repair packet. The old record stays interpretable because history is not edited into a cleaner story.

Repair
New packetA repair or changed route should produce a new bounded packet rather than rewriting activated authority.
Stop
Protected authority remains protectedGate Chair verdicts, benchmark promotion, ontology adoption, and source edits require their own authority paths.
Limit
Completion evidence stays transaction-localA completion can close or hand off one job, but it cannot make the checked operation a scientific result.

Related reading

These links keep the primary reader journey inside the website. Source links remain visible in the provenance section.

Source provenance

Source links are for inspection, not primary navigation.

The links below point to reviewed upstream source surfaces. This website adaptation remains downstream from those sources and from the registered authority records they cite.

Source authority