Version. 0.1 Date. 2026-06-05 Status. Discovery note. Captures the reasoning from the seed v0.10 amendment session about how an engagement relates to the scopes above it. Input to C5 (the Domain layer) scoping; not a scoping note, not a CR. Records positive and negative paths so the trajectory is reconstructable. Audience. C5 scoping (the separate session that follows seed v0.10 landing); Operator.
While amending the seed to widen Memory to N-scope (v0.10), a worked example — a denim-jeans engagement drawing on a denim-heritage domain and a cotton-production domain — surfaced four design questions that the seed itself does not answer but that C5 must. This note records what was decided in principle and why, so C5 starts from settled reasoning rather than re-deriving it.
The four findings, in brief:
An engagement for the manufacture and marketing of a current denim jeans brand. It accumulates its own Memory — manufacturing detail, marketing, brand specifics. Above it sit two domains holding knowledge no single engagement owns: a denim domain (denim's history, including the Levi's origin story — anecdotal, narrative material) and a cotton domain (the cotton-growing economy, yarn and thread production).
A particular Shaping — say a brand story presenting the jeans and how they are made — reaches into both domains and composes relevant material from each alongside the engagement's own content. A different Shaping — a wholesale buyer's spec sheet — reaches the same domains but selects almost nothing anecdotal. Same Memory, same Manifestations, different reach, different selection.
This is the confirmed path: composition across scopes happens in Shaping, from several single-scope Manifestations. Manifestation never merges scopes. (Seed v0.10, confirmed by the Operator.)
The example exposed a false framing in the seed draft. The draft said an engagement "belongs to an organization, which may belong to a domain, and so on up the chain" — a single-parent chain. But the denim and cotton domains are not a chain over the engagement, and they are not above each other. Cotton is not denim's parent; they are peers.
The correction: there are two distinct relationships.
The denim-jeans engagement: membership → its brand organization (one). Reference → denim domain + cotton domain (several, orthogonal).
Why this matters for C5. A tree (single-parent) literally cannot represent "references denim AND cotton as peers." Reference must be a fan-out. But membership need not pay graph costs in the common case — it is a chain. The model is therefore two axes: a membership relationship (a chain, mostly) and a reference set (a typed fan-out). Collapsing them into one "fan-out" loses that membership is usually singular; collapsing them into one "tree" makes orthogonal references inexpressible.
Use cases tested (each demanded fan-out references; membership stayed a chain except the shared-subject case):
References are not uniform. At least three flavors, which Shaping must compose differently:
An untyped reference graph is the expensive case; a typed reference set is tractable, because each edge declares how it composes. C5's composition rules attach to the type.
The diamond hazard, and the rule that dissolves it. The Operator drew two routes to cotton:
Brand Jeans ──> Denim ──> Cotton (cotton reached via denim)
Brand Jeans ──────────────> Cotton (cotton reached directly)
This is the classic diamond. Its hazards: double-pull (same assertion composed twice), provenance ambiguity (why is cotton here — direct sourcing, or denim's mention?), and conflict-resolution ambiguity (which path's precedence applies to a cotton floor?).
The resolving rule: reference edges are non-transitive. A Shaping composes the engagement's own declared references. It does not automatically walk references-of-references. So:
Brand Jeans ──refs──> Cotton. Explicit, attributed to a direct brand decision.
Note the false arrow in the Operator's diagram: Denim ──> Cotton is not membership (denim does not belong to cotton). It is denim's own reference to cotton (denim knowledge invokes cotton). Once membership and reference are separated (Finding 1), the diamond is well-defined and safe.
Opt-in depth, never automatic. There is a real case where a Shaping wants denim's references as first-class (the heritage story wants deep cotton context, not just denim's mention). This must be an explicit Operator/Shaping choice — "also reach denim's references" — never an automatic transitive walk. Opt-in preserves operator-authority over what gets reached. Default reach depth is 1.
A scope's Memory is reachable in one of two modes:
Open-by-default, closed-by-exception. A scope is open until an ACL is established on it. Establishing an ACL is the deliberate, recorded act that restricts. This is the right posture for a knowledge commons (denim/cotton domains open so engagements compound) and it makes restriction an explicit decision, not a default someone forgot to change.
The OVA-stub period, stated honestly. Today OVA does not enforce, so every scope is effectively open. This is not the same as "all" being a placeholder. "All" is a permanent, first-class mode. The access mode is seam-declared now, so that when OVA enforces, scopes carrying an ACL become restricted and the rest stay open. The Operator was explicit: the model must support both restricted (ACL via OVA) and open ("all"); they are distinct commitments. Open is open by design.
Operator's phrasing of the rule: all by default; if OVA is present (an ACL exists on the scope), OVA is now in control.
The fan-out reference model creates a burden: someone has to know which domains exist and curate the engagement's reach set. That someone must not be the Operator studying a scope taxonomy — the seed's voice principle forbids requiring the Operator to understand technical structure.
The flow. As the Operator discusses the engagement with the Companion (manufacturing, marketing, the brand story), the Companion notices the subject touches denim and cotton and surfaces those domains: "There's a denim domain with heritage knowledge, and a cotton domain covering sourcing and production — want this engagement to draw on either?" The Operator says yes/no/which. The reach set is built from the Operator's intent, in plain conversation.
Why this fits. The manifest records Companion-as-Operator-system-interface as a settled principle (Phase 60): the Companion is the primary surface for Operator-system interaction, not just chat. Domain reach is exactly that. So the seed does not need to grow to permit this — the existing commitment already covers it. This is a direction for C5 / engagement-creation, recorded here, not seed text.
Three disciplines it must honor:
A quieter benefit. The Companion surfacing "denim domain (already used by N engagements)" is how domains get discovered and reused — the compounding thesis operating at engagement creation. The Companion becomes the matchmaker between an engagement and the existing body of domain knowledge. Strong product idea; downstream of getting the reach model right.
In seed v0.10 (because leaving it out invited the false-hierarchy reading):
Left to C5 scoping (specification-level; this note is the Discovery-record input):
This note records reasoning from the seed v0.10 amendment session (2026-06-05), Operator Marvin Percival. The worked denim/cotton example, the diamond diagram, the "all by default; if OVA present, OVA controls" access rule, and the Companion-surfacing-domains direction are the Operator's; the structuring into findings and the non-transitive-diamond rule are the session's synthesis. Seed v0.10 is the artifact this note accompanies.
DUNIN7 — Done In Seven LLC — Miami, Florida Loomworks — Discovery note: the domain reference model (C5 input) — v0.1 — 2026-06-05