# The Portable Definition Layer // the durable object, separable from the tool that holds it A method primitive: **the durable normative object a system must preserve across a substrate change** — the structured statement of *intent, constraints, discretion, references, and governance* that makes outputs (or interpretations) **recoverable, auditable, and accountable** independent of whatever generator, tool of record, or workflow happened to hold them. ```text intent · constraints · discretion · references · governance → the portable definition layer (the durable object) → survives a generator / tool-of-record / workflow swap → the output or interpretation stays recoverable · auditable · accountable ``` It is not a renderer, a substrate, or an execution. It is the durable object those three replaceable things are *about*. --- ## Classification **Accepted as method doctrine (a distinct method primitive), 2026-06-14.** Routed from `asset-pipeline-ASK` as a candidate (2026-06-13); classified here per [`docs/absorption-discipline.md`](absorption-discipline.md); ASK-approved as **option 1** (a distinct primitive, not a facet or umbrella) once the interpretive second instance was confirmed. It clears the §Evidence thresholds as a **two-instance bracket across structurally different kinds of system**: - **[`asset-pipeline-ASK`](https://github.com/apexSolarKiss/asset-pipeline-ASK) (generative, implemented)** — the proven worked instance (milestone-14 portability frontier: recovery / auditability / consumability). - **[`urban-observatory`](https://github.com/apexSolarKiss/urban-observatory) (interpretive, non-generative — conceptual)** — independent-domain confirmation on the durability axis; the five facets map while it explicitly does *not* carry generative mechanics. The second instance is what disambiguates: a non-generative domain confirming the same durable-structure pattern is direct evidence the primitive concerns **durable normative structure across substrates, separable from generation** — not a feature of any one generator or domain. ## Distinct from bounded generativity — a different axis [`method-ASK`](../README.md) already holds the **bounded generativity** primitive ([`docs/bounded-generativity.md`](bounded-generativity.md)). The portable definition layer is **orthogonal**, not nested: ```text bounded generativity — PROCESS axis grammar → bounded variance → selection → governed artifact (how a governed artifact is generated) portable definition layer — DURABILITY axis intent / constraints / discretion / references / governance (which normative structure is the durable object, and whether it survives being lifted out of the tool that held it) ``` They are complementary peers. The portable definition layer is **not a facet** of bounded generativity — an interpretive, non-generative system instantiates it with no generation at all. It is **not an umbrella** over bounded generativity — generation is not a special case of durability; it is a different axis. A system may exhibit one, the other, or both. ## The five facets The durable object is the structured statement of: - **Intent** — what the work is for (the source of intent a substrate change must not lose). - **Constraints** — the anti-goals and boundaries the work is held within. - **Discretion** — judgment exercised *within* standards. *Generative* discretion (which realized candidate is truest) and *evidentiary* discretion (how strong the evidence must be before a claim is licensed) are both instances. The durable statement holds discretion's conditions (what may vary, under which standard, who may decide, and how the decision closes) and the record of decisions made under them. The exercise itself is an act performed in each application ([`bounded-generativity.md`](bounded-generativity.md#where-discretion-enters)), not content the layer preserves. - **References** — the sources the work is accountable to — first-class accountability anchors (source + provenance + basis + applicability), not decoration. - **Governance** — what becomes a durable record, who may say so, and what recourse exists when it is wrong. **Applicability is relational, not a sixth facet.** It binds a claim or reference to the object, project, scale, or decision context it may describe or govern. Authentic source, correct provenance, and adequate basis do not by themselves establish that the material is attached to the right object. Where one context substrate spans several objects, the portable definition layer must preserve that relation; its carrier and enforcement mechanism are implementation-specific. This primitive is not a multi-object scope protocol. **Precedence ≠ applicability.** Precedence may resolve competing claims after their applicability has been established; it cannot establish which object, project, scale, or decision context a claim belongs to. These are what must survive a tool swap intact. The renderer, the base model, the pipeline, the interpretive surface are all replaceable; the definition layer is the object they are *about*. ## Worked instances (one implemented, one conceptual — across system kinds) These are **ASK-system worked examples and antecedent studies, not dependencies** — cite them as worked examples, never as imports. - **[`asset-pipeline-ASK`](https://github.com/apexSolarKiss/asset-pipeline-ASK)** — *generative, implemented.* One complete governed creative decision (brief → accepted asset) proven **recoverable** outside its tool (re-expressed as tool-agnostic structured data, reconstructed by a fresh reader), **auditable** without carrying the pixels (content hash for identity + durable pointer for access, inspection on demand), and worth holding even absent a downstream consumer (a receipt is valuable because it can be held, checked, and trusted). The durable object was the definition layer, not the generator, the base, or the pipeline. (Milestone-14 portability frontier + the byte-boundary and consuming-artifact findings.) - **[`urban-observatory`](https://github.com/apexSolarKiss/urban-observatory)** — *interpretive, non-generative, conceptual.* Reconstructs public-record evidence (`Assumption → ImplementationSignal → ImplementationFinding → InterventionCandidate`), provenance-first, with **gated interpretation** as its bounded-discretion analog and a **reviewer-role boundary** as governance. All five facets map; **auditability by construction** — public-data-only + provenance-first makes the interpretation natively inspectable against the public record. UO confirms the durability axis **only**, and has **not built or adopted** a liftable portability layer. ## Evidence posture (read this before citing the primitive) ```text asset-pipeline-ASK — proven generative worked instance (implemented) urban-observatory — confirmed interpretive instance (conceptual; durability axis only) UO has NOT built or adopted liftable portability infrastructure ``` This doc lands the **method primitive, not an implementation protocol.** It names the durable object a system must preserve across tools; it does **not** assert a built second instance, a schema, a workflow requirement, or an automation claim. The interpretive confirmation is conceptual; promotion of a *primitive* (a structural concept) turns on cross-domain conceptual confirmation, which is met — implementation enforcement is a separate, later question. ## Tiering (where the primitive and its relations live) - **[`method-ASK`](../README.md)** owns the primitive definition — this doc. - **Project repos** reference the primitive at high-level doctrine altitude — **not** as schema, proof-test, or implementation requirement. AP is the antecedent worked instance; UO holds a scratch analog it has not adopted. - A cross-repo *relationship* record, if/when warranted, belongs in [`control-surface`](https://github.com/apexSolarKiss/control-surface), not here. ## Boundaries - **Method-level, not project-specific.** AP is one implemented instance; UO is a conceptual second on the durability axis. Both cited as instances, **not dependencies or imports**. - **This defines the primitive; it authorizes nothing operational.** No schema, no project migration, no client doctrine, no implementation, no downstream repo mutation. No UO adoption claim; no "built second instance" claim. - **Auditability and accountability ≠ verification discipline.** Auditability and accountability are properties the durable object must preserve. The execution-time instruments, checks, and review procedures that test whether those properties are satisfied are not themselves facets or instances of the Portable Definition Layer; they belong to the verification discipline. A verification system may enforce or evaluate a portable definition layer without becoming the durable object it tests. - **It does not import bounded generativity's mechanics.** The durability axis is separable from generation; an interpretive instance carries no candidate-generation, creative-selection, or variance management. - **Source of intent, in the worked instances documented here, remains human/institutional.** What the definition layer *means*, and what counts as a governed artifact-or-interpretation worth preserving, is supplied or authorized by the operator or governing institution — not produced merely by the tool that carries or executes it. ## Anchors - Public articulation: [*The Missing Layer Is Not Generation*](https://atomicspacekitten.substack.com/p/the-missing-layer-is-not-generation) (asset-pipeline-ASK domain, 2026-06-13) — the outward translation; companion to [*Creative Discretion Is Not Creative Intent*](https://atomicspacekitten.substack.com/p/creative-discretion-is-not-creative). The article translates the finding outward; the repo/finding chain (AP milestone-14) is the source of truth. - Sibling primitive: [`docs/bounded-generativity.md`](bounded-generativity.md) — the **process** axis this is positioned against. - Inbound routing record: `2026-06-13_asset-pipeline-ASK_to_method-ASK_portable-definition-layer-candidate-primitive.md` — retained in the ecology operator surface's intent inbox; resolve its current physical path through `ecology-ASK-EXTERNAL/_INDEX-ecology-ASK.md` (ingested 2026-06-13). - Interpretive second-instance confirmation: `2026-06-13_urban-observatory_to_method-ASK_portable-definition-layer-interpretive-instance-feedback.md` — retained in the ecology operator surface's intent inbox; resolve its current physical path through `ecology-ASK-EXTERNAL/_INDEX-ecology-ASK.md` (ingested 2026-06-13).