How to work here

How the Platform composes. The unit of composition is the Schematic — an app's authored declaration of which primitives it names. A recipe stitches Schematics into a coherent composition: the parts named, the joints declared, the whole proven constructible before anyone claims it runs.

The ladder

Each app climbs a ladder of rungs; a rung means a primitive is named in the app's Schematic, not that the app runs. Gaps are declared, not hidden — the catalog shows both. Read the catalog for the live numbers.

The conventions

• Manifest-first. Catalog, counts, and drops are folds — author the frame, derive the content.
• Name-agnostic. The layer names are pulled from one field; a rename is a one-field change.
• Honest texture. A specimen stays labeled a specimen. Nothing here implies a shipped app it isn't.

Worked example

Pick an app from the catalog, read its rungs and its declared gaps, then read Reference for the seam conventions. That's the loop: read the Schematic, compose the recipe, ship.