Ground blocked owner strips with direct disassembly
This commit is contained in:
parent
dc04ef085d
commit
fa19d1b89a
4 changed files with 38 additions and 1 deletions
|
|
@ -3669,6 +3669,7 @@ fn build_region_service_trace_report(
|
|||
evidence: vec![
|
||||
"atlas already bounds this owner as the direct consumer of [region+0x276], [region+0x302], and [region+0x316]".to_string(),
|
||||
"the new region trace already proves the record envelope and profile subcollection, so the remaining gap is the separate persisted latch seam rather than the service owner".to_string(),
|
||||
"direct disassembly now shows 0x004358d0 calling 0x00420030 twice plus 0x00420280, resolving the linked company through 0x0047efe0, posting company stat slot 4, and then clearing [region+0x276] while stamping [region+0x302] or [region+0x316]".to_string(),
|
||||
],
|
||||
blockers: vec![
|
||||
"persisted owner seam for [region+0x25e/+0x276/+0x302/+0x316]".to_string(),
|
||||
|
|
@ -3864,6 +3865,7 @@ fn build_infrastructure_asset_trace_report(
|
|||
),
|
||||
"atlas already bounds these helpers under the literal Infrastructure owner".to_string(),
|
||||
"the side-buffer corpus is disjoint from the placed-structure triplet corpus, so a separate child/rebuild family is more plausible than a compact alias".to_string(),
|
||||
"direct disassembly now shows 0x0048a1e0 cloning the first child triplet bands through 0x52e880/0x52e720, destroying the prior child, seeding a new literal Infrastructure child through 0x455b70 with payload seed 0x5c87a8, attaching through 0x5395d0 or 0x53a5d0, and republishing the two bands through 0x52e8b0/0x530720".to_string(),
|
||||
],
|
||||
blockers: vec![
|
||||
"exact compact-prefix regime semantics".to_string(),
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue