29 lines
1.5 KiB
Markdown
29 lines
1.5 KiB
Markdown
# Phase 1.0AV: target-free launch-context canary contract
|
|
|
|
Status: `OFFLINE_CAUSAL_PAIR_CONTRACT_COMPLETE_NO_ARTIFACT_OR_AUTHORITY`
|
|
|
|
Date: 2026-07-29
|
|
|
|
AV defines the minimum causal comparison for the launch-context hypothesis.
|
|
Both arms must use the same exact future payload and `CHD10AV1` protocol. One
|
|
arm uses raw elfldr and the other a separately identified BigApp candidate.
|
|
Launcher hashes, run IDs and approval hashes must differ; neither approval can
|
|
carry to the other arm. Retry, reconnect, resume, installation and autoload are
|
|
forbidden.
|
|
|
|
Each supplied result must prove submit, then D04, then a distinct later cleanup
|
|
terminal. Missing or early terminal state makes the pair incomparable. Identity
|
|
drift, a retry, a persistent-write count or an unscoped visible-output claim is
|
|
a hard contract failure. Graphics operations have a separate closed approval
|
|
gate and are not conflated with persistent writes.
|
|
|
|
A changed submit return is classified only as a launch-context candidate. A
|
|
zero return is not interpreted as a visible flip, correct VideoOut semantics or
|
|
root cause. This module processes synthetic immutable values only. There is no
|
|
target source, artifact, address, transport, activation or device authority.
|
|
|
|
Before any implementation can be considered, a separate offline audit must
|
|
bind the exact source delta, post-D04 terminal, launcher effects and result-path
|
|
feasibility. BigApp termination requires its own explicit artifact-specific
|
|
approval and is currently false.
|