Expose current frontier to proposal Modeling

This commit is contained in:
Meta Vens 2026-08-07 15:26:41 +01:00
commit 58cf898497
4 changed files with 46 additions and 5 deletions

View file

@ -399,7 +399,19 @@ pub fn append_modeling_repo_model_shape_context(
node.id, node.domain_id, node.title
));
}
context.push_str("New nodes must reference one exact existing domain id. Every unresolved frontier item must target at least one exact existing claim id from existingClaims, or a claim id created by the same patch. RepoArchitecture and RepoDataflow nodes/edges may use only observed, proposed, accepted, stale, or retired lifecycle. Prefer accepted for a source-grounded current claim. Do not invent a domain because RepoModel patches have no domain mutation operation.\n");
context.push_str("existingFrontier:\n");
for item in &snapshot.frontier {
let status = debug_variant_snake_case(item.status);
context.push_str(&format!(
"- id={} status={} recommendedNextOrgan={} targetClaims={} sourceScope={}\n",
item.id,
status,
item.recommended_next_organ,
item.target_claim_ids.join(" | "),
item.source_scope.join(" | "),
));
}
context.push_str("New nodes must reference one exact existing domain id. Every unresolved frontier item must target at least one exact existing claim id from existingClaims, or a claim id created by the same patch. Use upsert_frontier only for a genuinely new frontier id not listed in existingFrontier. Use revise_frontier when changing an id listed in existingFrontier; an existing frontier id cannot be upserted again. RepoArchitecture and RepoDataflow nodes/edges may use only observed, proposed, accepted, stale, or retired lifecycle. Prefer accepted for a source-grounded current claim. Do not invent a domain because RepoModel patches have no domain mutation operation.\n");
context.push_str("</canonical_repo_model_shape>");
Ok(context)
}
@ -1361,6 +1373,9 @@ mod tests {
assert!(shape.contains("id=repo"));
assert!(shape.contains("existingClaims:"));
assert!(shape.contains("id=claim-modeling-authority domain=repo"));
assert!(shape.contains("existingFrontier:"));
assert!(shape.contains("id=frontier-modeling-handoff status=active"));
assert!(shape.contains("Use revise_frontier when changing an id listed in existingFrontier"));
assert!(shape.contains("Prefer accepted"));
fs::remove_dir_all(&temp)?;
Ok(())

View file

@ -1162,6 +1162,14 @@ an equality assertion over Self's derived request. This cuts the split owner
exposed when exact `881b2b1a` saw the live v23 proposal but remained in manual
regather.
Proposal Modeling receives the canonical RepoModel shape, including current
domain, claim, and frontier identity. `existingFrontier` is the operation
boundary: `upsert_frontier` creates only a genuinely new id, while
`revise_frontier` changes an id already owned by Modeling. Admission still
fail-closes both mistakes. This context is required because exact `737f2b94`
correctly routed a live proposal but the worker, deprived of the frontier
inventory, attempted to upsert an existing item and was rejected.
The autonomous proposal crossing is source-grounded in
`runtime_spine.rs`, `admitted_model_direction_consideration.rs`,
`coordinator_launch.rs`, and `repo_model_gateway.rs`. A deployment-configured

View file

@ -189,6 +189,24 @@ Debug status over live v23 now derives `launchModeling` and that exact request.
Package and publish the repair before retrying; do not use `881b2b1a` to bypass
its own finding.
Exact `737f2b94` was subsequently packaged and published as
`sha256-b6dfa923a10cab369d56bcbf5d87c2b2da76bc5c3a7f3007ba228f4a63a3564f`
with witness
`sha256-185bd9a3a8657bd9f6cf6a4d158d6368db73363e57ee900ad9cdee265ed6cf82`.
Live v23 proved canonical Self selected `launchModeling` without
`--proposal-modeling-request-id`. The proposal-bound result was not admitted:
it attempted `upsert_frontier` for the already-present
`frontier-eyes-release-topology-evidence-r1`, and Soul superseded the result.
The request is consumed and v23 is revision 19. Do not replay it.
The cause was missing Body context, not weak rejection. Modeling launch context
listed current domains and claims but omitted current frontier items, so the
worker could not know whether a frontier id required insert or revision. The
local repair adds `existingFrontier` to the canonical RepoModel shape and states
the typed contract: upsert only new ids, revise existing ids. The focused
canonical-model launch-context test passes. Commit/package/publish this repair,
then use one fresh legitimate proposal to continue the native lifecycle.
## Immediate re-entry
1. Run `cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-state -- status`.

View file

@ -34,9 +34,9 @@ invariants:
- Evidence and git retain history; this map retains only state that changes future decisions.
current_status:
summary: Epiphany is a supervised engineering alpha on Starfire, not deployment-ready. Exact 881b2b1a packaged and published the native Imagination lifecycle, then live v23 exposed a remaining split owner: a legitimate selected user proposal existed, but Self status stayed in manual regather because proposal routing lived in a narrow CLI rewrite. No worker launched. The local repair now derives the single unclaimed proposal Modeling request from CultCache, routes it before regather, and makes the CLI request ID assertion-only. Live debug status derives launchModeling for the exact pending request; 20 coordinator and 14 MVP tests pass. A new exact package and live proof remain open. Persona consequence, Continuity recovery, retention, long-duration pacing, and Linux/Yggdrasil cognition remain open.
summary: Epiphany is a supervised engineering alpha on Starfire, not deployment-ready. Exact 737f2b94 is authenticated and published; live v23 proved Self derives and launches a selected proposal without a CLI routing override. Soul then correctly rejected the proposal-bound Modeling patch because it tried to upsert an existing frontier id. Diagnosis found that canonical launch context exposed domains and claims but omitted the current frontier inventory, so the invalid operation was locally reasonable. The local repair now exposes existing frontier identity and makes the upsert-new/revise-existing contract explicit. Its focused context test passes; exact packaging and a fresh legitimate proposal remain open. Persona consequence, Continuity recovery, retention, long-duration pacing, and Linux/Yggdrasil cognition remain open.
operational_state:
local_worktree: pending_proposal_native_status_repair_uncommitted
local_worktree: proposal_modeling_frontier_context_repair_uncommitted
operator_wireguard: restored
yggdrasil: canonical_small_public_crossing_body
starfire: temporary_epiphany_cognition_body
@ -52,8 +52,8 @@ current_status:
bifrost_feedback_crossing: authenticated_transport_only
yggdrasil_epiphany_services: absent
resident_physiology: heartbeat_and_self_running
unresolved_authority: v23 holds accepted Eyes, reorientation, causal Modeling evidence, and one legitimate unclaimed proposal Modeling request. Exact 881b2b1a is authenticated but cannot route that proposal from manual regather. The local native-status repair is test-proven but unpublished. Native Imagination live proof, Persona consequence, Continuity crash/restart/closure, retention, long-duration behavior, and Linux/Yggdrasil cognition remain open.
next_action: Commit, package, and publish the native pending-proposal routing repair. Retry packaged Self on v23 without using the CLI ID as a routing override; prove status itself launches the exact proposal-bound Modeling request, then continue through admitted Imagination and dedicated Mind decision. Do not recreate the proposal, inject a frontier, or mutate v22.
unresolved_authority: v23 revision 19 holds the consumed proposal request and a superseded Modeling admission after Soul rejected an upsert of existing frontier-eyes-release-topology-evidence-r1. Exact 737f2b94 proved native Self routing. The local frontier-context repair is focused-test-proven but unpublished. Native Imagination live proof, Persona consequence, Continuity crash/restart/closure, retention, long-duration behavior, and Linux/Yggdrasil cognition remain open.
next_action: Commit, package, and publish the proposal-Modeling frontier-context repair. Then create one fresh legitimate typed proposal for the still-open release-auth ownership seam, let Self derive its Modeling launch without overrides, and prove a valid revise-or-new-frontier admission before continuing through Imagination and dedicated Mind. Do not replay the consumed request or mutate v22.
active_subgoals:
- Prove Persona, Self, Eyes, Modeling, Imagination, Hands, Soul, Mind, Continuity, and nervous-system behavior individually.