Policy

Developer and company-account policy

How an app gets onto the store.

Company accounts

A company account is a record in the estate's tenant registry with a stable id, a display name, and the list of product slugs it owns. The store's catalog/publishers.json mirrors that record. Only the estate operator creates company accounts.

Submitting an app

The app lives in a company repository under apps/mobile, apps/desktop, or assets/websites with a project.json.
The artifact is built by the repository's build tooling (compile.py / the forge builders), which writes a provenance manifest beside it.
The artifact is published to a reviewed download surface (the product's own site or the downloads site) and its digest recorded.
The catalog entry is added to catalog/apps.json with slug, version, platforms, status, artifacts (url, digest, signing status), and the company account as publisher; the store pages are regenerated and the site tests run.
Review records the outcome; the listing goes live with the next site release.

Signing

State the signing status honestly. Release keys are held by the company account; debug keys produce beta listings only.