# PythTIG Acceptance Status: Phase 7 acceptance record for the PythTIG version 1 cutover and cross-target line merged to `main`. The acceptance oracle is automated command output, QEMU serial output, and recorded package/evidence artifacts. A successful compile is not a successful boot. A screenshot-only physical run is not PythTIG acceptance evidence. ## Required Evidence Phase 7 acceptance requires all earlier PythTIG gates plus default-boot, recovery, reboot-restore, native-backend, cross-target, and physical-import tooling evidence: ```powershell cargo run -p pythc -- build programs/session-manager/main.pyth -o target/pyth-tig/session-manager.tig cargo run -p pyth-tig-tool -- verify target/pyth-tig/session-manager.tig cargo test -p pythc cargo test -p pythos-user-pyth-runtime cargo test -p pythos-shared --features pyth-tig-test-support cargo test -p pythos-core pyth_service_supervisor cargo build -p pythos-core --target x86_64-unknown-none cargo build -p pythos-core --target x86_64-unknown-none --no-default-features --features legacy-shell cargo build -p pythos-core --target x86_64-unknown-none --features pyth-tig-session-manager-fault-test cargo build -p pythos-user-shell --target x86_64-unknown-none python -m py_compile scripts/build-pyth-graph.py scripts/build-image.py scripts/build-iso.py scripts/test-pyth-default-boot.py scripts/pyth_cross_target.py scripts/test-pyth-cross-target.py scripts/prepare-pyth-physical-image.py scripts/verify-pyth-physical-log.py python scripts/build-pyth-graph.py python scripts/build-image.py --with-pythtig-default-services python scripts/test-pyth-tig-format.py python scripts/test-pyth-graph-runtime.py python scripts/test-pyth-graph-object-flow.py python scripts/test-pythc.py python scripts/test-pyth-native-codegen.py python scripts/test-pyth-default-boot.py python scripts/test-object-shell.py python scripts/test-boot.py --slice milestone-1 --timeout 60 python scripts/test-pyth-cross-target.py --unit-only python scripts/test-pyth-cross-target.py --automated-only python scripts/verify-pyth-physical-log.py --self-test python scripts/prepare-pyth-physical-image.py --manifest target/pyth-physical-image-manifest.json python scripts/verify-pyth-physical-log.py --manifest target/pyth-physical-image-manifest.json --log target/pyth-cross-target-ahci.log --backend ahci --target-id qemu-ahci-import-smoke --output target/pyth-physical-log-verification-ahci.json python -m unittest tests.test_ci_workflow cargo clippy -p pythos-core --target x86_64-unknown-none --features verify -- -D warnings cargo clippy -p pythos-core --target x86_64-unknown-none --features verify,sdhci-emmc-backend -- -D warnings cargo clippy -p pythos-boot --target x86_64-unknown-uefi -- -D warnings cargo fmt --all -- --check git diff --check ``` The long whole-workspace test remains a standing quality gate when practical: ```powershell cargo test --workspace ``` The broad `cargo clippy --workspace --all-targets -- -D warnings` command is not the accepted Phase 7 clippy gate for this no-std workspace layout. It attempts to clippy host-target user binaries and fails before lint analysis with the no-std panic/unwind configuration. Use the target-specific clippy commands above. ## Build Artifact Isolation The one-shot PythTIG QEMU harnesses must build the `pythtig-phase2-test` PythCore binary into the dedicated Cargo target directory `target/pythtig-phase2-core` and package that exact ELF with `scripts/build-image.py --kernel target/pythtig-phase2-core/x86_64-unknown-none/debug/pythcore`. This avoids a CI artifact collision where an earlier default-feature `pythos-core` build and a later no-default PythTIG test build both write through Cargo's shared final binary path `target/x86_64-unknown-none/debug/pythcore`. If the PythTIG one-shot image packages the wrong binary, QEMU can enter the normal boot path and fail before `PYTHOS:PYTHTIG:RUNTIME_TERMINATED`; observed failure signatures include `PYTHOS:CORE:NORMAL_INIT:BLOCK_DEVICE_READY` followed by `PYTHOS:PANIC`, or a normal boot timeout with no PythTIG runtime markers. Host-side coverage for this contract lives in: ```powershell python -m unittest tests.test_build_orchestration ``` The artifact-collision signature is fixed only when the one-shot runtime harness packages the isolated kernel and reaches `PYTHOS:PYTHTIG:RUNTIME_TERMINATED`. If a later object-flow run emits `PYTHOS:PYTHTIG:OBJECT_CREATED` and then exits with runtime status 1, treat that as a separate retained-object persistence investigation rather than evidence that the wrong kernel was packaged. The one-shot control sector is harness state. Failure to read it is fatal and is marked by `PYTHOS:PYTHTIG:CONTROL_READ_FAILED`; failure to clear an already read selector is nonfatal and is marked by `PYTHOS:PYTHTIG:CONTROL_CLEAR_FAILED`. A panic between `PYTHOS:CORE:NORMAL_INIT:BLOCK_DEVICE_READY` and `PYTHOS:CORE:NORMAL_INIT:SUBSTRATE_READY` with `PYTHOS:CORE:NORMAL_INIT:OBJECT_SERVICE_RESTORE_FAILED` belongs to retained object-service restore, not to PythTIG package verification. ## Required Markers Default normal boot must include, in order: ```text PYTHOS:CORE:NORMAL_BOOT:FAST_PATH PYTHOS:PYTHTIG:SERVICE_PACKAGE_ADMITTED service:session-manager package: principal:50595448534D0001 nodes: blocks: PYTHOS:PYTHTIG:SESSION_MANAGER_READY PYTHOS:PYTHTIG:SERVICE_PACKAGE_ADMITTED service:task-steward package: principal:5059544853540001 nodes: blocks: PYTHOS:PYTHTIG:TASK_STEWARD_READY PYTHOS:PYTHTIG:DEFAULT_SERVICES_READY PYTHOS:CORE:NORMAL_INIT:LAUNCHER_READY ``` `SERVICE_PACKAGE_ADMITTED` is emitted only after PythCore validates the named PythTIG graph manifest, shared package verifier result, expected service principal, and non-empty package shape. It is package-admission evidence, not a claim of independent daemon scheduling. The reboot restore path must prove an object-shell note revision and task state survive reboot under the default Pyth service composition. The recovery path must contain the service fault and enter the recovery shell: ```text PYTHOS:PYTHTIG:SERVICE_PACKAGE_ADMITTED service:session-manager package: principal:50595448534D0001 nodes: blocks: PYTHOS:CORE:CRASH:USER_FAULT PYTHOS:PYTHTIG:SERVICE_FAULT_CONTAINED service:session-manager PYTHOS:PYTHTIG:RECOVERY_SHELL_ENTER ``` Cross-target records must match package SHA-256, package runtime digest, normalized semantic markers, runtime entry, and runtime exit for every accepted backend claim. Physical logs must be verified through `scripts/verify-pyth-physical-log.py` against a manifest produced by `scripts/prepare-pyth-physical-image.py`. ## Phase Boundary When these commands pass and the final docs are committed, Phase 7 is complete. Stop at the Phase 7 boundary. Do not begin later PythTIG phases, hardware expansion, networking, package management, updates, AI, or SMP without explicit owner re-invocation.