§21 Substrate Profiles

A substrate profile is a pre-configured instance type optimized for a governance context — each provides a different observation perspective on the organizational world model. Three profiles exist: Enterprise Accountability Substrate (EAS), Business Accountability Substrate (BAS), and Project Accountability Substrate (PAS). The three profiles share the same nineteen primitives across five tiers (§4), the same ten behavioral invariants (§5), the same truth type system (§6), and the same state transformation model (§9). Profiles differ in authority model, temporality, governance subject, default activation levels, accountability model, and bootstrap pattern, allowing different stakeholders to query the same underlying organizational world model through tailored lenses.

Profiles are substrate-level concepts — not protocol-level. Any DLP implementer uses the same primitives and invariants. Profiles configure how those primitives activate and interact within a specific organizational context.

One structural relationship governs the three profiles: EAS = BAS + Governance. EAS is a superset of BAS, not a sibling. Every EAS instance contains all BAS content plus a governance layer. BAS is the operational base. PAS is bounded scope with delegated authority. BAS→EAS graduation is additive — the governance layer instantiates on top of existing BAS content.

Profiles partition the governance problem space by organizational complexity and temporality. EAS governs complex organizations with subordinate units and portfolio structure. BAS governs operating businesses with ongoing rhythm. PAS governs time-bounded projects with completion criteria. The same primitives, invariants, and mechanics operate across all profiles; activation intensity varies per profile.

§21.1 Profile Architecture

Table 21.1.1: Profile Comparison Matrix

Structural Containment

The EAS = BAS + Governance relationship is not a classification convenience — it is a structural containment. Every EAS instance contains the full BAS operational layer: the full BAS intent domain catalog, all BAS evidence types, all BAS account templates, all BAS commitment and authority templates, and the five-phase BAS activation sequence. The EAS governance layer adds a governance domain intent catalog, governance-specific evidence types, governance accounts, governance commitments, oversight and advisory authority types, board and executive role templates, and a governance lifecycle overlay.

This containment means BAS→EAS graduation is additive. When a business adds enterprise governance, the existing BAS content continues operating at the operational (COMMAND) level while the governance layer adds OVERSIGHT authority above and ADVISORY authority alongside.

Profile Selection at Genesis

Profile selection occurs at Genesis — the irreversible initialization that establishes the substrate's initial valid state (§18.2). Profile configures functional capability activation across the four-stage lifecycle (Configure → Operate → Plan → Learn). The lifecycle stages are universal across profiles; the activation intensity is profile-specific.

Profile selection is determined by organizational complexity, not hierarchy position. A node is EAS when it has subordinate units requiring their own governance, maintains its own methodology, operates its own governance framework, and manages a portfolio. A node is BAS when it has ongoing business rhythm without subordinate governance needs. A node is PAS when it has bounded scope and clear completion criteria.

§21.2 Content Package Architecture

Each profile ships with pre-built content that instantiates at Genesis. Content packages provide the initial governance structure from which the organization operates. The three packages reflect the containment relationship: EAS inherits all BAS content and adds a governance layer; PAS provides bounded project structure.

Table 21.2.1: EAS Content Package Structure

EAS Governance Domain Intents

EAS ships with a pre-built governance domain intent catalog covering enterprise governance categories. Specific domain naming and scope are deployment-configurable; reference deployments include a default catalog provided in the substrate's content package. The protocol commitment is that EAS instances carry pre-built governance domain intents above the BAS operational baseline.

Some governance domain intents enhance existing BAS domains rather than replacing them — e.g., a financial-stewardship intent may add board-level budget approval and audit requirements to BAS Money; a people-and-capability intent may add succession planning to BAS Hiring; an operations-and-delivery intent may add board-level performance reporting to BAS Managing. The BAS intent continues operating at COMMAND level while the EAS intent adds OVERSIGHT requirements.

BAS Content Scope

BAS ships with a pre-built intent domain catalog spanning the business lifecycle. Reference deployments organize domains into a strategic layer (founder readiness, problem and market validation, business model and strategy, financial planning, product and operations design, brand and market presence) and a structural layer (entity and legal structure, tax elections, ownership and governance, compliance, financial infrastructure, insurance, licenses, location, employment, intellectual property, contracts, fundraising). Specific domain naming, count, and partition are deployment-configurable.

BAS ships with evidence types across its intent domain catalog, account template categories, commitment templates, authority templates, and a five-phase activation sequence (Phase 0: Pre-Commitment through Phase 4: Scale Prep) with evidence-gated transitions between phases.

PAS Content Scope

PAS ships with a pre-built project type catalog covering common bounded-project categories — physical creation, investigation, transitional change, time-boxed effort, gateway evaluation, creative work, capability acquisition. Specific project type definitions, naming, and default durations are deployment-configurable.

PAS ships with evidence types (universal project evidence plus type-specific evidence per project type), required account templates (time budget, time spent, progress, scope), self-commitment and external commitment templates, and owner plus collaborator authority templates. PAS lifecycle consists of five phases: Definition, Planning, Execution, Completion, and Closure.

Table 21.2.2: Profile Content Summary

§21.3 Profile Governance Model

RACIVG as Profile Differentiator

The RACIVG accountability model (§22) provides the structural differentiator between enterprise and business governance. Six roles exist in the model:

• R (Responsible) — executes the work
• A (Accountable) — owns the outcome and accepts closure
• C (Consulted) — must concur before decision or closure
• I (Informed) — notified after decision or closure
• V (Verifies) — verifies required evidence and quality; holds blocking power
• G (Governs) — owns binding constraints and policy surfaces; authorizes enforcement and exceptions

EAS activates the full six-role RACIVG model. BAS activates RACI only — four roles. PAS uses a simplified model with OWNER and COLLABORATOR roles. The V (Verifies) and G (Governs) roles are what distinguish enterprise governance from business operations. V provides independent evidence verification with hold power — it can block closure when evidence is missing. G provides policy and constraint authority — it owns the governance surfaces that bind all actors. Without V and G, outcome ownership (A) implicitly absorbs assurance and governance, which is adequate for founder-driven businesses but structurally insufficient when multiple stakeholders, boards, regulators, or external accountability requirements exist.

Table 21.3.1: Profile Governance Activation

Full RACIVG definition, Role Envelopes, dynamic context modifiers, and AI participation rules are specified in §22.

Table 21.3.2: Profile Defaults Matrix

Knowledge Governance per Profile

Knowledge governance activation (§18.3, §19) varies by profile, reinforcing the governance model differentiation.

EAS activates the full knowledge governance protocol: knowledge intake triage with all four intake categories (Mapped, Partial, Unmapped, Conflicting), the complete term promotion lifecycle (PROPOSED → UNDER_REVIEW → VERIFIED → ACTIVE), and all three knowledge governance roles (Domain Steward, Knowledge Verifier, Ontology Governor). Confidence thresholds operate at protocol defaults. The Ontology Governor role maps to the enterprise governance authority structure — typically the board or senior leadership holds this role.

BAS activates knowledge intake triage and term promotion with a simplified role structure. The business owner typically holds both Domain Steward and Ontology Governor functions. A separate Knowledge Verifier is required by protocol invariant. Confidence thresholds are adjustable within protocol bounds, allowing business-appropriate sensitivity without compromising structural integrity.

PAS inherits knowledge governance configuration from its parent instance. PAS does not independently configure knowledge governance roles or thresholds. Knowledge intake within a PAS instance routes to the parent's governance structure for triage and promotion decisions.

§21.4 Profile Selection & Graduation

Table 21.4.1: Profile Selection Decision Matrix

Profile Graduation Mechanics

Graduation is a topology change in the instance portfolio, not a mutation of an existing instance. Graduation creates a new instance with the target profile. Evidence carries forward with full lineage preserved. The source instance completes or archives with a graduation reference linking to the new instance. Every graduation transition produces a Decision primitive with lineage — the graduation decision itself is a governed state transformation.

PAS → BAS Graduation

PAS → BAS graduation occurs when a bounded project becomes an ongoing business. The authority model shifts from delegated to inherent. The governance scope shifts from project completion criteria to business sustainability.

PAS → BAS graduation has a gateway pattern: a bounded project type may serve as the formal entry to business creation, with a GO/NO-GO decision producing evidence that transfers to the new BAS instance at its initial phase. Specific gateway evidence requirements are deployment-configurable.

On GO: evidence, decisions, and lineage transfer directly to the new BAS instance at Phase 1 (Foundation), preserving full provenance.

On NO-GO: the project completes normally. Evidence is preserved with full lineage for potential future reactivation. No business instance is created.

Universal graduation triggers. All PAS project types include graduation triggers — signals that a project may be becoming a business:

• Revenue generated
• Recurring customers or demand
• Outside investment interest
• Employment created
• Indefinite commitment emerging (bounded → unbounded drift)

Type-specific triggers supplement universal triggers: Building projects trigger on licensing interest or manufacturing requests. Research projects trigger on commercialization interest or methodology requests. Creative projects trigger on distribution deals or audience monetization.

Configurable sensitivity. Graduation trigger sensitivity is configurable per instance:

Triggers are advisory signals, not automatic transitions. The substrate prompts; the human decides. The graduation decision is a full Decision primitive with lineage.

BAS → EAS Graduation

BAS → EAS graduation occurs when a business adds enterprise governance. The accountability model expands from RACI to full RACIVG. The governance framework activation expands to the full governance stack. The content package gains the governance layer — a governance domain intent catalog, governance-specific evidence types, governance accounts, governance commitments, and oversight and advisory authority types.

Graduation triggers:

• Board addition or formal advisory body establishment
• Outside capital with governance requirements (investors requiring board seats, reporting obligations, or audit rights)
• Regulatory mandate requiring formal governance structures
• Founder control exceeded — organizational complexity surpasses what a single decision-maker can govern
• Multiple concurrent sub-projects requiring coordination beyond parent methodology
• Specialized methodology needs beyond parent standard approach
• Resource allocation complexity requiring portfolio management

BAS → EAS graduation creates a new EAS instance. All BAS primitives carry forward. Existing BAS authorities reclassify as COMMAND type. New OVERSIGHT authority (board-level) instantiates above. New ADVISORY authority instantiates alongside. The governance lifecycle overlay (Formation → Establishment → Operations → Maturity) begins at Formation, operating in parallel with the existing BAS operational phases.

§21.5 SDK Constraints Summary

Table 21.5.1: §21 SDK Constraints

Scope

Scope limited to logical model specification. Transport protocol, serialization format, and implementation languages are DESIGN SPACE.

Implementation Requirements

All SDK constraints listed in §21.5 are binding implementation requirements for DLP substrate builders.