Positive objective
Build and promote the framework's first parameter-closed emergent-gravity stack: start from accepted substrate dynamics, derive rather than assume a generally covariant low-energy gravitational action and its normalization, obtain a controlled nonflat sourced spacetime, and show that both massive and massless probes follow from the same derived geometry. The completed construction must make at least one static and one radiative held-out prediction from the same frozen parameter ledger.
This is an objective-level successor to the unresolved frontier documented in #12 and must respect the Route-2 no-go established in #9. It may reuse their correct artifacts and rejected-route evidence, but neither issue's narrative is authority.
Why this is the highest-value next goal
Release v0.160.0 now contains strong but separate pieces:
- conditional induced-coupling and identifiability bookkeeping (
C-GRV-001);
- exact effective geometry without physical gravity (
C-GOR-001);
- Einstein-scalar consumers whose gravitational coupling is supplied (
C-STG-001, C-STG-002);
- conditional static/radiative geometry and quadrupole consumers (
C-GW-*);
- accepted massive, massless, reparametrization, and conformal worldline mechanics (
C-WLN-001..003).
The framework still lacks the load-bearing bridge that makes these one theory: no accepted substrate mechanism derives the gravitational action, fixes its usable normalization and corrections, generates a nontrivial physical spacetime, and sends both matter and radiation through that same result. Closing that bridge would turn several conditional sectors into a coherent predictive stack.
What counts as real success
The issue closes only when one coherent, independently reviewed construction does all of the following:
- Derives a low-energy metric/connection action from accepted framework degrees of freedom and explicitly approved imports. Its leading regime is generally covariant and Einstein-equivalent, or a separately governed foundational revision proves that the smallest coherent alternative is required.
- Derives the usable gravitational normalization and the regime of validity. A free additive baseline, fitted Newton constant, borrowed Einstein-Hilbert coefficient, arbitrary field-to-metric rescaling, or comparator-selected regulator/field content does not close the goal. Any renormalization condition must itself have declared, reviewable provenance.
- Controls every term that can defeat the claimed regime, including the cosmological and leading higher-curvature/dispersion/Lorentz-violating sectors as applicable. They may be derived, cancelled by a justified mechanism, or bounded in a predeclared domain; they may not be omitted silently.
- Produces at least one controlled, nonflat sourced solution of the derived field equations, with conservation, boundary/initial data, existence or numerical-convergence evidence, and known-limit checks appropriate to the claim.
- Composes
C-WLN-001..003 with that same solution so massive and massless probes obtain the correct timelike/null dynamics without supplying a second geometry or force normalization.
- Produces at least two independent consequences from the same frozen inputs: one static/weak-field observable and one radiative/dynamical observable. At least one must be confronted with a held-out empirical or independently established GR benchmark under a preregistered error model. Algebraically equivalent restatements do not count as independent predictions.
- Promotes only the claims that individually pass the repository's success definition: importable APIs and tests, sensitive strongest-practical oracles, independent rederivation, full dependency replay, claim-level review, synchronized registry/release/generated docs/memory, and no debt inside the promoted scope.
A no-go, wrong sign, uncontrolled correction, nonidentifiability result, failed comparator, or useful partial API is durable attempt/harvest evidence. It advances the campaign but is not completion; continue with a materially different candidate unless the user changes the objective.
Scientific freedom
The implementing agent owns the scientific strategy. This issue does not prescribe an induced-action route, regulator, field content, ansatz, discretization, representation, or proposal sequence. Compare plausible concepts under the candidate-first workflow and let framework fit and evidence select the route. Do not retrofit accepted invariants around a favored mechanism.
Accepted base is v0.160.0. Audit before reuse at minimum:
These are starting evidence, not mandatory ingredients. Reuse only what survives source audit and exact dependency matching.
Custom IPython harness contract
The stress-test harness must expose the entire repository workflow catalog to the agent and record which routes were actually invoked. Native skill discovery is preferred; otherwise it must resolve and read the corresponding SKILL.md in full. Reference skill names rather than hard-coding this workstation's absolute paths.
Required instruction and skill references
AGENTS.md — normative scientific, governance, validation, and non-self-merge contract.
AGENTS_START_HERE.md — authority, issue/branch coordination, memory, GitNexus, PR, review, and handoff workflow.
physics-erdos-loop — .agents/skills/physics-erdos-loop/SKILL.md; mandatory for this campaign, including every routed reference needed by the selected oracle and phase.
research-pr-harvest — .agents/skills/research-pr-harvest/SKILL.md; mandatory when a scientific PR is reviewed, harvested, narrowed, or handed off.
shared_agent-memory-usage — tools/agent-memory/skills/shared_agent-memory-usage/SKILL.md when the harness needs memory CLI syntax; repository memory remains an index/work record, not authority.
- GitNexus skill catalog:
gitnexus-guide, gitnexus-cli, gitnexus-exploring, gitnexus-impact-analysis, gitnexus-debugging, gitnexus-refactoring, and gitnexus-pr-review. The harness must advertise all seven and invoke each when its trigger applies; merely listing them is not evidence that their workflow ran.
Required workflow behavior
- Clean startup: show repository root, exact commit/branch, dirty files, current release, open issues/PRs, resolved instruction files, available tools, and resolved skill catalog before substantive work.
- Authority and recall: read accepted release/claims and relevant canonical sources; search repository memory and verify useful hits at source; inspect both source text and the refreshed GitNexus graph.
- Durable contracts before computation: instantiate the research-arc, effort, and campaign proposal contracts that apply; validate the proposal manifest/schema before opening source bodies or comparator values. Register competing candidates and structural criteria first.
- Blinding: the harness must be able to withhold empirical comparator values until the proposal's equations, conventions, candidates, and selection criteria are frozen. Comparator leakage into startup context must be reported.
- Honest execution capture: every shell, Python, SymPy, SciPy, Lean, or verifier run records the exact command/cell, working directory, inputs, stdout/stderr, wall time, and return status. A green tail with a nonzero process status is failure. Notebook variables or prior cell order may not be hidden premises.
- Fresh replay: before each durable milestone/PR, restart the IPython kernel and replay the claimed evidence from a clean checkout/state. Save reusable code in
src/substrate_framework/, tests, proposal/campaign artifacts, or memory—not only in notebook state.
- Attempt continuity: record attempts append-only, classify failures, harvest correct reusable units without closing this goal, and continue to a materially different route. Do not stop because a finite run, token budget, or first candidate ended.
- Impact and validation: use GitNexus impact before canonical changes and change detection on the final diff; run claim-appropriate oracle/mutation/refinement/consumer checks and the required scoped or full repository validation once at the unchanged boundary, then
git diff --check separately.
- PR lifecycle: every PR uses this issue as its one canonical issue. Use
Advances #N until every objective-level gate above is complete; reserve Fixes #N for the final closure transaction. The authoring/implementing agent never merges its own work. A distinct reviewer and merger apply the review/harvest workflows and leave the unit-level issue handoff.
The harness should fail visibly when a required reference or tool is unavailable, but absence is not permission to weaken the scientific objective. It may pause for genuinely missing authority or external inputs while preserving the continuation state.
Coordination boundary
The first agent to take the goal must comment with its branch, proposal/claim identifiers after collision search, selected initial slice, intended write surfaces, and comparator-blinding point before editing. Avoid concurrent edits to those declared surfaces. Focused milestone PRs are welcome when they add independently correct reusable units, but merged milestones create provenance—not automatic claim promotion or goal closure.
This issue remains the single canonical objective until real success or an explicit owner decision changes it.
Positive objective
Build and promote the framework's first parameter-closed emergent-gravity stack: start from accepted substrate dynamics, derive rather than assume a generally covariant low-energy gravitational action and its normalization, obtain a controlled nonflat sourced spacetime, and show that both massive and massless probes follow from the same derived geometry. The completed construction must make at least one static and one radiative held-out prediction from the same frozen parameter ledger.
This is an objective-level successor to the unresolved frontier documented in #12 and must respect the Route-2 no-go established in #9. It may reuse their correct artifacts and rejected-route evidence, but neither issue's narrative is authority.
Why this is the highest-value next goal
Release
v0.160.0now contains strong but separate pieces:C-GRV-001);C-GOR-001);C-STG-001,C-STG-002);C-GW-*);C-WLN-001..003).The framework still lacks the load-bearing bridge that makes these one theory: no accepted substrate mechanism derives the gravitational action, fixes its usable normalization and corrections, generates a nontrivial physical spacetime, and sends both matter and radiation through that same result. Closing that bridge would turn several conditional sectors into a coherent predictive stack.
What counts as real success
The issue closes only when one coherent, independently reviewed construction does all of the following:
C-WLN-001..003with that same solution so massive and massless probes obtain the correct timelike/null dynamics without supplying a second geometry or force normalization.A no-go, wrong sign, uncontrolled correction, nonidentifiability result, failed comparator, or useful partial API is durable attempt/harvest evidence. It advances the campaign but is not completion; continue with a materially different candidate unless the user changes the objective.
Scientific freedom
The implementing agent owns the scientific strategy. This issue does not prescribe an induced-action route, regulator, field content, ansatz, discretization, representation, or proposal sequence. Compare plausible concepts under the candidate-first workflow and let framework fit and evidence select the route. Do not retrofit accepted invariants around a favored mechanism.
Accepted base is
v0.160.0. Audit before reuse at minimum:governance/releases/current.yamlandgovernance/claims.yaml;src/substrate_framework/covariant_sine_gordon_action.pyandscalar_induced_newton.pyas unpromoted/review-bounded prior work;C-GRV-001,C-GOR-001,C-STG-001/002,C-GW-*, andC-WLN-001..003.These are starting evidence, not mandatory ingredients. Reuse only what survives source audit and exact dependency matching.
Custom IPython harness contract
The stress-test harness must expose the entire repository workflow catalog to the agent and record which routes were actually invoked. Native skill discovery is preferred; otherwise it must resolve and read the corresponding
SKILL.mdin full. Reference skill names rather than hard-coding this workstation's absolute paths.Required instruction and skill references
AGENTS.md— normative scientific, governance, validation, and non-self-merge contract.AGENTS_START_HERE.md— authority, issue/branch coordination, memory, GitNexus, PR, review, and handoff workflow.physics-erdos-loop—.agents/skills/physics-erdos-loop/SKILL.md; mandatory for this campaign, including every routed reference needed by the selected oracle and phase.research-pr-harvest—.agents/skills/research-pr-harvest/SKILL.md; mandatory when a scientific PR is reviewed, harvested, narrowed, or handed off.shared_agent-memory-usage—tools/agent-memory/skills/shared_agent-memory-usage/SKILL.mdwhen the harness needs memory CLI syntax; repository memory remains an index/work record, not authority.gitnexus-guide,gitnexus-cli,gitnexus-exploring,gitnexus-impact-analysis,gitnexus-debugging,gitnexus-refactoring, andgitnexus-pr-review. The harness must advertise all seven and invoke each when its trigger applies; merely listing them is not evidence that their workflow ran.Required workflow behavior
src/substrate_framework/, tests, proposal/campaign artifacts, or memory—not only in notebook state.git diff --checkseparately.Advances #Nuntil every objective-level gate above is complete; reserveFixes #Nfor the final closure transaction. The authoring/implementing agent never merges its own work. A distinct reviewer and merger apply the review/harvest workflows and leave the unit-level issue handoff.The harness should fail visibly when a required reference or tool is unavailable, but absence is not permission to weaken the scientific objective. It may pause for genuinely missing authority or external inputs while preserving the continuation state.
Coordination boundary
The first agent to take the goal must comment with its branch, proposal/claim identifiers after collision search, selected initial slice, intended write surfaces, and comparator-blinding point before editing. Avoid concurrent edits to those declared surfaces. Focused milestone PRs are welcome when they add independently correct reusable units, but merged milestones create provenance—not automatic claim promotion or goal closure.
This issue remains the single canonical objective until real success or an explicit owner decision changes it.