Status
Claim Status
Inspect claimed, not claimed, blocked, and open language boundaries.
Open routePhysics Research / Open Burdens
This route lists the derivation obligations that remain open, blocked, scoped, or human-gated. It is a burden map, not evidence that the obligations are solved.
The Æther Flow Project is a two-part research program about foundational physics and the governed, human-accountable AI research system used to organize and test that work. Its physics track asks whether ordinary general relativity can be interpreted, and eventually derived, from a deeper Æther or Æther-Flow foundation; exact GR remains the observable-scale benchmark, while that first-principles derivation is still open.
This Open Burdens page reads a checked-in snapshot of the missing links as separate obligations, from source structure and metric construction through matter coupling, Einstein equations, benchmark promotion, and protected human review, so one partial result cannot silently stand in for the whole chain. Ledger rows and status counts describe which work exists, which prerequisite is missing, and which gate applies; they are not a percentage score, and scoped evidence for one step does not solve the steps after it.
By making both constructive work and recorded obstructions visible, the page helps readers understand what the project must still establish without treating one blocked route as a rejection of the entire research program. If the snapshot becomes stale, the page remains orientation only, while upstream source records and human gates continue to govern stronger conclusions.
Static diagram
The dashboard boundary diagram keeps Distance-to-GR ledger rows, blockers, and burden labels visible while preventing a progress-bar interpretation.
Open burden dossier
The rows below put matter coupling, Einstein equations, benchmark promotion, and Gate Chair status beside their blockers instead of collapsing them into a single success narrative.
| Burden | Current status | What remains missing | Blocked overread |
|---|---|---|---|
| Active Distance-to-GR burden | draft object exists | general equivalence under variations | No active burden means no current ledger movement, not completed derivation. |
| matter coupling | accepted | PositiveMSProfile_v1 RR_ETransportCompletenessOrInvarianceLaw_v1 NarrowMSCertEq_v1 SourceCertificateAlgebraPrimitives_v1 and SourceCertificateOperationLaws_v1 are accepted or drafted only as scoped source-extension evidence/preconditions evidence-status draft/control certificate primitives or draft/control operation-law support under declared source-side and fail-closed scope while no source-law adoption no RR_ETransportCompletenessOrInvarianceLaw_v1 adoption no PositiveMSProfile_v1 adoption no SourceMatterSemanticsAdoptionReadinessLaw_v1 law adoption no source-extension data adoption beyond exact scoped gate result no matter-semantics adoption no detector-semantics adoption no coupling-law adoption no matter-coupling derivation no stress-energy semantics no matter action no MetricData(E) adoption no g_eff scope expansion no Einstein-equation premise no benchmark fit and no downstream promotion occurred | RT-20260702-064 proved draft/control conditional source certificate operation laws and fail-closed lemmas including identity declared-scope preservation compatible composition closure restriction closure malformed fail-closed target-import invalidity and the OB-P3T02-MISSING-CERT-RRE-SEPARATION-DATA branch. No source-law RR_ETransportCompletenessOrInvarianceLaw_v1 unrestricted RR_E theorem PositiveMSProfile SourceMatterSemanticsAdoptionReadinessLaw matter-semantics detector-semantics coupling-law matter-coupling stress-energy matter-action MetricData(E) g_eff Einstein-equation benchmark completed-derivation future-source-extension-impossibility or global-theory-rejection adoption or promotion occurred. |
| Einstein equations | not started | dynamics action or variation | no Einstein-equation derivation supplied |
| benchmark promotion | blocked by missing primitive | all upstream derivation burdens | benchmark promotion remains blocked |
| Gate Chair status | human-gated | protected verdict authority | Gate Chair review remains blocked |
Reader rule
The ledger is useful because it keeps unlike obligations separate. Scalar progress would hide the different proof, construction, and gate requirements.
| Rule | Reason | Consequence |
|---|---|---|
| No percentage score | Derivation burdens are heterogeneous: source ontology, metric behavior, matter coupling, equations, benchmark promotion, and human gates cannot be collapsed into one scalar. | The page reports row state and missing steps instead of a progress bar proof. |
| Scoped acceptance stays scoped | Some rows can be accepted as source-extension evidence or preconditions while downstream claims remain blocked. | Acceptance language must preserve no source-law adoption, no matter-coupling derivation, no Einstein equations, and no benchmark promotion when those are still absent. |
| Human gates stay human-gated | Gate Chair status requires protected verdict authority outside website validators. | Validation PASS and public readability cannot substitute for a protected review decision. |
Ledger groups
Grouping helps readers find burden families without making one family discharge another.
| Group | Rows | Status classes | Reader meaning |
|---|---|---|---|
| Source foundation | 6 | draft object exists; blocked by missing primitive; constructive witness exists; accepted | Ontology, source equivalence, retention, generation, localization, and response rows. |
| Metric and bridge rows | 2 | accepted | Source manifold and effective metric rows that remain narrower than downstream GR promotion. |
| Downstream GR burdens | 4 | accepted; not started; blocked by missing primitive; human-gated | Matter coupling, Einstein equations, benchmark promotion, and protected Gate Chair status. |
| Negative and control rows | 2 | Refuter stress passed; frozen negative | Finite robustness and frozen toy-model rows that guide routing without proving global failure. |
Snapshot counts
Counts are useful operational metadata. They are not a proof score, and they do not convert accepted scoped rows into downstream derivations.
| Status | Rows | How to read it |
|---|---|---|
| accepted | 4 | A count of ledger rows in this status class, not a measure of derivation completion. |
| blocked by missing primitive | 3 | A count of ledger rows in this status class, not a measure of derivation completion. |
| constructive witness exists | 1 | A count of ledger rows in this status class, not a measure of derivation completion. |
| draft object exists | 2 | A count of ledger rows in this status class, not a measure of derivation completion. |
| frozen negative | 1 | A count of ledger rows in this status class, not a measure of derivation completion. |
| human-gated | 1 | A count of ledger rows in this status class, not a measure of derivation completion. |
| not started | 1 | A count of ledger rows in this status class, not a measure of derivation completion. |
| Refuter stress passed | 1 | A count of ledger rows in this status class, not a measure of derivation completion. |
Freshness and source basis
The route displays source-basis metadata so readers can see the checked state behind the page.
| Field | Value | How to read it |
|---|---|---|
| Snapshot refresh date | 2026-06-29 | The burden data is checked in. If freshness cannot be verified, fail closed and avoid stronger claims. |
| Source commit | 53aea4bfed31... | The commit identifies the source basis used to generate the snapshot. |
| Latest handoff | handoff-0323 | The handoff id is context, not a proof surface or permanent website truth. |
| Ledger rows | 14 | Row count describes scope of the snapshot, not percentage progress toward GR. |