Creates another grouping domain under the instance. The kind matches the one selected in the header. Name is required.

The long-lived things this Org builds, ships and runs. Each holds its brief and roadmap, and its id is the one the rest of the suite uses. Creating one opens its kickoff. Projects name the products they change on their own tab.

not loaded yet

Stored on this Org -- the shared default every Project uses unless it registers its own (Project settings, once one is selected). Not encrypted at rest yet. Grok-Build signs in with SSO; the others take an API key.

A pack's signature is only honored if the key that signed it is trusted here. Trusting a signer authorizes everything they'll ever publish -- there's no per-pack revocation. Gated on Create at the instance.

Make this PinonPM the master of the suite's shared model: people, the org/product/component tree, and who may do what. Other suite services then follow it as replicas. This instance's root becomes the suite's root, under the id it already has, and every change to the tree or to bindings is written to the suite's log from then on. It cannot be undone from here. Gated on Create at the instance.

Once it is master, Suite admin lists the tree (retire and delete), pending changes and the audit.

Link a suite service to this PinonPM once, for the whole instance. You approve it in that service, signed in as one of its admins. It then holds an AI agent for this Core, with Admin over every org there, so onboarding can create orgs, products and people there under PinonPM's ids. The agent's token stays sealed here. Unlinking revokes it in the service. Gated on Create at the instance.

Paste a signed pack (the output of pinon-sign-pack sign). Reinstalling the same pack id replaces its rules/entry kinds rather than duplicating them. Same instance Create gate as trusted signers.

Creates a child of the selected Org. It then becomes the selected Project in the header. Name is required so the picker has something to show. Type is the same kind as this Org's existing children, or the pack's project-noun key when this Org has none.

Which packs apply to this Project. Base is always on. Everything else under this Project -- Teams types, board kinds, Consult roles, repos -- follows these checkboxes. Packs are installed on the Org; this only chooses which of them this Project uses.

The roadmap this Project works from lives on these products, and its seats reach them through this list. Naming a product takes write access to it.

not loaded yet

Teams under the selected Project. Type comes from enabled modules, not a free-text kind. Holders are work cards on the board, not folders here.

Who holds each access level on this Project. People this page has already seen, plus LLM providers registered on this Project or the Org (labeled by which). A Project's own registration takes precedence over the Org's. LLM options appear only on roles whose rules name a Project or child kind. Org-only seats (Owner) are assigned under Users.

Stored on this Project -- takes precedence over the Org's if both are set. Register one here when this Project bills its own key; leave it empty to keep using the Org's. Not encrypted at rest yet. Grok-Build signs in with SSO; the others take an API key.

One SSH identity for this Project. Add the public key on the forge, then add git URLs below. Optional image/script pin the Make env until .kiln/build.yaml ships. Builds is the suite component this remote builds: one under the Project's products, or a new one, which Depot and Deliver then have too. A repo that builds nothing (docs, infra) builds nothing. The leaf lane stays indexed.repo.

Creates a person who can sign in with email and password. No invite email is sent yet -- tell them the password out of band.

Who can administer this Org (Owner, and anything else the pack grants at this level). The access level is free text a pack's Rules give meaning to. An LLM cannot hold this seat.

Lighting for this browser. Saved on this device, not on the org.