Understand your environment identity.

The normative model keeps project, source, environment specification, materialization, delivery and runtime state separate.

Single-target first

The model must allow a project to have one target and no coordinator. A materialized environment is distinct from raw download cache. Strict preparation records where materialization happened and whether registry access or target-side installation is still required.

Core objects

Project identifies tenant scope and components. SourceRevision identifies immutable source state and native-file digests. EnvSpecRevision identifies native inputs, resource requirements, target constraints and resolution policy. Materialization records OS, architecture, ABI, resource digests, activation and host prerequisites. DeliveryBinding maps a materialization to a provider-specific handoff. WorkspaceSession and RunAttempt remain runtime concerns.

Identity rules

Do not flatten every native lock into one synthetic dependency graph. Do not treat a provider snapshot ID as the environment ID. Do not use a mutable branch name as the only source identity. Credentials never belong in reusable environment identity.