Memory and registry refresh
Bootstrap, then validate
Generated registry, wiki, semantic, and memory derivatives refresh through the approved bootstrap path, then validate-only checks the result.
AI research-agent deep dive / Phase 5D
Validator And Operator Workflow
AEther Flow uses validators and operator receipts to keep changes bounded, reproducible, and reviewable. The central rule is conservative: a PASS result is operational evidence for the checked transaction, not a scientific verdict or authority expansion.
Command decision matrix
Choose checks by changed authority surface.
The operator question is not only which command runs. It is which evidence chain fits the risk of the changed files and the authority surface they touch.
Publication page work
Pair checks with screenshots
Public page changes need source grounding, static checks, and rendered desktop/mobile evidence because visual quality is not fully deterministic.
Project-system change
Classify and record impact
State-changing project-system work uses classifier, resolver, signal checks, documentation-impact receipts, research-control checks, and checkpoint gates.
Tooling change
Run focused tests
Script, validator, schema, role, or memory-tooling changes need focused tests in addition to the relevant control validators.
Evidence chain
Receipts explain what was checked and why.
Classifiers, documentation-impact records, validators, tests, screenshots, completions, and checkpoint gates answer different questions. They should not be collapsed into one generic green status.
Documentation impact
Why did this matter?
A documentation-impact receipt covers live source changes, generated derivatives, classifier reason codes, and required validators when project-system state changes.
Research-control validation
Did the tracked boundary hold?
Research-control checks validate task records, registries, handoffs, parent-child constraints, write boundaries, and diff allowlists.
Sidecar bridge
Was the exact path authorized?
Project-improvement sidecars are accepted only when changed source-bridge metadata names the exact YAML and Markdown pair.
Completion evidence
What actually passed?
A completion record owns command evidence for one bounded transaction. Signal closure requires explicit PASS evidence or a documented rejection decision.
PASS-result limits
Validator success is bounded evidence, not a scientific verdict.
Deterministic checks are necessary for operational integrity. They do not replace source inspection, human-gated authority, or scientific argument.
Deterministic acceptance
Necessary evidence
A PASS result can show that the named deterministic check accepted the current checked state.
No scientific verdict
Not theorem proof
Validator success does not prove ontology, derive GR, promote a benchmark, close a Gate Chair question, or certify a scientific claim.
No authority expansion
No hidden permission
A green check does not expand role authority, task-local allowlists, sidecar adoption status, generated-output authority, or routing behavior.
Review still matters
Human judgment remains
Publication quality, editorial clarity, and visual fit need screenshot review and source-boundary judgment in addition to deterministic checks.
Failure boundaries
A failed check is routing evidence, not an invitation to bypass.
Failures protect the record chain. The disciplined response is to narrow the packet, repair the receipt, synchronize the source stack, or stop for the proper authority.
Write-path failure
Narrow or stop
If a changed path falls outside the current allowlist, the correct response is a narrower packet or explicit authorization, not bypassing the check.
Orphan surface
Synchronize the stack
A public source spec, GitHub page, HTML output, or registry row without its paired source surface is a publication-process problem.
Resolver overread
Advisory is not a gate
Resolver output can guide routing, but checkpoint blocking comes from validators and concrete authority-boundary violations.
Sidecar overread
No global allowance
Conditional sidecar acceptance does not allow arbitrary changes under the sidecar directory and does not replace the research handoff spine.
Reader path
Read validation with workflow, memory, and source authority.
This page completes the first AI research-agent deep-dive family: workflow explains bounded transactions, roles explain authority, memory explains source finding, and validators explain operational checks.
Back to AI research-agent trackReturn to the AI track landing page for the completed first version of the AI deep-dive family.Research-agent workflowRead the bounded transaction chain behind command and receipt evidence.Memory and registriesRead how memory and registries support source-first routing without replacing source authority.Source authority pageReview the broader boundary between website pages, generated derivatives, and tracked sources.Upstream validator workflowGenerated noncanonical source-backed operator guide for validation and PASS-result limits.Upstream project-system loopGenerated noncanonical source-backed guide to project-system classification, signals, receipts, and sidecars.
Source authority
What this page can and cannot establish.
This page can orient readers to validation, deterministic checks, documentation impact, checkpoint boundaries, screenshot evidence, and operator receipts. It cannot change validator behavior, command semantics, routing behavior, checkpoint gates, sidecar adoption status, generated-output authority, or physics claim status.