25 lines
1.1 KiB
Markdown
25 lines
1.1 KiB
Markdown
# Phase 1.0AD: inactive activation contract
|
|
|
|
Status: `INACTIVE_NUMERIC_TARGET_CONTRACT_COMPLETE_NO_LIVE_CAPABILITY`
|
|
|
|
Date: 2026-07-29
|
|
|
|
This phase closes the data boundary left by Phase 1.0AC. It does not add a
|
|
network adapter, target source, launcher, socket, DNS lookup, clock, CLI or
|
|
device action.
|
|
|
|
The tracked activation is entirely inactive and target-free. The host-only
|
|
contract can validate hypothetical future records, but validation neither
|
|
activates nor persists them. A candidate must use canonical private IPv4 text,
|
|
source-bound port 2323, a unique run ID, a window of at most five minutes and
|
|
separate SHA-256 identities for launcher, payload and untracked approval.
|
|
|
|
Retry, reconnect, resume, device writes, app termination and system remounts
|
|
are rejected. The contract deliberately cannot express authorization for
|
|
those effects.
|
|
|
|
The next useful phase is a separate offline architecture review of a minimal
|
|
BigApp launcher derived from official GPLv3 shsrv source. That review must
|
|
remove the general shell, persistent fake-app creation, remount behavior,
|
|
unbounded waits and arbitrary payload selection before target code is allowed.
|