Y2E-130 — Establish the safe initial Linux RAM map
> **Historical record.** The dates, candidate identity, "current" claims, > next steps and permissions below belong to this recorded boundary. See > [current state](../../CURRENT_PLATFORM_STATE.md) for the latest physically observed result.Canonical issue: https://github.com/SchulzCode/Y2Linux/issues/7
Depends on Y2E-125 (#6). Resolve U07a with offline FM-kernel/preloader/LK analysis and retained safe stock evidence. Ownership: research and architecture; no implementation handoff until the policy is fixed.
Acceptance criteria:
- Remap FM kernel reservation logic independently of old symbol offsets.
- Record preloader/LK RAM-bank construction, display, modem/connectivity and identifiable loader/secure/shared-memory exclusions, distinguishing static facts from actual runtime observations.
- Assess DMA risks at entry and choose a deliberately bounded initial memory map.
- Specify exact permitted kernel/decompression, appended-DTB and initramfs intervals, byte budgets and offline validation formulas; do not invent the actual size of an unbuilt kernel.
- Choose static DT memory or ATAG import and document all memory/initrd/command-line implications.
- Update authoritative knowledge and state whether offline implementation may begin. Keep this issue open if the memory policy remains architecturally unresolved.
No Linux build, DTS/kernel implementation, BOOTIMG creation/modification, flashing, device writes or delegated research. Recovery and launch gates remain separate from offline artifact-design readiness.
Result: offline memory policy complete under D08; see initial-ram-map. U07c remains an explicit inherited-DMA/secure-state launch gate. No Linux artifact or implementation issue created; M0 not passed.