01
Route the task
A Director decision selects the appropriate lane and records the boundary.
Operational synthesis
Operations
Operations are the control surfaces that make the project auditable: route one bounded task, bind authority to records, run the right checks, and preserve evidence without turning operational success into scientific proof.
Operations comprehension
Operations are the control spine, not scientific authority.
The operations family explains how requests become routed decisions, bounded AgentJobs, execution-role evidence, validators, completions, and handoffs.
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.
02
Bind the job
The AgentJob defines allowed reads, writes, generated outputs, validators, and stop conditions.
03
Preserve evidence
Completion, handoff, and registry evidence keep work inspectable without rewriting history.
Terms
Define the loaded words before using them.
- Operations
- The project-control practices that route, execute, validate, publish, improve, and reproduce work.Not a scientific result.
- Completion evidence
- A record of outputs, checks, verdict, uncertainty, and next step.Not claim promotion.
- Handoff
- A bounded next-step record when work must continue separately.Not an extension of the current authority.
Boundaries
What this page must not imply.
- No source edits
- Operations pages are explanatoryThey cannot change routing behavior, validators, roles, publication policy, or physics status.
- No proof by process
- Auditability is not theorem proofStrong operations can support trustworthy work without replacing mathematical or scientific source evidence.
Safe reading
A useful summary also names the unsafe one.
- Safe summary
- Supported readingOperations explain how bounded work is routed, executed, checked, recorded, published, and improved without changing source authority.
- Unsafe summary
- Forbidden shortcutOperations pages authorize work, promote claims, prove physics, rewrite activated records, or make validator PASS broader than the checked state.
Related routes
Continue through internal pages first.
Source basis
Use these as provenance, not primary navigation.
Source basis
Operations explainer set
Generated noncanonical upstream explainers for lifecycle, role routing, validation, publication, improvement, and technical requirements.
Operating model
Authority narrows as evidence accumulates.
The operational stack is conservative. Each record answers a smaller question than the previous one: what was requested, what was authorized, what was allowed, what was checked, and what remains open.
- Route
- Director decisionA Director decision selects one role path, records rejected alternatives, and preserves the claim boundary.
- Execute
- AgentJob allowlistThe AgentJob controls allowed paths, outputs, validators, source classes, and stop conditions for one transaction.
- Check
- Validation evidenceValidators and tests establish bounded acceptance for the checked state, not global correctness or source authority.
- Preserve
- Completion and handoffCompletion records, handoffs, and registries keep the evidence trail inspectable without rewriting history.
Operational routes
Use the operations pages as an inspection guide.
These routes organize operational concepts inside the website. Source links remain available below as provenance.
- Internal route
- Director and AgentJob lifecycleHow tasks narrow into decisions, jobs, completions, handoffs, and registry evidence.
- Internal route
- Role routingWhy role names are templates, while execution records and AgentJobs control one transaction.
- Internal route
- Validator and operator workflowHow checks, receipts, screenshots, and PASS results should be interpreted.
- Internal route
- Publication processHow public explainers move from brief to source spec, page, screenshots, and review.
- Internal route
- Project-system improvementHow classifiers, signals, sidecars, receipts, and one bounded AgentJob structure repairs.
- Internal route
- Technical requirementsLocal tool tiers for reproducible operation without confusing tools with authorization.
Operations routes
Use the route that matches the operational question.
The operations landing now exposes the internal route family directly: lifecycle, routing, validation, publication, system improvement, and tool requirements.
Operations / implemented
Director and AgentJob lifecycle
Task, decision, AgentJob, completion, handoff, and registry evidence chain.
Open pageOperations / implemented
Role routing
Role templates, execution-role records, task overlays, provisional roles, and allowlists.
Open pagePG-019 / implemented
Validator PASS limits
Why command PASS is checked-state evidence, not theorem proof, claim promotion, role authority, or Gate Chair approval.
Open pageOperations / implemented
Publication process
Brief, source spec, public page, screenshot evidence, and review discipline.
Open pagePG-020 / implemented
Project-system improvement
Signals, sidecars, classifiers, advisory resolver output, one bounded maintenance packet, and explicit closure evidence.
Open pageOperations / implemented
Technical requirements
Local tool tiers for reproducible operation without confusing tools with authorization.
Open pageRelated reading
Continue through internal routes first.
These links keep the primary reader journey inside the website. Source links remain visible in the provenance section.
Director and AgentJob lifecycle
How tasks narrow into decisions, jobs, completions, handoffs, and registry evidence.
Open routeRole routing
Why role names are templates, while execution records and AgentJobs control one transaction.
Open routeValidator and operator workflow
How checks, receipts, screenshots, and PASS results should be interpreted.
Open routePublication process
How public explainers move from brief to source spec, page, screenshots, and review.
Open routeProject-system improvement
How classifiers, signals, sidecars, receipts, and one bounded AgentJob structure repairs.
Open routeTechnical requirements
Local tool tiers for reproducible operation without confusing tools with authorization.
Open routeAI Research-Agent System
Conceptual track landing page for the governed AI research-agent system.
Open routeSource Authority
How to read website pages, generated derivatives, registries, and source records.
Open routeSource 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.
Director and AgentJob lifecycle source
Reviewed generated noncanonical source for the operational lifecycle page.
Inspect sourceRole routing source
Reviewed generated noncanonical source for the role-routing page.
Inspect sourceValidator workflow source
Reviewed generated noncanonical source for the validator/operator page.
Inspect sourcePublication process source
Reviewed generated noncanonical source for the publication-process page.
Inspect sourceProject-system improvement source
Reviewed generated noncanonical source for the improvement-loop page.
Inspect sourceTechnical requirements source
Reviewed generated noncanonical source for local operation requirements.
Inspect sourceResearch-control guide
Committed control source for routing, validation, and operational evidence boundaries.
Inspect sourcePublication process standard
Committed source for brief-first publication and human review discipline.
Inspect sourceProject-control script guide
Committed tooling source for project-system classifier, resolver, sidecar, and receipt workflows.
Inspect source