This commit is contained in:
@@ -0,0 +1,41 @@
|
||||
# Phase 1.0DD: minimal launcher source-prerequisite audit
|
||||
|
||||
Status: `LAUNCH_EXPORT_NAMES_PRESENT_ABI_AND_FW960_TITLE_CONTRACT_BLOCKED`
|
||||
|
||||
This is an offline read-only audit of the pinned public SDK and official shsrv
|
||||
v0.7 source. It creates no target source, launcher artifact, transport or
|
||||
device action.
|
||||
|
||||
The SDK stubs contain export names for foreground-user lookup, running-BigApp
|
||||
lookup and application launch. They do not contain C declarations, parameter
|
||||
semantics or the launch-context structure layout. All declarations used by
|
||||
the candidate—including `app_launch_ctx_t`—are local to the same shsrv v0.7
|
||||
source lineage. A symbol name is not an ABI, so this is insufficient evidence
|
||||
for new Chimera target code.
|
||||
|
||||
The v0.7 source hard-codes `PPSA01659` and labels it VideoPlayer/WebApp. That
|
||||
proves upstream intent only. It does not prove that the title exists, launches
|
||||
or supplies VideoOut ownership on firmware 9.60. No currently reviewed,
|
||||
nonmutating observer can establish that premise.
|
||||
|
||||
A bounded public search on 2026-07-30 targeted the exact function and
|
||||
structure names. It found a recent
|
||||
[`sonicloader`](https://git.earthonion.com/soniciso/sonicloader/commits/tag/1.0.48/sonic-loader.elf)
|
||||
candidate, but that project's
|
||||
own commit description says the context changes were ported from a supplied
|
||||
reference snippet. The same project includes persistent/autolaunch scope. It
|
||||
is therefore derivative evidence, not an independent ABI source, and is not a
|
||||
permitted Chimera dependency. The search found no qualifying independent
|
||||
header or firmware-9.60 title contract; this is a bounded result, not a claim
|
||||
of global absence.
|
||||
|
||||
AF–AU already model bounded ELF admission, mapping rollback, copy/credential
|
||||
restoration, worker supervision, result records and deadline-driven FD
|
||||
ownership. Those host models do not supply the missing ABI or firmware
|
||||
runtime evidence. DC therefore cannot yet bind a launcher hash.
|
||||
|
||||
Target implementation remains blocked until independent public source binds
|
||||
the three function signatures and launch-context layout, firmware-9.60 title
|
||||
presence can be established fail-closed, and one target composition proves
|
||||
absolute deadlines, restoration and the live result channel. Guessing the ABI,
|
||||
copying v0.7 declarations or invoking hbldr is explicitly excluded.
|
||||
Reference in New Issue
Block a user