@agenticprimitives/ontology 1.0.0-alpha.18 → 1.0.0-alpha.19

package/tbox/intents.ttl

@@ -92,6 +92,16 @@ apint:AssignRoleIntent a owl:Class ;
     rdfs:subClassOf apint:RelationshipIntent ;
     rdfs:label "AssignRoleIntent" .
 
+# ─── Consultation (spec 329 — org assistant member routing) ──────────
+# Layer-2 spine artifact ONLY: a ConsultationIntent DESCRIBES a routed org→member
+# consult; it is EXECUTED by the ADR-0044 Ring-0 loop over the A2A task rail —
+# never by the W1 marketplace resolver (the spine describes; the loop executes).
+
+apint:ConsultationIntent a owl:Class ;
+    rdfs:subClassOf apint:Intent ;
+    rdfs:label "ConsultationIntent" ;
+    rdfs:comment "An org's signed request that a specific member agent answer a discussion question. Layer-2 spine artifact; executed via the A2A task rail (spec 329), never the marketplace resolver. direction 'receive'; object = the consult-answer IRI; expressedBy the org SA; addressedTo exactly one member SA. Wire binding: `ap.consultation-intent.v1` ↔ this class (TS mirror: fabric ConsultationIntentV1)." .
+
 apint:MatchInitiation a owl:Class ;
     rdfs:subClassOf prov:Activity ;
     rdfs:label "MatchInitiation" ;

package/tbox/messaging.ttl

@@ -143,6 +143,22 @@ apmsg:invitationStatus a owl:DatatypeProperty ;
     rdfs:label "invitationStatus" ;
     rdfs:comment "Concept from apmsg:discussionInvitationStatusScheme: invited | accepted | declined | revoked." .
 
+# ─── Org-assistant participation + acting-agent provenance (spec 327; 318 §8.1) ──
+# The org's OWN agent posting in its topics is the Organization SA being agentic — the principal
+# itself (318 §8.1/§8.8), never a Service participant and never a "bot account". Participant bots
+# (distinct Service SAs, admission delegations — 318 §8.2–8.8 / C4) get their OWN classes at the
+# fabric cutover; these two terms are deliberately narrower and compose with them.
+
+apmsg:actingAgent a owl:ObjectProperty ;
+    rdfs:domain apmsg:MessageEnvelope ; rdfs:range ap:Agent ;
+    rdfs:label "actingAgent" ;
+    rdfs:comment "spec 324 §9 acting-agent provenance on a board entry: WHO performed the authoring move when it was not a human session — for org-assistant posts, the org SA itself. Absent ⇒ human-session authored. Never erased (prov: alignment: the acting move is attributable, not anonymous). Mirrors fabric ExchangeRecordV1.actor, which absorbs it at the 316 cutover." .
+
+apmsg:topicAssistantPolicy a owl:ObjectProperty ;
+    rdfs:domain apmsg:DiscussionTopic ; rdfs:range skos:Concept ;
+    rdfs:label "topicAssistantPolicy" ;
+    rdfs:comment "Presence ⇔ the org's own agent participates in this DiscussionTopic (steward-enabled, spec 327). apmsg:assistantOnMention (reply only to @-mentions of the org) | apmsg:assistantOnAllPosts (reply to every member post). Orthogonal to participationPolicy — enablement is a steward act on the topic, never a participation assertion." .
+
 apmsg:inConversation a owl:ObjectProperty ;
     rdfs:domain apmsg:Discussion ; rdfs:range apmsg:Conversation ;
     rdfs:label "inConversation" .
@@ -157,6 +173,39 @@ apmsg:ConversationProfile a owl:Class ;
     rdfs:label "ConversationProfile" ;
     rdfs:comment "direct | group | discussion | broadcast | forum | announcement | support." .
 
+# ─── Routed consultation (spec 329 — org assistant member routing) ────
+# ARTIFACTS only, per this file's rule: the ConsultAnswer (a member agent's durable, structured
+# answer) gets a class; pending-routing rings and candidate rankings are PROJECTIONS and get NONE.
+# The routing decision itself is described by apint:ConsultationIntent (tbox/intents.ttl); the
+# synthesized reply's provenance reuses PROV-O directly (prov:wasDerivedFrom each contributing
+# ConsultAnswer, prov:wasAttributedTo) — no parallel terms are minted (house rule).
+# Wire binding: `ap.consult-answer.v1` ↔ apmsg:ConsultAnswer (TS mirror: fabric ConsultAnswerV1).
+
+apmsg:ConsultAnswer a owl:Class ;
+    rdfs:subClassOf prov:Entity ;
+    rdfs:label "ConsultAnswer" ;
+    rdfs:comment "A member agent's structured answer Artifact to a ConsultationIntent (spec 329 §3.2). Durable artifact in the org's vault; agent-authored (apmsg:actor = member SA). Carries exactly one of an answer or an explicit decline (SHACL: answered xor declined)." .
+
+apmsg:consultedAgent a owl:ObjectProperty ;
+    rdfs:domain apmsg:MessageEnvelope ; rdfs:range ap:Agent ;
+    rdfs:label "consultedAgent" ;
+    rdfs:comment "Synthesized-reply attribution: an agent consulted for this reply (PROV-aligned; pairs with prov:wasDerivedFrom pointing at the contributing apmsg:ConsultAnswer records). Attribution only — never authority." .
+
+apmsg:answerText a owl:DatatypeProperty ;
+    rdfs:domain apmsg:ConsultAnswer ; rdfs:range xsd:string ;
+    rdfs:label "answerText" ;
+    rdfs:comment "The member agent's answer text. Present iff the consult was ANSWERED (xor apmsg:declined — ConsultAnswerShape). The artifact body's integrity hash reuses apful:bodyHash (the answer rides the a2a task Artifact)." .
+
+apmsg:declined a owl:DatatypeProperty ;
+    rdfs:domain apmsg:ConsultAnswer ; rdfs:range xsd:boolean ;
+    rdfs:label "declined" ;
+    rdfs:comment "True iff the member's agent explicitly declined to answer (spec 329 §3.2 — the playbook's decline path). Present (true) xor apmsg:answerText; an optional free-text reason rides apmsg:declineReason." .
+
+apmsg:declineReason a owl:DatatypeProperty ;
+    rdfs:domain apmsg:ConsultAnswer ; rdfs:range xsd:string ;
+    rdfs:label "declineReason" ;
+    rdfs:comment "Optional member-agent-supplied reason accompanying a decline." .
+
 # ─── Classes + predicates (aporg extension: the membership listing) ──
 
 aporg:DirectoryListing a owl:Class ;
@@ -188,3 +237,8 @@ aporg:listingHash a owl:DatatypeProperty ;
     rdfs:domain aporg:DirectoryListing ; rdfs:range xsd:string ;
     rdfs:label "listingHash" ;
     rdfs:comment "sha256 of the canonical listing — the commitment an OPT-IN on-chain anchor attests to (apatt:credentialHash ≡ this; anchor requires the ADR-0025 amendment, spec 322 §6)." .
+
+aporg:consultable a owl:DatatypeProperty ;
+    rdfs:domain aporg:DirectoryListing ; rdfs:range xsd:boolean ;
+    rdfs:label "consultable" ;
+    rdfs:comment "Member-asserted, org-scoped routing HINT (spec 329 §2.2). The authority is the consultability delegation; this property only surfaces eligibility. Absent ⇒ false. Flag without delegation ⇒ not consultable (fail-closed); delegation without flag ⇒ not surfaced to routing." .

package/tbox/plan.ttl

@@ -0,0 +1,169 @@
+# T-box — P-Plan grounding (spec 332 §4; closes the outstanding spec-316 W5 `plan.ttl` item).
+#
+# ── Why ONE module for three plans ───────────────────────────────────────────────────────────────
+# The substrate has three plan-shaped objects, and confusing them is the recurring failure this
+# module exists to prevent (ADR-0054 §3):
+#
+#   apcoord:CoordinationPlan — DURABLE, SHARED, versioned. Multi-principal. Adopted by decision.
+#   apexec:ExecutionPlan     — RUN-SPECIFIC. One goal, one executor, one loop (spec 330 §8).
+#   service-agent PrimitivePlan — the deterministic compile target (spec 316 §6; runtime-owned,
+#                                 typed as p-plan:Plan in A-box emission, no T-box class here).
+#
+# All are p-plan:Plan. They are related ONLY through compilation provenance
+# (prov:wasDerivedFrom): a CoordinationPlan step COMPILES INTO run ExecutionPlans; it is never a
+# synonym for one. The run bridge is p-plan:correspondsToStep + the spec-330 §9 qualified
+# association — that pair is what makes a whole coordination process reconstructable: who
+# (prov:agent + prov:hadRole), did what (activities), on what (prov:used, by hash), producing what
+# (prov:generated), under WHICH plan step and revision (prov:hadPlan + correspondsToStep).
+#
+# A plan is never authority: activating, adopting, or corresponding to a plan grants nothing
+# (capability-architecture §2 axiom 6; ADR-0041). No gate reads a p-plan: term.
+
+@prefix p-plan:  <http://purl.org/net/p-plan#> .
+@prefix ep-plan: <https://w3id.org/ep-plan#> .
+@prefix apcoord: <https://agenticprimitives.dev/ns/coordination#> .
+@prefix apexec:  <https://agenticprimitives.dev/ns/execution#> .
+@prefix prov:    <http://www.w3.org/ns/prov#> .
+@prefix rdfs:    <http://www.w3.org/2000/01/rdf-schema#> .
+@prefix owl:     <http://www.w3.org/2002/07/owl#> .
+
+<https://agenticprimitives.dev/ns/plan> a owl:Ontology ;
+    rdfs:label "Agentic Primitives — P-Plan grounding" ;
+    owl:versionInfo "0.1.0" ;
+    rdfs:comment "Declares the imported P-Plan terms the substrate uses and grounds the plan-shaped objects (durable apcoord:CoordinationPlan, run-specific apexec:ExecutionPlan, service-agent PrimitivePlan) as p-plan:Plan. Spec 332 §4; spec 316 §6; spec 330 §9." .
+
+# ═══ Imported P-Plan terms (declared so shapes and A-box rows target something real) ═══
+
+p-plan:Plan a owl:Class ;
+    rdfs:subClassOf prov:Plan , prov:Entity ;
+    rdfs:label "Plan (P-Plan)" ;
+    rdfs:comment "A prescriptive description of intended activities. In this substrate every plan variant is a p-plan:Plan first." .
+
+p-plan:Step a owl:Class ;
+    rdfs:label "Step (P-Plan)" ;
+    rdfs:comment "One planned element of a p-plan:Plan. Prescriptive — an executed activity CORRESPONDS to a step; it never IS the step." .
+
+p-plan:Variable a owl:Class ;
+    rdfs:label "Variable (P-Plan)" ;
+    rdfs:comment "A typed input/output slot of a Step, bound at execution time to concrete entities (artifacts, context snapshots — referenced by hash)." .
+
+p-plan:isStepOfPlan a owl:ObjectProperty ;
+    rdfs:domain p-plan:Step ; rdfs:range p-plan:Plan ;
+    rdfs:label "isStepOfPlan" .
+
+p-plan:isPrecededBy a owl:ObjectProperty ;
+    rdfs:domain p-plan:Step ; rdfs:range p-plan:Step ;
+    rdfs:label "isPrecededBy" ;
+    rdfs:comment "Step ordering. apcoord:PlanEdge kind `precedes` projects onto this property; the richer typed edges (depends-on / alternative / condition / compensates / refines) stay apcoord:-reified." .
+
+p-plan:correspondsToStep a owl:ObjectProperty ;
+    rdfs:domain prov:Activity ; rdfs:range p-plan:Step ;
+    rdfs:label "correspondsToStep" ;
+    rdfs:comment "THE run bridge: an executed activity (apexec:ServiceExecution / an apful:Task's activity) points at the durable planned step it enacted. Paired with the spec-330 §9 qualified association (prov:agent + prov:hadRole + prov:hadPlan = the exact adopted plan revision), this is what makes an Endeavor's whole process reconstructable." .
+
+p-plan:hasInputVar a owl:ObjectProperty ;
+    rdfs:domain p-plan:Step ; rdfs:range p-plan:Variable ;
+    rdfs:label "hasInputVar" .
+
+p-plan:hasOutputVar a owl:ObjectProperty ;
+    rdfs:domain p-plan:Step ; rdfs:range p-plan:Variable ;
+    rdfs:label "hasOutputVar" .
+
+p-plan:isVariableOfPlan a owl:ObjectProperty ;
+    rdfs:domain p-plan:Variable ; rdfs:range p-plan:Plan ;
+    rdfs:label "isVariableOfPlan" .
+
+# ═══ Imported EP-PLAN terms (https://w3id.org/ep-plan — Markovic/Garijo/Edwards/Vasconcelos) ═══
+#
+# EP-PLAN is the published PROV extension for EXACTLY our plan↔execution gap: it aligns with
+# P-PLAN (ep-plan:correspondsToStep ≡ p-plan:correspondsToStep) and adds the four things P-PLAN
+# lacks that this substrate already produces as facts without vocabulary:
+#
+#   1. the TRACE BUNDLE  — projectEndeavorProvenance's per-Endeavor graph IS an
+#                          ep-plan:ExecutionTraceBundle (⊑ prov:Bundle);
+#   2. CONSTRAINTS + their EVALUATION — commitment bounds / plan-step criteria evaluated against
+#                          trace activities, with satisfied/violated as facts, not inference;
+#   3. OBJECTIVES        — apcoord:OutcomeSpecification is what the plan is FOR;
+#   4. STEP→PLAN DECOMPOSITION — the CoordinationPlan-step → run-ExecutionPlan compile bridge as
+#                          a first-class relation (alongside prov:wasDerivedFrom).
+#
+# Deliberately NOT imported: ep-plan:Policy/ResponsibleAgent/hasPermittedAgent — anything reading
+# like permission. A plan is never authority here (axiom above); authority stays with the
+# delegation/entitlement/custody gates, so no term that could be misread as a gate input crosses
+# the boundary. Communication* is fabric's job; MultiVariable/MultiStep wait for a reader.
+
+ep-plan:ExecutionTraceBundle a owl:Class ;
+    rdfs:subClassOf prov:Bundle , prov:Entity ;
+    rdfs:label "Execution Trace Bundle (EP-PLAN)" ;
+    rdfs:comment "A collection of trace elements generated during a single plan execution. The graph projectEndeavorProvenance emits per Endeavor is one; its members attach via ep-plan:hasTraceElement." .
+
+ep-plan:hasTraceElement a owl:ObjectProperty ;
+    rdfs:domain ep-plan:ExecutionTraceBundle ;
+    rdfs:label "hasTraceElement" ;
+    rdfs:comment "Links the bundle to its activities, agents, and entities. Range: prov:Activity ∪ prov:Agent ∪ prov:Entity." .
+
+ep-plan:Constraint a owl:Class ;
+    rdfs:label "Constraint (EP-PLAN)" ;
+    rdfs:comment "A restriction placed on a step or plan, evaluated against the execution trace. Commitment bounds (deadline) and step-level requirements ground here. EP-PLAN explicitly does NOT require a constraint be satisfied for execution to continue — violations are recordable facts, which is what makes honest audit possible." .
+
+ep-plan:hasConstraint a owl:ObjectProperty ;
+    rdfs:range ep-plan:Constraint ;
+    rdfs:label "hasConstraint" ;
+    rdfs:comment "Attaches a Constraint to a p-plan:Plan or Step (apcoord:CoordinationPlan / apcoord:PlanStep / apexec:ExecutionPlan)." .
+
+ep-plan:ConstraintEvaluation a owl:Class ;
+    rdfs:label "Constraint Evaluation (EP-PLAN)" ;
+    rdfs:comment "Qualifies HOW a trace activity was checked against a constraint (evaluator, method, when). The reified form behind satisfied/violated — the same qualified-relation pattern as prov:qualifiedAssociation." .
+
+ep-plan:evaluatedAgainst a owl:ObjectProperty ;
+    rdfs:range ep-plan:Constraint ;
+    rdfs:label "evaluatedAgainst" ;
+    rdfs:comment "A trace activity was evaluated against a constraint. Use the subproperties `satisfied` / `violated` to record the verdict as a FACT (never inferred from conversation — spec 334 §3 rule 2d applies to verdicts too)." .
+
+ep-plan:satisfied a owl:ObjectProperty ;
+    rdfs:subPropertyOf ep-plan:evaluatedAgainst ;
+    rdfs:range ep-plan:Constraint ;
+    rdfs:label "satisfied" ;
+    rdfs:comment "The activity satisfied the constraint. apcoord PlanStepSatisfied events (with evidenceRefs) project here." .
+
+ep-plan:violated a owl:ObjectProperty ;
+    rdfs:subPropertyOf ep-plan:evaluatedAgainst ;
+    rdfs:range ep-plan:Constraint ;
+    rdfs:label "violated" ;
+    rdfs:comment "The activity violated the constraint — recorded, never silently dropped (ADR-0013)." .
+
+ep-plan:FailedActivity a owl:Class ;
+    rdfs:subClassOf prov:Activity ;
+    rdfs:label "Failed Activity (EP-PLAN)" ;
+    rdfs:comment "An activity not executed in full — the point where a plan execution was interrupted. Failed apexec executions / withdrawn-commitment steps type here so failure is a first-class trace fact." .
+
+ep-plan:Objective a owl:Class ;
+    rdfs:label "Objective (EP-PLAN)" ;
+    rdfs:comment "The purpose a plan serves. apcoord:OutcomeSpecification grounds here: the outcome an Endeavor's adopted plan is FOR." .
+
+ep-plan:isAchievedBy a owl:ObjectProperty ;
+    rdfs:domain ep-plan:Objective ;
+    rdfs:label "isAchievedBy" ;
+    rdfs:comment "Objective → the plan (or plan element) expected to achieve it. Inverse: ep-plan:achieves." .
+
+ep-plan:achieves a owl:ObjectProperty ;
+    rdfs:range ep-plan:Objective ;
+    rdfs:label "achieves" ;
+    rdfs:comment "Plan (element) → Objective. apcoord:MilestoneAchievement / EndeavorSatisfied evidence projects onto this." .
+
+ep-plan:isDecomposedAsPlan a owl:ObjectProperty ;
+    rdfs:range p-plan:Plan ;
+    rdfs:label "isDecomposedAsPlan" ;
+    rdfs:comment "THE compile bridge, named: an apcoord:PlanStep is decomposed as the run-specific apexec:ExecutionPlan that enacts it. Emitted ALONGSIDE prov:wasDerivedFrom (derivation says where the run plan came from; decomposition says which step it elaborates). EP-PLAN scopes the domain to MultiStep; we use it for any step that compiles to a plan and keep the domain open here." .
+
+ep-plan:isSubPlanOfPlan a owl:ObjectProperty ;
+    rdfs:domain p-plan:Plan ; rdfs:range p-plan:Plan ;
+    rdfs:label "isSubPlanOfPlan" ;
+    rdfs:comment "Transitive plan containment — future CoordinationPlan hierarchies (child endeavor plans) without inventing a new relation." .
+
+# ═══ Grounding the substrate's plan variants ═══
+
+apexec:ExecutionPlan a owl:Class ;
+    rdfs:subClassOf p-plan:Plan ;
+    rdfs:label "ExecutionPlan" ;
+    rdfs:comment "RUN-SPECIFIC plan (spec 330 §8): one goal, one executor, one ADR-0044 loop. When it compiles an apcoord:PlanStep it is prov:wasDerivedFrom that step's adopted CoordinationPlan revision AND ep-plan:isDecomposedAsPlan of that step — never the durable shared plan itself. Declared here (ahead of the parked spec-330 W1) because plan.ttl owns the plan trichotomy; W1 extends, it does not rewrite." .

package/tbox/profile.ttl

@@ -0,0 +1,100 @@
+# T-box — the public agent PROFILE facet (spec 217 / 282 / 331; facet-registries.md §2, G2–G4).
+#
+# What this module owns: the SA-keyed, owner-written, unconditionally PUBLIC self-description
+# published through `AgentProfileResolver` under `atl:*` predicates and projected into the
+# discovery knowledge graph as `approf:*` (apps/demo-discovery-indexer PROFILE_KEYS).
+#
+# Until now `approf:` was a declared namespace with NO T-box file: `approf:displayName`,
+# `approf:description` and `approf:skills` were emitted into the production graph by the indexer
+# and read by the MCP without ever being declared. This module closes that (ADR-0009: on-chain
+# ontology governs records; ADR-0013: no read path for an undeclared term).
+#
+# ── The identifier / prose split (ADR-0051, facet-registries §7) ─────────────────────────────
+# The on-chain predicate key is `atl:skills` and is immutable (its id is keccak256("atl:skills"),
+# already registered and already written into live agents' profiles). The T-box term is
+# `approf:skills`. Both are OPAQUE KEYS. What they carry is a set of DECLARED CAPABILITY
+# PROJECTIONS (aps:CapabilityProtocolProjection, related by aps:declaresCapability) — the weakest
+# of the three assertion strengths. Prose and UI always say "capability".
+#
+# ── Assertion strength (capability-architecture.md §2) ───────────────────────────────────────
+# Everything in this module is SELF-DECLARED and unverified. It feeds discovery FIT scoring only.
+# Nothing here is a claim credential (aps:claimsCapability — private vault VC), nothing here is
+# demonstrated (aps:demonstratedCapability — execution provenance), and nothing here authorizes
+# anything (authority is delegation ∩ entitlement ∩ policy, at the gate).
+
+@prefix approf: <https://agenticprimitives.dev/ns/profile#> .
+@prefix ap:     <https://agenticprimitives.dev/ns/core#> .
+@prefix aps:    <https://agenticprimitives.dev/ns/skill#> .
+@prefix apctx:  <https://agenticprimitives.dev/ns/context#> .
+@prefix apg:    <https://agenticprimitives.dev/ns/geo#> .
+@prefix rdf:    <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+@prefix rdfs:   <http://www.w3.org/2000/01/rdf-schema#> .
+@prefix owl:    <http://www.w3.org/2002/07/owl#> .
+@prefix xsd:    <http://www.w3.org/2001/XMLSchema#> .
+@prefix prov:   <http://www.w3.org/ns/prov#> .
+@prefix dul:    <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#> .
+
+approf: a owl:Ontology ;
+  rdfs:label "Agentic Primitives — public agent profile ontology" ;
+  owl:versionInfo "0.1.0" ;
+  rdfs:comment "SA-keyed public self-description projected from AgentProfileResolver. Owner-asserted, opt-in, unconditionally public, discovery-rankable. Self-declared evidence only — never a credential, never authority." .
+
+approf:AgentProfile a owl:Class ;
+  rdfs:subClassOf ap:Facet , prov:Entity , dul:InformationObject ;
+  rdfs:label "AgentProfile" ;
+  rdfs:comment "The public self-description facet of ONE Smart Agent, keyed by the SA address (never by a name node — it must survive a rename and exist for nameless agents, ADR-0010/0020)." .
+
+approf:describesAgent a owl:ObjectProperty ;
+  rdfs:domain approf:AgentProfile ; rdfs:range ap:CanonicalAgentId ;
+  rdfs:label "describesAgent" .
+
+# ─── Existing, live predicates — declared here for the first time ───────────
+
+approf:displayName a owl:DatatypeProperty ;
+  rdfs:domain approf:AgentProfile ; rdfs:range xsd:string ;
+  rdfs:label "displayName" ;
+  rdfs:comment "atl:displayName. The agent's own public display name. Distinct from the name-node label and from any vault display name (agent-metadata-tiers.md: same field name ≠ same field; never auto-synced)." .
+
+approf:description a owl:DatatypeProperty ;
+  rdfs:domain approf:AgentProfile ; rdfs:range xsd:string ;
+  rdfs:label "description" ;
+  rdfs:comment "atl:description, SA-keyed. NOT the node-keyed name-record description (apnam:description) — facet-registries G8: emitting both under this IRI lets tier 2 clobber tier 3 by loop order. Free text; a SECONDARY carrier only, never a structured filter target." .
+
+approf:skills a owl:DatatypeProperty ;
+  rdfs:domain approf:AgentProfile ; rdfs:range xsd:string ;
+  rdfs:label "skills (declared capability projections)" ;
+  rdfs:comment "atl:skills (spec 282). Comma-joined DECLARED CAPABILITY PROJECTIONS — aps:CapabilityProtocolProjection nodes related by aps:declaresCapability. Legacy key retained for ABI (ADR-0051); prose says 'declared capabilities'. Spec 331 migrates the value space from free-text labels to canonical catalog capability ids." .
+
+approf:declaresCapabilityId a owl:DatatypeProperty ;
+  rdfs:domain approf:AgentProfile ; rdfs:range xsd:string ;
+  rdfs:label "declaresCapabilityId" ;
+  rdfs:comment "Spec 331 — the PARSED, resolvable capability id carried inside an approf:skills token (e.g. 'adv:estate-planning'). One triple per id, projected by the indexer so the matcher can do set-membership instead of substring search. The datatype is a string, not an IRI, because the token is exactly what the agent wrote on chain; resolution to an aps:Capability IRI is the catalog's job and may fail (an unresolvable id is an honest miss, never a silent skip — ADR-0013)." .
+
+# ─── G2 / G3 / G4 — the three facets registered by governor tx
+#     0x53acec54d850b8a790da4feda055abf81a0c2f203c1a69d0644d1a1138a18789 ──────
+
+approf:languages a owl:DatatypeProperty ;
+  rdfs:domain approf:AgentProfile ; rdfs:range xsd:string ;
+  rdfs:label "languages" ;
+  apctx:classifiedBy apctx:LanguageFacet ;
+  rdfs:comment "atl:languages (facet-registries G2). VALUE SPACE: comma-separated BCP-47 language tags, normalized lowercase, e.g. 'es,en,pt-br'. Matching is subtag-prefix based ('es' matches 'es-ES'), never substring. A flat string for parity with atl:skills; per-language proficiency waits for spec 330 and is a value-space migration inside this one predicate, not a new one. RANKING ROLE: soft boost, plus an OPT-IN hard mandate (requireLanguage) that a caller must ask for explicitly." .
+
+approf:regions a owl:DatatypeProperty ;
+  rdfs:domain approf:AgentProfile ; rdfs:range xsd:string ;
+  rdfs:label "regions" ;
+  apctx:classifiedBy apctx:JurisdictionFacet ;
+  rdfs:comment "atl:regions (facet-registries G3). VALUE SPACE: comma-separated UPPERCASE codes drawn from the GeoFeatureRegistry controlled vocabulary (spec 251) — ISO 3166-1 alpha-2, ISO 3166-2 subdivisions, or a registered supranational feature code, e.g. 'EU,ES,ES-CT'. Requiring the value space to be GeoFeatureRegistry-drawn is what makes a later upgrade to explicit (featureId, version) references a VALUE-SPACE migration inside one predicate rather than a new predicate + projector + UI. RELATION COLLAPSE (accepted v1 limitation): this flattens the five apg:geoRelation values — servesWithin, operatesIn, licensedIn, residentOf, originIn — into one list. servesWithin and licensedIn are materially different claims for a regulated advisor; if that distinction becomes load-bearing, add a second predicate (atl:licensedIn), never structure inside this string. The full truth stays in the private apg: GeoClaimCredential." .
+
+approf:focusAreas a owl:DatatypeProperty ;
+  rdfs:domain approf:AgentProfile ; rdfs:range xsd:string ;
+  rdfs:label "focusAreas" ;
+  apctx:classifiedBy apctx:KnowledgeDomain ;
+  rdfs:comment "atl:focusAreas (facet-registries G4). VALUE SPACE: comma-separated subject-domain labels, lowercase-hyphenated, e.g. 'modelo-720,forced-heirship'. Maps to the apctx:KnowledgeDomain facet so it stays ORTHOGONAL to capability identity — a focus area is a subject, never a declared capability (ADR-0051). RANKING ROLE: fitScore boost ONLY, capped hardest of the three. It must NEVER become a hard filter: a focus area is an emphasis, not a boundary, and an agent that has not published one is UNKNOWN, not absent." .
+
+# ─── The value-space anchors these three point at ───────────────────────────
+
+approf:regionVocabulary a owl:AnnotationProperty ;
+  rdfs:label "regionVocabulary" ;
+  rdfs:comment "Declares which controlled vocabulary an approf:regions value space draws from. Points at apg: (GeoFeatureRegistry) — see cbox/profile-facet-vocabulary.ttl." .
+
+approf:regions approf:regionVocabulary apg:geoKind .

package/tbox/skills.ttl

@@ -120,3 +120,135 @@ aps:matchedSkill a owl:ObjectProperty ;
     rdfs:subPropertyOf aps:matchedCapability ;
     rdfs:domain aps:IntentCapabilityMatch ; rdfs:range aps:CapabilityDefinition ;
     rdfs:label "matchedSkill (deprecated)" .
+
+# ═══════════════════════════════════════════════════════════════════════════
+# Capability IDENTITY, the independent relations, and CATALOGS
+# (spec 330 W0 §5 — unparked by spec 331; capability-architecture.md §2 + §8)
+# ═══════════════════════════════════════════════════════════════════════════
+#
+# Prefixes used below beyond the header: apctx: (context facets), apguide: (playbooks),
+# apexec: (executions — declared in spec 330 W1, referenced here by IRI only), prov:, skos:.
+#
+# THE DISTINCTION THIS SECTION EXISTS TO HOLD (architecture §1):
+#   aps:Capability            — the stable, provider-independent IDENTITY of an outcome.
+#   aps:CapabilityDefinition  — a VERSIONED artifact that defines it (above).
+#   aps:CapabilityProtocolProjection — an ADVERTISEMENT of it (a card AgentSkill, an
+#                               atl:skills token, an offering). Above.
+# Until now identity was implicit in the definition. Spec 331 mints it explicitly, because a
+# domain catalog needs many agents to reference ONE id across MANY definition versions.
+
+@prefix apctx:   <https://agenticprimitives.dev/ns/context#> .
+@prefix apguide: <https://agenticprimitives.dev/ns/guidance#> .
+@prefix apexec:  <https://agenticprimitives.dev/ns/execution#> .
+@prefix prov:    <http://www.w3.org/ns/prov#> .
+@prefix skos:    <http://www.w3.org/2004/02/skos/core#> .
+@prefix sh:      <http://www.w3.org/ns/shacl#> .
+@prefix xsd:     <http://www.w3.org/2001/XMLSchema#> .
+
+aps:Capability a owl:Class ;
+    rdfs:label "Capability" ;
+    rdfs:comment "The stable, provider-independent identity of an achievable OUTCOME. Not a service, not a plan, not a taxonomy term, not an execution, and not a subject domain. Its identity NEVER depends on one provider, one jurisdiction, one language, or one playbook — those are apctx: facets of a realization. A capability is not a prov:Activity: it is what COULD be achieved; an activity is an occurrence that attempted it (architecture §5)." .
+
+aps:CapabilityCatalog a owl:Class ;
+    rdfs:label "CapabilityCatalog" ;
+    rdfs:comment "A named, versioned, steward-owned set of capability definitions for one bounded context (e.g. the family-office advisory catalog, spec 331). A catalog is a DISTRIBUTION and GOVERNANCE unit, never a taxonomy: membership implies no hierarchy, and a capability may appear in several catalogs." .
+
+aps:catalogSteward a owl:ObjectProperty ;
+    rdfs:domain aps:CapabilityCatalog ; rdfs:range ap:CanonicalAgentId ;
+    rdfs:label "catalogSteward" ;
+    rdfs:comment "The account authorized to publish/version definitions in this catalog (SkillDefinitionRegistry stewardAccount)." .
+
+aps:inCatalog a owl:ObjectProperty ;
+    rdfs:domain aps:CapabilityDefinition ; rdfs:range aps:CapabilityCatalog ;
+    rdfs:label "inCatalog" .
+
+aps:capabilityId a owl:DatatypeProperty ;
+    rdfs:domain aps:Capability ; rdfs:range xsd:string ;
+    rdfs:label "capabilityId" ;
+    rdfs:comment "The canonical, human-readable, STABLE id string (a CURIE, e.g. 'adv:succession-plan-design'). keccak256 of this exact string is the on-chain SkillDefinitionRegistry skillId — the same keccak-of-CURIE convention atl:* predicates use. Once published it is never re-spelled: a rename is a new capability plus a skos:exactMatch, never an edit." .
+
+aps:outcomeStatement a owl:DatatypeProperty ;
+    rdfs:domain aps:CapabilityDefinition ; rdfs:range xsd:string ;
+    rdfs:label "outcomeStatement" ;
+    rdfs:comment "One sentence in the PASSIVE COMPLETED voice naming what is true when the capability has been realized ('a target asset allocation and its implementation are determined for a stated mandate'). Written this way deliberately: an outcome statement that can only be phrased as an activity ('advises on…') is a signal the term is a service or a subject domain, not a capability." .
+
+# ─── The independent relations. NEVER an overloaded `implementsCapability`. ──
+
+aps:definesCapability a owl:ObjectProperty ;
+    rdfs:domain aps:CapabilityDefinition ; rdfs:range aps:Capability ;
+    rdfs:label "definesCapability" ;
+    rdfs:comment "Which versioned artifact defines it. Many definition VERSIONS, one capability identity." .
+
+aps:classifiesCapability a owl:ObjectProperty ;
+    rdfs:range aps:Capability ;
+    rdfs:label "classifiesCapability" ;
+    rdfs:comment "External taxon → capability, via SKOS alignment. Classification is never possession and never authorization (architecture §2 axiom 4). External taxa are ALIGNED, never term-copied into this T-box (invariant 11)." .
+
+aps:assertsCapability a owl:ObjectProperty ;
+    rdfs:range aps:Capability ;
+    rdfs:label "assertsCapability" ;
+    rdfs:comment "Abstract parent of the three ASSERTION STRENGTHS. They are subproperties rather than a datatype rank because the asserter and the verification path differ STRUCTURALLY, not in degree. They must be surfaced to users separately and never summed as one signal." .
+
+aps:declaresCapability a owl:ObjectProperty ;
+    rdfs:subPropertyOf aps:assertsCapability ; rdfs:range aps:Capability ;
+    rdfs:label "declaresCapability" ;
+    rdfs:comment "SELF-declared, owner-signed, UNVERIFIED: an atl:skills token, a card AgentSkill, a crawled offering. Costs one transaction and nothing else — anyone may declare anything. Feeds discovery FIT scoring only, and must never be presented as endorsement." .
+
+aps:claimsCapability a owl:ObjectProperty ;
+    rdfs:subPropertyOf aps:assertsCapability ; rdfs:range aps:Capability ;
+    rdfs:label "claimsCapability" ;
+    rdfs:comment "CREDENTIALED: an aps:SkillClaim credential (self or endorsed), vault-resident, referencing an on-chain (definitionId, version). A SELF claim is bounded (SELF_MAX_PROFICIENCY) and forbidden the endorsement relations; an ENDORSED claim carries a distinct issuer. Feeds TRUST scoring — and only through its public commitment, never its body (ADR-0040)." .
+
+aps:demonstratedCapability a owl:ObjectProperty ;
+    rdfs:subPropertyOf aps:assertsCapability ; rdfs:range aps:Capability ;
+    rdfs:label "demonstratedCapability" ;
+    rdfs:comment "EARNED: evidenced by execution provenance — a conforming apexec:ServiceExecution that realized the capability. Derived, never asserted by the subject. Feeds an OUTCOME signal, and is the only assertion strength that cannot be produced by writing a string." .
+
+# ─── Structure: a DAG of composition/specialisation, never a single-parent tree ──
+
+aps:specializesCapability a owl:ObjectProperty ;
+    rdfs:domain aps:Capability ; rdfs:range aps:Capability ;
+    a owl:TransitiveProperty ;
+    rdfs:label "specializesCapability" ;
+    rdfs:comment "A genuinely NARROWER FORM OF THE SAME ability (private fund diligence ⊏ manager selection & diligence). Multi-parent is legal and expected; only cycles are forbidden. NOT rdfs:subClassOf — capabilities are individuals, not classes, and subclassing them would make every facet stack into a hierarchy. A jurisdiction, a language or an asset class is NEVER a specialization: those are apctx: facets." .
+
+aps:hasComponentCapability a owl:ObjectProperty ;
+    rdfs:domain aps:Capability ; rdfs:range aps:Capability ;
+    rdfs:label "hasComponentCapability" ;
+    rdfs:comment "A broader outcome DEPENDS ON constituent abilities that are part of achieving it. NO ORDERING is implied — ordering lives in an apexec:ExecutionPlan (apexec:precedes), never in capability semantics (architecture invariant 8)." .
+
+aps:requiresCapability a owl:ObjectProperty ;
+    rdfs:domain aps:Capability ; rdfs:range aps:Capability ;
+    rdfs:label "requiresCapability" ;
+    rdfs:comment "A DEPENDENCY: the object must be realizable for the subject to be realizable, but is not a part of it (covenant analysis requires secured-lending structuring — you cannot stress-test a facility that was never structured). Distinct from hasComponentCapability, which is part-of." .
+
+apguide:supportsCapability a owl:ObjectProperty ;
+    rdfs:range aps:Capability ;
+    rdfs:label "supportsCapability" ;
+    rdfs:comment "AgentSkillPackage (SKILL.md playbook) → capability, 0..N. Which plans MAY inform a realization. GUIDANCE ONLY — never authority, never identity (ADR-0050). A card projection is never wired to exactly one playbook (architecture §2 axiom 1)." .
+
+apexec:realizesCapability a owl:ObjectProperty ;
+    rdfs:range aps:Capability ;
+    rdfs:label "realizesCapability" ;
+    rdfs:comment "ServiceExecution → capability. What actually occurred. Declared here (the aps: module owns the capability end of the relation); the apexec: classes land with spec 330 W1." .
+
+# ─── Realization contracts ──────────────────────────────────────────────────
+
+aps:CapabilityRealizationContract a owl:Class ;
+    rdfs:subClassOf sh:NodeShape ;
+    rdfs:label "CapabilityRealizationContract" ;
+    rdfs:comment "A SHACL shape over PROV stating what a CONFORMING realization of one capability must contain: activity type, required prov:agent roles, prov:used input types, prov:generated output types, the prov:qualifiedAssociation carrying prov:hadPlan, and completion conditions. It governs SHAPE, not outcome — a recorded decline is a conforming realization. It is NOT a test suite and NOT an authorization: no gate may read it." .
+
+aps:hasRealizationContract a owl:ObjectProperty ;
+    rdfs:domain aps:CapabilityDefinition ; rdfs:range aps:CapabilityRealizationContract ;
+    rdfs:label "hasRealizationContract" .
+
+aps:contractStatus a owl:DatatypeProperty ;
+    rdfs:domain aps:CapabilityDefinition ; rdfs:range xsd:string ;
+    rdfs:label "contractStatus" ;
+    rdfs:comment "'enforced' | 'deferred'. DEFERRED IS FIRST-CLASS AND HONEST: a capability whose realizations this substrate cannot yet observe declares 'deferred' plus the evidence that would be needed, rather than carrying a contract nothing validates. An unenforceable contract is worse than an absent one — it makes a claim about verification the system cannot keep (ADR-0013)." .
+
+aps:deferredContractRationale a owl:DatatypeProperty ;
+    rdfs:domain aps:CapabilityDefinition ; rdfs:range xsd:string ;
+    rdfs:label "deferredContractRationale" ;
+    rdfs:comment "Required when contractStatus = 'deferred': one line naming the evidence that would make a contract enforceable." .

package/tbox/trust.ttl

@@ -88,3 +88,123 @@ aptrust:hasTrustScore a owl:ObjectProperty ;
   rdfs:domain apdisc:TrustDetermination ;
   rdfs:range aptrust:TrustScore ;
   rdfs:label "hasTrustScore" .
+
+# ═══════════════════════════════════════════════════════════════════════════
+# T-BOX PROMOTION of the projected trust-fabric terms (facet-registries G1; spec 331)
+# ═══════════════════════════════════════════════════════════════════════════
+#
+# WHAT WAS WRONG. `apps/demo-discovery-indexer/src/ontology.ts` coined a set of `ap:` terms for
+# the relationship and attestation projectors and wrote them into the production graph;
+# `apps/demo-discovery-mcp/src/graphdb.ts` queries them by name (`?e ap:edgeId ?eid ;
+# ap:edgeSubject ?subj ; ap:edgeObject ?obj ; …`). None of them were ever declared in a T-box.
+# `aprel:` is a declared namespace with no module and no terms, and this file typed the EDGE
+# (aptrust:TrustGraphEdge) while declaring nothing about its subject, object, type or status.
+# The result was a live query path over undeclared vocabulary — exactly the read-path-without-a-
+# definition condition ADR-0013 forbids, and the mirror image of gap G5 on the write side.
+#
+# WHY THE `ap:` PREFIX IS RETAINED RATHER THAN RE-MINTED AS `aptrust:` OR `aprel:`.
+# The IRIs are already in the deployed GraphDB and already in the MCP's SPARQL query TEXT.
+# Re-prefixing them is a graph migration plus a coordinated Worker deploy, not an edit — and it
+# would buy nothing semantic, because a T-box term's namespace is not its meaning. This follows
+# the established discipline (facet-registries §7, ADR-0051): IDENTIFIERS KEEP THEIR NAMES, prose
+# and docs use the canonical term. The alternative considered and rejected was declaring `aptrust:`
+# twins as owl:equivalentProperty aliases — that is a SECOND mechanism for one read path, which
+# ADR-0013 forbids more strongly than it forbids an awkward prefix.
+#
+# NOTHING IS MINTED HERE. Every term below is verbatim the IRI the indexer already emits.
+# Promotion is a declaration, not a change; the graph is unaffected.
+#
+# ENDPOINT-RELATIVE vs ABSOLUTE — the invariant that decides which properties sit where.
+# One on-chain AgentRelationship edge is ONE record shared by both endpoints, and the edge node's
+# IRI derives from the deterministic on-chain edgeId, so BOTH agents project the SAME subject.
+# Its properties must therefore be endpoint-INDEPENDENT. `ap:edgeDirection` and `ap:relatedAgent`
+# are meaningful only relative to whoever is looking, so they hang on the AGENT; the shared edge
+# node states subject and object ABSOLUTELY.
+
+@prefix apreg: <https://agenticprimitives.dev/ns/registry#> .
+@prefix xsd:   <http://www.w3.org/2001/XMLSchema#> .
+
+# ─── Agent → child-node facet links ─────────────────────────────────────────
+
+ap:hasRelationship a owl:ObjectProperty ;
+  rdfs:domain ap:Agent ; rdfs:range aptrust:TrustGraphEdge ;
+  rdfs:label "hasRelationship" ;
+  rdfs:comment "Agent → a projected AgentRelationship edge it is an endpoint of (either side)." .
+
+ap:hasAttestation a owl:ObjectProperty ;
+  rdfs:domain ap:Agent ; rdfs:range apatt:Attestation ;
+  rdfs:label "hasAttestation" ;
+  rdfs:comment "Agent → an AttestationRegistry row in which it is the SUBJECT. Issuer-side rows are not projected onto the issuer: an attestation is evidence ABOUT its subject." .
+
+# ─── Edge-node properties — ABSOLUTE, endpoint-independent ──────────────────
+
+ap:edgeId a owl:DatatypeProperty ;
+  rdfs:domain aptrust:TrustGraphEdge ; rdfs:range xsd:string ;
+  rdfs:label "edgeId" ;
+  rdfs:comment "The deterministic on-chain edgeId = computeEdgeId(subject, object, relationshipType). The edge node's IRI derives from it, which is why both endpoints project one shared node." .
+
+ap:edgeSubject a owl:ObjectProperty ;
+  rdfs:domain aptrust:TrustGraphEdge ; rdfs:range ap:CanonicalAgentId ;
+  rdfs:label "edgeSubject" ;
+  rdfs:comment "The SA that PROPOSED the edge. On-chain `proposeEdge` requires msg.sender == subject, so this is structurally the proposing party — never inferred, never symmetric with edgeObject." .
+
+ap:edgeObject a owl:ObjectProperty ;
+  rdfs:domain aptrust:TrustGraphEdge ; rdfs:range ap:CanonicalAgentId ;
+  rdfs:label "edgeObject" ;
+  rdfs:comment "The SA that CONFIRMED the edge. An edge reaches ACTIVE only through PROPOSED → CONFIRMED → ACTIVE, so an active edge is bilateral by construction: both parties consented on chain." .
+
+ap:relationshipType a owl:DatatypeProperty ;
+  rdfs:domain aptrust:TrustGraphEdge ; rdfs:range xsd:string ;
+  rdfs:label "relationshipType" ;
+  rdfs:comment "The well-known label ('HAS_MEMBER', 'VALIDATION_TRUST', 'RECOMMENDS', …) when the type hash resolves; absent otherwise. Never a substitute for relationshipTypeId." .
+
+ap:relationshipTypeId a owl:DatatypeProperty ;
+  rdfs:domain aptrust:TrustGraphEdge ; rdfs:range xsd:string ;
+  rdfs:label "relationshipTypeId" ;
+  rdfs:comment "The raw on-chain bytes32 type id, ALWAYS emitted — an unresolved governor-registered type must still be queryable (ADR-0013: no silent gaps)." .
+
+ap:edgeStatus a owl:DatatypeProperty ;
+  rdfs:domain aptrust:TrustGraphEdge ; rdfs:range xsd:string ;
+  rdfs:label "edgeStatus" ;
+  rdfs:comment "'PROPOSED' | 'CONFIRMED' | 'ACTIVE' | 'REVOKED'. Only ACTIVE edges may inform trust scoring — a proposal is one party talking to itself, and revocation is terminal." .
+
+# ─── Agent-level, endpoint-RELATIVE denormalizations ────────────────────────
+
+ap:relatedAgent a owl:ObjectProperty ;
+  rdfs:domain ap:Agent ; rdfs:range ap:CanonicalAgentId ;
+  rdfs:label "relatedAgent" ;
+  rdfs:comment "The COUNTERPARTY as seen from this agent. Endpoint-relative by construction, hence on the agent and never on the shared edge node." .
+
+ap:edgeDirection a owl:DatatypeProperty ;
+  rdfs:domain ap:Agent ; rdfs:range xsd:string ;
+  rdfs:label "edgeDirection" ;
+  rdfs:comment "'subject' | 'object' — which end of the edge THIS agent occupies. Endpoint-relative; see ap:relatedAgent." .
+
+ap:edgeCount a owl:DatatypeProperty ;
+  rdfs:domain ap:Agent ; rdfs:range xsd:integer ; rdfs:label "edgeCount" .
+
+ap:activeEdgeCount a owl:DatatypeProperty ;
+  rdfs:domain ap:Agent ; rdfs:range xsd:integer ;
+  rdfs:label "activeEdgeCount" ;
+  rdfs:comment "Edges in ACTIVE status only. This is the count trustScore reads, and it saturates fast — a public edge is cheap to create, so it is corroboration, never authority." .
+
+# ─── Attestation terms with no apatt: home (the T-box does not model the
+#     on-chain struct's issuer or its isValid(uid) view) ─────────────────────
+
+ap:attestationIssuer a owl:ObjectProperty ;
+  rdfs:domain apatt:Attestation ; rdfs:range ap:CanonicalAgentId ;
+  rdfs:label "attestationIssuer" ;
+  rdfs:comment "The asserting party. AttestationRegistry leaves msg.sender UNCONSTRAINED and derives authority from a recomputed EIP-712 signature, so the issuer here is the SIGNER, never the transaction sender. This is what makes third-party endorsement relayable without the issuer holding gas — the property spec 331's endorsement ceremony depends on." .
+
+ap:attestationValid a owl:DatatypeProperty ;
+  rdfs:domain apatt:Attestation ; rdfs:range xsd:boolean ;
+  rdfs:label "attestationValid" ;
+  rdfs:comment "The contract's isValid(uid) verdict at index time. Note AR-06: there is NO issuer-revoke entrypoint — only the holder or a party may revoke on chain; issuer-side revocation is off-chain via offchainCredentialStatusList and is therefore NOT reflected here." .
+
+ap:attestationCount a owl:DatatypeProperty ;
+  rdfs:domain ap:Agent ; rdfs:range xsd:integer ; rdfs:label "attestationCount" .
+
+ap:validAttestationCount a owl:DatatypeProperty ;
+  rdfs:domain ap:Agent ; rdfs:range xsd:integer ;
+  rdfs:label "validAttestationCount" ;
+  rdfs:comment "Non-revoked attestations where this agent is the SUBJECT. The count trustScore reads." .