Physics deep dive / Phase 4D

Claim Gates

AEther Flow uses claim gates to keep proposals, audits, stress tests, completions, handoffs, freeze labels, and human-gated decisions inside their proper scope. The discipline is conservative: negative results are preserved without turning them into success or global rejection.

Claim gate lifecycle mapproposalaudit / stresshuman gate
Visual orientation only: the diagram explains scope control, not a physics verdict or Gate Chair decision.

Claim lifecycle

Each state narrows what can be said.

A useful packet can still be provisional. A failed packet can still be valuable. Neither condition widens claim authority beyond the tracked source boundary.

Proposal

A bounded packet

A proposal names a possible construction, selector, witness, audit, or review target. It is not accepted physics by itself.

Audit

A hidden-import screen

An audit checks whether a packet imports target-GR structure, role authority, generated-output authority, or hidden assumptions.

Stress

A refutation attempt

A stress test may expose fragility, nonuniqueness, missing primitives, or underdetermination. It does not reject the whole ontology.

Gate

A protected decision

Human-gated decisions such as Gate Chair approval or benchmark promotion require explicit protected authority, not validator success or public prose.

Negative-result discipline

Stopped, blocked, and frozen states remain scoped.

No-go records and obstruction records help the project avoid repeating weak routes. They do not prove the whole ontology false, and they do not secretly complete the derivation.

Scoped obstruction

Route-local evidence

A scoped obstruction says a specific route failed under stated assumptions and source data. It is narrower than a global no-go theorem.

Freeze label

Do not repeat casually

A freeze label preserves a repeated burden or blocked route so future work needs a new payload, redesign, audit, or gate action before reuse.

Blocked status

Not success

Blocked or stopped states preserve what remains missing. They should not be rewritten as completion, benchmark promotion, or hidden progress.

Validator pass

Operational evidence only

A validator can show a bounded transaction satisfied structural checks. It cannot prove g_eff, matter coupling, equations, or scientific truth.

Reader path

Read gates together with source authority and workflow.

Claim gates connect the physics track to the AI research-agent workflow: bounded jobs, role constraints, validators, completions, and handoffs can organize evidence while remaining separate from physics proof.

Source authority

What this page can and cannot establish.

This website page can explain the claim-control model. It cannot create a claim boundary, issue a Gate Chair verdict, promote a benchmark, reject the global ontology, change role authority, treat validator passes as scientific evidence, or supersede tracked source files.