Status: public-facing draft. This is not a release authorization, artifact publication, release-signing authorization, native boot authorization, or security assurance claim.
Evidence Principles
PolymerOS evidence is separated by lane:
- selected amd64 sandboxed build checks and separately tracked runtime checks;
- native Apple non-mutating artifact builds and separately review-gated runtime proof;
- QEMU-L1 live feature testing;
- Monomer service VM payload evidence;
- VM catalog and artifact-manifest publication gates.
Evidence from one lane does not automatically prove another lane.
Current Claim Boundaries
| Evidence category | Current public-safe claim | Non-claim |
|---|---|---|
| Sandboxed amd64 checks | Selected checks have passed under sandboxed build conditions, including integration, installer, and a KVM-backed Wayland check; KVM daemon-sandbox access is proven for the current boot, with persistent access policy still pending. | Not full release proof, compositor promotion, native graphics proof, or complete graphics/runtime proof. |
| Native Apple build work | A non-mutating live artifact build has passed read-only postbuild gates. | Not boot, install, EFI, USB write, signing, publication, or runtime authorization. |
| QEMU-L1 | Refreshed 16K live-test evidence shows nested KVM is available and Cloud Hypervisor starts; app VM root mounting remains the current runtime blocker after the live-image rebuild. | Not native Apple proof or current app VM root, vsock, virtio-fs, vhost-user networking, GPU, or Wayland proof. |
| Monomer runtime | Direct-boot runtime evidence exists for the first appliance payload, and a development-signed dm-verity rootfs candidate exists. | Not a reviewed catalog payload, reviewed public artifact URL, release-signing policy, or published VM artifact. |
| TamaGo Phase 1 | The ssh-agent micromer has local disposable-dev QEMU boot and attestation marker evidence. | Not production launch approval, catalog promotion, release signing, publication, USB Armory flash, or hardware-root validation. |
| VM catalog | Review contracts and placeholder packet shape exist. | No catalog payload is publication-ready. |
Release Gates
Publication requires:
- recorded build provenance;
- sandboxed build labels where applicable;
- strict VM artifact manifests;
- detached signatures and non-placeholder signing identity;
- dm-verity rootfs metadata for service VM payloads;
- native Apple runtime evidence only after explicit review authorization;
- catalog review that passes strict mode;
- human publication decision.
Source Of Truth
Internal review sources are intentionally not listed in public copy. Before any publication step, each row above must map to the internal claim map and either a reviewed evidence packet or a named future gate.
Public copy should cite reviewed evidence categories without exposing internal operational details.