PolymerOS docs

Understand

Catalog Proof Quickstart

source=docs/public/catalog-quickstart.md sha256=ded119fb996456a4

The catalog runtime smoke is the replayable development proof for one Monomer. It uses one flow rather than a documentation-only simulation.

From a checkout that contains the catalog runtime lane, run:

scripts/run-catalog-runtime-smoke.sh

The script builds a small x86_64 payload, creates a local catalog entry, and runs the bounded QEMU proof. It does not publish an artifact, sign a release, open network access, or grant provider authority.

What The Proof Does

  1. Acquires the catalog payload into a content-addressed local store.
  2. Checks the catalog's declared SHA-256 digest before launch.
  3. Starts the Monomer and waits for its identity and ready markers.
  4. Observes the lifecycle status as starting, running, stopping, and stopped.
  5. Starts the same verified payload a second time and stops it cleanly.
  6. Corrupts a copy, refuses it before launch, and confirms that no partial store entry remains.

The successful log includes these milestones:

POLYMER_CATALOG_ACQUIRED=1
POLYMER_CATALOG_DIGEST_VERIFIED=1
POLYMER_CATALOG_GUEST_READY=1
POLYMER_CATALOG_PROVIDER_OBSERVED=1
POLYMER_CATALOG_CLEAN_STOP=1
POLYMER_CATALOG_RELAUNCH_COMPLETE=1
POLYMER_CATALOG_CORRUPT_REFUSED=1
POLYMER_CATALOG_PARTIAL_STORE_CLEAN=1
POLYMER_CATALOG_RUNTIME_PROOF_COMPLETE=1

POLYMER_CATALOG_PROVIDER_OBSERVED=1 means this observation-only smoke read the provider/status vocabulary; it still records authority as not-requested. The separate provider-control proof uses the same verified payload and shared status feed to approve, launch, stop, and relaunch it. Those development-scoped requests do not grant publication, native boot, general network access, or authority over any catalog entry whose policy is not approved.

For the naming used by the proof, read Micromer and Monomer and runtime tiers.