Meta-Model
25 Core Entities
intenture, Intent, Object, Conception, Vision, Will to Embodiment, Actor, Artifact, Constraint, Value, Metric, State, Transition, Signal, Evidence, Expected Output, Explication Record, Knowledge Card, Composition (v1.8), Vergil (v1.8), Realization Artifact (v2.0), Realization Artifact Type (v2.0), Service Definition (v2.1), Realization Strategy (v2.2), Success Scorecard (v2.3).
> New in v1.8: Composition is the hierarchical parent-contains-children relation with constraint inheritance and value aggregation. Vergil is the Intenture Guide agent, primary decision-maker for operational matters of intenture realization.
> New in v2.0: Realization Artifacts - derived artifacts produced during intenture realization (SP, IRS, Spec, Plan, Report are examples in the Inspark CVD; concrete types are domain-specific). Realization Artifact Type is the domain-defined category of a Realization Artifact, an extensible typing that parallels Knowledge Card Type.
> New in v2.1: Service Definition - a permanent, reusable, versioned definition of a service/offering (the supply-side counterpart of a single-use intenture). It reuses the intenture 'core_definition' plus a neutral 'service_profile' (provider, performers, measurement, SLA, cost, pricing - structure only; domain vocabulary is declared in the manifest, as with Realization Artifact Type). It is instantiated through the version-pinned 'instantiated_by' relation.
> New in v2.2: Realization Strategy (Intenture Realization Strategy / IRS) - the committed, full-depth plan for HOW a specific intenture is realized. The second named stage of the Intent -> Realization chain after Intenture. Abstract base: 'realizes' (version-pinned link to the intenture, formula 23) + a structured 'compass' (Objective + Strategies-with-trade-off + Goals x Measures) + role-tagged sections (compass, object_analysis, stakeholders, approach, metrics_forecast, resources_value, risks, operating_plan, domain) + the Strategy/Operations/Hygiene discipline. Domains specialize via a profile declaring a 'strategy_type' (e.g. 'inspark:IRS', 'game:IRS').
> New in v2.3: Success Scorecard - the standing, compact, machine-readable contract for HOW success is measured. The third named stage of the Intent -> Realization chain, after Realization Strategy. Abstract base: 'derived_from' (version-pinned link to the Realization Strategy, formula 24) + 'objective' + 'measures' (each with a 'computation' for unambiguous automated tracking and a 'value_ref' linking to the intenture Value item) + 'data_access' (instrumentation and beneficiary obligations: analytics, databases, ad accounts, APIs) + 'reporting' + the value-coverage discipline. Dual-form per §7.10: the AI-facing JSON is the source of truth a tracking agent uses to compute metrics, build reporting and update platforms; the human-facing rendering is the mutually-agreed measurement contract. Domains specialize via a profile declaring a 'scorecard_type' (e.g. 'inspark:PB').
Core Relations
expresses, explicates, acts_on, shapes, constrains, creates_value_for, informs, is_evidenced_by, is_measured_by, transitions_to, is_triggered_by, is_realized_as, is_performed_by, produces, targets, results_in, records, depends_on, enables, conflicts_with, shares_constraint_with, shares_actor_with, informed_by + Composition relations (contains, parent_of, inherits_constraint_from, allocates_from, contributes_to_value) (v1.8) + Realization relations (realizes, derived_from) (v2.0) + Service relations (instantiates, instantiated_by) (v2.1).
_(Realization Strategy reuses formula 23 'realizes': a Realization Strategy realizes an intenture. Success Scorecard reuses formula 24 'derived_from': a Success Scorecard is derived from a Realization Strategy.)_
26 Semantic Formulas
| # | Formula |
|---|---|
| 1 | Intent acts_on Object |
| 2 | intenture is_constrained_by Constraint |
| 3 | intenture creates_value_for Actor |
| 4 | intenture is_evidenced_by Evidence |
| 5 | Value is_measured_by Metric |
| 6 | Explication (process) produces Explication Record |
| 7 | Explication (process) is_performed_by Actor (Vergil) |
| 8 | intenture results_in Expected Output |
| 9 | Artifact creates_value_for Actor |
| 10 | Transition is_triggered_by Signal |
| 11 | Explication Record records intenture |
| 12 | intenture depends_on intenture (cascading dependency between intents) |
| 13 | intenture enables intenture (realization of one opens possibility for another) |
| 14 | intenture conflicts_with intenture (potential conflict between intents) |
| 15 | intenture shares_constraint_with intenture (shared constraints) |
| 16 | intenture shares_actor_with intenture (shared actors) |
| 17 | intenture informed_by Knowledge Card (intenture uses structured knowledge from card) |
| 18 | Knowledge Card informed_by Knowledge Card (one card references another) |
| 19 | intenture contains intenture (parent compositionally contains child; hierarchy, not graph) |
| 20 | Constraint inherits_into intenture (parent's Constraint inherits into child via fixed pattern) |
| 21 | Value contributes_to Value (child's Value item covers parent's Value item) |
| 22 | Vergil governs intenture (Vergil manages lifecycle transitions, override approvals, complexity signaling in operational scope) |
| 23 | Realization Artifact realizes intenture (derived artifact carries the realization of the intent; directed relation) |
| 24 | Realization Artifact derived_from Realization Artifact (one realization artifact derives from another; forms a realization chain) |
| 25 | Artifact instantiates Service Definition (a concrete consumer artifact is a version-pinned instance of the permanent service definition; v2.1) |
| 26 | Service Definition instantiated_by Artifact (reverse: soft pin while active, hard snapshot once finalized - the Explication Record pattern) |
Inter-intenture Relations (graph - V2)
Relations between separate intenture within an Intenture Portfolio. Each linked intenture is a full entity with its own Canvas and Lifecycle.
| Relation | Directionality | Semantics |
|---|---|---|
| depends_on | Directed (A depends_on B) | Realization of A is impossible or significantly hindered without realization of B |
| enables | Directed (A enables B) | Realization of A opens the possibility for realization of B |
| conflicts_with | Symmetric | A and B contain a potential conflict (in Constraints, resources, or goals) |
| shares_constraint_with | Symmetric | A and B share common Constraints (type specified: [budget], [timeline], [resource], etc.) |
| shares_actor_with | Symmetric | A and B share common Actors |
Rules:
Composition Relations (tree - V1, introduced in v1.8)
Composition Relations describe the hierarchical structure of intenture (a tree), parallel to the graph of Inter-intenture Relations. Hierarchy differs from graph: parent intenture contains children as its parts with constraint inheritance, value aggregation, and readiness roll-up.
| Relation | Directionality | Semantics |
|---|---|---|
| contains | Directed (P contains C) | C is part of P; P inherits C structurally; C inherits Constraints from P |
| parent_of | Reverse of contains (C parent_of P) | C declares its parent P |
| inherits_constraint_from | Derived (C inherits_constraint_from P) | Constraint Inheritance in one of 2 patterns |
| allocates_from | Derived (C allocates X from P) | Pool & Allocate: C gets allocated share of parent's resource |
| contributes_to_value | Directed (C value contributes_to P value) | Child's Value item covers parent's Value item |
Minimum Unit
The minimum unit of Intenture is a structured fragment of intent in which at least one entity + one semantically valid relation with another entity, context, or expected result is fixed.
However, the minimum unit of the language does not equal the readiness threshold for realization. Realization begins only after passing the Critical Readiness Threshold.