Split acquisition region lane statuses

This commit is contained in:
Jan Petykiewicz 2026-04-18 19:17:22 -07:00
commit 23beba2a63
2 changed files with 34 additions and 5 deletions

View file

@ -3493,6 +3493,8 @@ pub struct SmpPeriodicCompanyServiceTraceReport {
#[serde(default)]
pub near_city_acquisition_remaining_owner_gaps: Vec<String>,
#[serde(default)]
pub near_city_acquisition_region_lane_statuses: Vec<String>,
#[serde(default)]
pub atlas_candidate_consumers: Vec<String>,
#[serde(default)]
pub known_bridge_helpers: Vec<String>,
@ -4147,10 +4149,16 @@ fn build_periodic_company_service_trace_report(
.to_string(),
];
let near_city_acquisition_remaining_owner_gaps = vec![
"persisted restore or rebuild owner for [region+0x276] pending amount before shellless 0x004014b0 can consume ordinary saves".to_string(),
"persisted restore or rebuild owner for [region+0x2a4] winning linked-company lane".to_string(),
"persisted restore or rebuild owner for [region+0x310/+0x338/+0x360] cached tri-lane sampled by 0x0040cac0".to_string(),
"stable save-native region class/type discriminator behind the vtable +0x80 byte-0x32 filter consumed through 0x0040d360".to_string(),
"save restore owner for [region+0x276] pending amount on ordinary saves, even though runtime producer 0x00422100 is grounded".to_string(),
"save payload or restore owner for [region+0x2a4] winning linked-company lane; current binary scan finds no region-class runtime writer".to_string(),
"save payload or restore owner for [region+0x310/+0x338/+0x360] cached tri-lane sampled by 0x0040cac0".to_string(),
"save-native projection of the region type byte consumed by 0x0040d360 as [owner_vtable+0x80+0x32] == 4".to_string(),
];
let near_city_acquisition_region_lane_statuses = vec![
"[region+0x276] pending amount lane: runtime producer grounded at 0x00422100, ordinary-save restore owner still missing".to_string(),
"[region+0x2a4] winning linked-company lane: consumed by 0x004014b0 and 0x0044554e0 path, no region-class runtime writer found in current binary scan".to_string(),
"[region+0x310/+0x338/+0x360] cached tri-lane: exact raw delta reader grounded at 0x0040cac0, payload/restore owner still missing".to_string(),
"region type filter: 0x0040d360 is the exact test [owner_vtable+0x80+0x32] == 4, but the save-native projection of that byte is still missing".to_string(),
];
let atlas_candidate_consumers = vec![
"0x004019e0 periodic company outer service owner".to_string(),
@ -4224,7 +4232,7 @@ fn build_periodic_company_service_trace_report(
let next_owner_questions = vec![
"Which persisted region and company linkage fields are still missing for a shellless 0x004014b0 implementation once the peer-site restore subset is accepted as sufficient to reconstruct the live runtime subset?".to_string(),
"How much of the linked-peer refresh path is strictly post-load versus recurring runtime maintenance now that 0x004133b0 reaches 0x0040ee10 -> 0x0040edf6 -> 0x00480710 during bring-up and 0x004160aa also re-enters 0x0040ee10 later?".to_string(),
"Which later restore or rebuild owner rehydrates the remaining region-side 0x004014b0 inputs [region+0x276], [region+0x2a4], and [region+0x310/+0x338/+0x360] once peer/company inputs are accepted as grounded?".to_string(),
"Which later restore or payload owner rehydrates the remaining region-side 0x004014b0 inputs [region+0x276], [region+0x2a4], and [region+0x310/+0x338/+0x360] once peer/company inputs are accepted as grounded?".to_string(),
"Which infrastructure consumer above the grounded 0x38a5 seam actually drives the linked-transit branch that 0x00409950 follows?".to_string(),
];
@ -4380,6 +4388,9 @@ fn build_periodic_company_service_trace_report(
notes.push(
"The shellless acquisition frontier is narrower now too: the peer-site selector/linked-peer seam is grounded enough to plan around, and the company/chairman side already sits on existing runtime-backed stat-family and save-native roster inputs. The remaining blocker is region-side restore or rebuild ownership for [region+0x276], [region+0x2a4], and the cached tri-lane [region+0x310/+0x338/+0x360], plus the stable class/type discriminator consumed through 0x0040d360.".to_string(),
);
notes.push(
"Direct disassembly now tightens the remaining region lanes too: 0x00422100 itself writes the pending amount lane [region+0x276], so that field is no longer an unknown producer, only an ordinary-save restore gap; 0x0040cac0 is only the raw tri-lane delta reader over [region+0x310/+0x338/+0x360]; 0x0040d360 is only the exact type test [owner_vtable+0x80+0x32] == 4; and the current binary write scan finds no region-class runtime writer for [region+0x2a4], which now makes that winning linked-company lane look payload/restore-owned rather than service-produced.".to_string(),
);
notes.push(
"That branch also reuses the same peer-site helper strip already bounded under the city-connection family: 0x0041f6e0 resolves the current center world-grid cell and checks one packed token through 0x0042b2d0, 0x0047de00 follows the linked region behind the candidate site into the status byte returned by 0x0040c990, and 0x004801a0 checks whether one candidate site is reachable from the cached company route anchor through the pending-bonus companion path 0x00425b90 -> 0x00401860 -> 0x0048e3c0.".to_string(),
);
@ -4416,6 +4427,7 @@ fn build_periodic_company_service_trace_report(
near_city_acquisition_shellless_readiness_status,
near_city_acquisition_runtime_backed_input_families,
near_city_acquisition_remaining_owner_gaps,
near_city_acquisition_region_lane_statuses,
atlas_candidate_consumers,
known_bridge_helpers,
next_owner_questions,
@ -26107,6 +26119,7 @@ mod tests {
5
);
assert_eq!(trace.near_city_acquisition_remaining_owner_gaps.len(), 4);
assert_eq!(trace.near_city_acquisition_region_lane_statuses.len(), 4);
assert!(trace.atlas_candidate_consumers.iter().any(|line| {
line.contains("0x00420030 / 0x00420280")
&& line.contains("0x006cec20")
@ -26147,6 +26160,13 @@ mod tests {
.iter()
.any(|line| line.contains("[region+0x276]"))
);
assert!(
trace
.near_city_acquisition_region_lane_statuses
.iter()
.any(|line| line.contains("[region+0x2a4]")
&& line.contains("no region-class runtime writer"))
);
assert!(trace.next_owner_questions.iter().any(|line| {
line.contains("0x004160aa")
&& line.contains("0x0040ee10")

View file

@ -140,6 +140,15 @@ Working rule:
remaining owner gaps
`[region+0x276]`, `[region+0x2a4]`, `[region+0x310/+0x338/+0x360]`, and the stable region
class/type discriminator consumed through `0x0040d360`
- use the new per-lane region status split in the same trace:
`[region+0x276]` already has a grounded runtime producer at `0x00422100` and is now only an
ordinary-save restore gap;
`[region+0x2a4]` currently has no region-class runtime writer in the binary scan and now looks
payload/restore-owned;
`[region+0x310/+0x338/+0x360]` has an exact raw delta reader at `0x0040cac0` but still lacks a
payload/restore owner;
`0x0040d360` is now exact as `[owner_vtable+0x80+0x32] == 4`, so the remaining gap there is
only the save-native projection of that byte
- make the next periodic-company slice about the smaller shellless-simulation question instead:
which later restore or rebuild owner rehydrates the remaining region-side `0x004014b0` inputs
once the peer/company inputs are treated as grounded