In++ 2.3

Glossary

Core Terms

Term	Definition
Intenture	The name of the language; a formal semantic linguo-graphical language for intent explication for precise human-AI interaction
intenture	The phenomenon of intent - the inner pre-realized shape of creation: an integral unity of Intent, Conception, Vision, and Will to Embodiment
Explication	The process of revealing, clarifying, and structurally unfolding the implicit content of intent, translating a hidden or partially expressed inner structure into an explicit, distinguishable, and structured form. Explication is what Vergil performs in dialogue with the human.
Reverse Explication	The process of recovering intenture from an existing implementation. The reverse path: from realization to intent.
Explication Record	A versioned artifact produced by explication - a fixed result of the Explication process that can be stored, compared, and versioned
Explication of intenture	Revealing, clarifying, and structurally unfolding intent into a form suitable for precise AI interpretation and subsequent realization
Assumption Gate	A mandatory control gate in the AI Interpretation Protocol that prohibits an intenture from transitioning to Realizable when unconfirmed AI assumptions exist. Vergil must pass each assumption through explicit confirmation, acceptance, or rejection by the human.
Accepted Assumption	A Canvas block status meaning the AI made an assumption and the human reviewed and explicitly accepted it as a valid basis for further work. Differs from Answered in that it records a conscious acceptance of risk, not a confirmation of fact.

Explication vs Explication Record: Explication is the process, Explication Record is its result-artifact. Vergil performs Explication, the result is fixed as an Explication Record, and the Record is versioned and stored in Linked Artifacts. Explication vs Reverse Explication: Explication goes from human to structure (human speaks, Vergil structures). Reverse Explication goes from implementation to structure (Vergil analyzes existing artifacts and recovers intent).

Level Distinctions

Term	Definition
Idea	A local fragment of intenture, a particular thought content or thought impulse
Intent	Directional will and semantic vector determining what exactly the subject wants to achieve relative to an Object
Conception	The semantic genesis of a solution, image, or approach through which intenture begins to acquire internal form. Answers: "by what approach will the task be solved?"
Vision	A holistic image of the desired result, future state, or created reality. Answers: "what does the ideal end result look like?"
Will to Embodiment	The inner directedness toward embodying intenture in artifacts, actions, processes, services, products, or changes

Conception vs Vision: Conception describes the approach and method. Vision describes the image of the result. One intenture may have one Vision but several possible Conceptions for achieving it.

Language Objects

Term	Definition
Object	An entity upon which thought, design, or transformative work is performed
Actor	A participant influencing intenture or consuming its result
Artifact	A formal result arising during explication, modeling, or realization of intenture
Constraint	A boundary that must not be violated
Value	Benefit created for a specific Actor or system
Metric	An indicator by which the quality, success, or usefulness of intenture and its realization is evaluated
State	A condition of the intenture or derived Artifact in the lifecycle
Transition	A permitted movement between States
Signal	An event, deviation, impulse, or observation capable of influencing intenture, its interpretation, or its development
Evidence	Data, observations, facts, or justifications upon which intenture or its interpretation relies
Expected Output	The form in which the realization result must exist and in which AI is obligated to provide or prepare it
Intenture Portfolio	A collection of related intenture belonging to one person or team, represented as a typed graph. Each node is a full intenture with its own Canvas, Lifecycle, and Explication Record.
Intenture Portfolio Map	A visual diagram of Portfolio: nodes are intenture (showing name, Object type, and current Lifecycle State), edges are typed inter-intenture relations. Formed by Vergil in Exploratory Mode or Structuring Mode.
Knowledge Card	A typed, structured, versioned unit of knowledge that exists independently of any intenture and can be linked to one or more intenture via the `informed_by` relation. Has its own schema, lifecycle (Draft → Active → Stale → Archived), and versioning.
Knowledge Card Type	A category of Knowledge Card that determines its field schema. Types are extensible — each domain defines its own types.
Information Source	A typed marker for data provenance in Knowledge Cards and Evidence blocks: `[fact]`, `[hypothesis:human]`, `[hypothesis:ai]`, `[research]` (with source and date), `[to-collect]`, `[unknown]`. Extends base Evidence tags from v1.3.
Realization Artifact	A derived, typed artifact produced during and as a result of realizing an intenture (introduced in v2.0). It is an output of realization, not a one-time intent. Linked to one or more intenture via the 'realizes' relation, may be 'derived_from' upstream artifacts and 'supersedes' prior ones, and has its own lifecycle (Draft → Active → Stale → Superseded → Archived). Concrete types are domain-specific.
Realization Artifact Type	A category of Realization Artifact defined by the domain (extensible, paralleling Knowledge Card Type). Each domain registers its types in a namespace manifest with a namespace prefix - e.g. Inspark CVD defines 'inspark:SP', 'inspark:IRS', 'inspark:TB', 'inspark:PB'. The type determines the field schema; the core language does not enforce it.
Service Definition	A standing, reusable, versioned definition of a service or offering - the supply-side counterpart of a one-time Intenture. A core peer-class (alongside Intenture / Knowledge Card / Realization Artifact) introduced in v2.1. Borrows the Intenture 'core_definition' and adds a neutral 'service_profile'; instantiated per use via the version-pinned 'instantiated_by' relation.
Realization Strategy	The committed, full-depth plan for HOW a specific intenture is realized (Intenture Realization Strategy / IRS). A core peer-class introduced in v2.2, the second named stage of the Intent -> Realization chain. Abstract base: 'realizes'(intenture, version-pinned) + structured 'compass' + role-tagged sections + the Strategy/Operations/Hygiene discipline. Domains specialize via a 'strategy_type' profile (e.g. 'inspark:IRS').
Success Scorecard	The standing, compact, machine-readable contract for HOW success is measured (Inspark's Performance Brief / PB). A core peer-class introduced in v2.3, the third named stage of the Intent -> Realization chain. Abstract base: 'derived_from'(Realization Strategy, version-pinned) + 'objective' + 'measures' (each with a 'computation' for unambiguous automated tracking and a 'value_ref' to the intenture Value item) + 'data_access' (instrumentation and beneficiary obligations) + 'reporting' + the value-coverage discipline. Dual-form per §7.10: the AI-facing JSON is read by a tracking agent to compute metrics, report and update platforms; the human-facing rendering is the mutually-agreed measurement contract. Domains specialize via a 'scorecard_type' profile (e.g. 'inspark:PB').
Composition	The hierarchical parent-contains-children relation between intenture (a tree, parallel to the inter-intenture graph), carrying Constraint inheritance, Value aggregation, and Readiness roll-up (introduced in v1.8). A child qualifies as a sub-intenture only if it passes the Separability tests; otherwise it is a Canvas block of the parent.
Vergil	The Intenture Guide agent - the primary decision-maker for operational matters of intenture realization (lifecycle transitions, override approvals, complexity signaling). Escalates to a human only for substantive (product / value / result) decisions. Named after Virgil in Dante's Divine Comedy.
Compass	The structured core of a Realization Strategy (an OGSM hybrid): Objective (the Intent restated in outcome terms) + Strategies (each a differentiating choice with an explicit trade-off) + Goals x Measures. Universal across domains.
Strategy / Operations / Hygiene	A core discipline of the Realization Strategy. Strategy = a differentiating choice with a real trade-off that materially changes the outcome (belongs in the Compass). Operations = how we execute, which any competent executor would do (belongs in the operating plan / downstream artifacts). Hygiene = required by law / contract / standards, no choice involved.
Critical Readiness Threshold (CRT)	The gate an intenture must pass before it can transition to Realizable: its Core Definition blocks are Answered and the Assumption Gate is cleared. Realization begins only after the CRT.

Next:Meta-Model