Glossary

Current GitHub product terms

App link — Stable directory URL that follows a public repository’s default branch.

Version link — App URL pinned to a full Git commit and numeric repository ID.

Deploy — Authenticated public GitHub app registration; no Registry gas, Claim, or Companion signature.

Source review — A verified GitHub account’s explicit recommendation of one commit and Xcode recipe; not a safety verdict or build consent.

Menlo on iPhone — Private intent client for the one Mac factory, retaining the technical Companion bundle identity.

Installed commit — Selected source recorded as installed only after verification on the intended physical iPhone.

Private factory and historical protocol terms

The following terms retain their specific scope. A GitHub registration is not a Shot/Ship, and a GitHub source review is not a DeviceKey Release Attestation.

Accepted Version — An immutable expression state whose exact verification and required delivery gates passed.

Adopted project — An existing Xcode app connected through an external private project_<uuid> record without repository mutation.

Builder — The authority that controls public Shot actions through a BuilderAccount.

BuilderAccount — Deterministically addressed generation-0.8 smart account validating authorized P-256 actions and recovery.

BuilderID — Chain-scoped CAIP-like identifier eip155:4663:<BuilderAccount>.

Browser Draft — Private website input before encrypted handoff; never a Shot.

Catalog release — Companion-signed closed manifest binding one public checkpoint to exact source and build metadata.

Claim — One public, signed account-to-Shot encounter at an exact release/checkpoint.

Claim Edition — One immutable Open/Limited/Timed/Limited+Timed policy opened on first Ship.

Claim mark — Canonical 64-point gesture representation committed by SHA-256; expression, not a key or biometric identity.

Command — Stable idempotent private request admitted and journaled before semantic work.

Companion — Retained technical name for Menlo on iPhone and its private SDK; on the historical Registry path it also authorizes exact public actions.

Conformance — Fail-closed offline result where every applicable exact check passes.

DeviceKey — Authorized Builder P-256 key, normally non-exportable on Companion.

Evolution — Authorized transition from one exact Version to another.

EvolutionaryIntent — Exact desired change bound to an expression/base and optional signed Feedback commitments.

Expression — One stable manifestation of a Shot, such as its Apple app expression.

Fascia — Pinned reusable Apple capability/runtime substrate plus each Shot’s concrete manifest.

Feedback — Optional record bound to one exact Expression and Version; not a mandatory product step.

Following — Private exact-Builder preference reconciled between paired Mac and Companion.

Fork — New private child Shot rooted in one exact public parent release.

Genome — Accepted Shot-specific rules/state changed only by proposal and acceptance. Distinct from the historical static factory Genome.

Harness — Configured coding-agent adapter allowed one bounded implementation invocation and at most one targeted repair.

InstallationKey — App-installation-scoped P-256 continuity identity; never an Apple certificate.

Local Pending Intention — Imported private handoff waiting on the Mac; not yet a Shot.

Local Workspace Service — Loopback-only persistent Mac service owning admission, journals and reconciliation.

Organ — Immutable capability declaration within one Expression’s verified graph.

Pending Relay Intention — Encrypted transport record in handoff; not a Shot.

Public checkpoint — Ancestry-free privacy-safe Registry head projection with no source/private lineage.

Registry — Active ShotRegistry witness plus independently verifiable signed catalog and canonical indexes.

Release candidate — Signed/notarized immutable artifact explicitly exposed for acceptance, not stable promotion.

Shot — Stable random identity and coherent accepted history behind software.

Ship — The one first public release of a Shot.

Source-tree commitment — Domain-separated digest of one explicit normalized regular-file tree under the normative path law.

State Transition Receipt — Private per-execution report of preserved intent, route/usage and deterministic gate outcomes.

Update — In GitHub distribution, an explicitly selected newer source commit for local installation. In the historical Registry, any public release after a Shot’s one Ship.

Updates — Private high-signal inbox, distinct from a public shot.updated event.

Version — Exact immutable accepted state of one Expression; distinct from public checkpoint count and app marketing version.