01
Current State
Dated implementation-control context, source-basis warnings, and bounded validation status.
Open routeAI Research System
AI Research System
Read this category as the governed workflow around the research, not as an autonomous proof engine.
The Æther Flow Project is a two-part research program about foundational physics and the governed, human-accountable AI research system used to organize that work. Its physics track asks whether ordinary general relativity can be interpreted, and eventually derived, from a deeper Æther or Æther-Flow foundation; for now, general relativity remains the exact benchmark for observable gravity, while the first-principles substrate derivation is still open.
The AI track turns each research request into a small, inspectable unit by recording the task, checking source material, limiting one AgentJob to named roles and allowed actions, running validators, and preserving completion and handoff evidence, with protected decisions left to a human Director or another explicit gate.
This overview shows how those records connect so a general reader can follow who may act, what evidence is required, and where the work stops or passes onward. An AI output, a validator PASS, or a completed workflow can document an operational result, but it does not by itself prove a physics claim or expand the authority granted by source records.
Static diagram
Read the AI research system as task authority, not autonomous proof.
The authority map shows request classification, source authority, task records, AgentJobs, validators, and bounded outputs in one controlled chain.
Reader route map
Start with the workflow boundary, then inspect the parts.
The overview is stable public orientation. The current-state page is dated snapshot context. Later pages explain the record chain, roles, validators, memory, runtime, and improvement loop.
02
Workflow
Request routing, memory/source checks, Director decisions, one bounded AgentJob, and completion evidence.
Open route03
AgentJob Lifecycle
One job envelope from allowlist through validators, completion, handoff, and checkpoint.
Open route04
Roles and Schemas
Role labels, schemas, execution-role records, and job-local authority boundaries.
Open route05
Validators and Handoffs
Operational PASS, completion receipts, handoff limits, and blocked overreads.
Open route06
Memory Preflight
Memory and retrieval as source-navigation support, not source authority.
Open route07
Project-System Improvement
Bounded repair loops for workflow and tooling issues without smuggling research continuation.
Open route08
Runtime Requirements
Tool, validator, environment, and checkpoint requirements as operational evidence.
Open routeWorkflow status
Operational rigor is useful because it stays bounded.
The public claim is not that AI proves physics. The public claim is that the research workflow is designed to make work inspectable, narrow, reversible, and accountable.
| Layer | Safe use | Boundary |
|---|---|---|
| Reader entry | The category explains why the project uses governed AI-supported research infrastructure. | It does not present AI systems as autonomous proof authorities. |
| Bounded work | One invocation narrows into one task, one AgentJob, one allowlist, and one completion record. | A job cannot silently add objectives, write paths, or claim authority. |
| Source-first evidence | Memory, registries, and generated summaries help locate source files and records. | Navigation layers do not replace source inspection or tracked authority. |
| Validation and handoff | Validators and handoffs make a checked state inspectable and preserve next-route context. | Validation PASS is operational consistency, not scientific proof. |
| Human accountability | Promotion, adoption, protected verdicts, and publication decisions stay explicit and gated. | Generated output cannot replace human-gated responsibility. |
Source basis
The category explains source-backed artifact classes.
Stable overview copy should describe artifact classes and boundaries. Moving task and handoff details belong in dated current-state context.
| Source area | Used here for | Authority boundary |
|---|---|---|
| Research-agent workflow sources | Governed workflow, one-job rule, AgentJob lifecycle, completions, handoffs, and validator limits. | Workflow evidence remains operational and source-bound. |
| Role, memory, and registry explainers | Role labels, skills, memory preflight, and retrieval-layer boundaries. | Labels and retrieval hits are not current execution authority. |
| Current-state rules | Dated snapshot behavior and stale-data warnings for moving implementation-control context. | Transient state belongs in current-state pages, not stable overview claims. |