Reference

Engagement Accelerators

The knowledge graph classifies what kind of engagement activity an organization, attestation, need or commitment concerns with the Phases of Engagement Toolkit's twelve Engagement Accelerators — the SKOS scheme poe:EngagementAcceleratorScheme. The scheme is exactly the Toolkit's twelve domains and nothing else: it carries no narrower concepts, and Global.Church adds none of its own to it. The Toolkit (April 2026; Frontiers, IMB, Joshua Project, Engage Network, Vision 5:9, Accelerate) is the source framework; Global.Church curates the representation.

What an organization is equipped to do — Bible translation, pioneer church formation, funder cultivation, media evangelism — is a different question, answered by a different, Global.Church-owned vocabulary: the organizational capability scheme via gc:hasOrganizationalCapability. The two axes are orthogonal; see Three classification dimensions below.

Both vocabularies are loaded into the <https://data.global.church/vocabs/> named graph.

The twelve accelerators

Code	Accelerator	Concept
`PRA`	Prayer	`poe:AccPrayer`
`SRA`	Scripture/Resource Access	`poe:AccScriptureAccess`
`VIS`	Vision Casting	`poe:AccVisionCasting`
`MNE`	Multi-node Engagement	`poe:AccMultiNode`
`MOB`	Mobilization/Sending	`poe:AccMobilization`
`COL`	Collaborative Engagement	`poe:AccCollaboration`
`COM`	Meeting Needs/Compassion	`poe:AccCompassion`
`CTX`	Critical Contextualization	`poe:AccContextualization`
`RCI`	Research/Cultural Insights	`poe:AccResearch`
`TRN`	Training/Equipping	`poe:AccTraining`
`MUL`	Multiplying Efforts	`poe:AccMultiplication`
`MKT`	Marketplace Involvement	`poe:AccMarketplace`

Each concept carries the Toolkit's own definition as skos:definition and its code as skos:notation. The codes are what the API accepts: engagementAccelerators on POST /v0/engagement-claims/submit, accelerators on POST /v0/needs/submit and acceleratorScope on POST /v0/commitments/submit each take one or more of the twelve codes and reject anything else with 400.

A planning aid, not a scorecard. The Toolkit says its accelerators are "for your own strategic planning, not for research, reporting, or outside assessment." In the graph they classify source-attributed activity — what a named organization says it does, in which domain. They are never rolled into a per-people-group scorecard, and no organization is ranked by them. The Toolkit-faithful planning surface is gc:AcceleratorPhaseProfile (below).

Three classification dimensions on an organization

Dimension	Property	Vocabulary	Question
Type	`gc:hasOrganizationType`	`gc:OrganizationTypeScheme` (10 structural types)	What is it?
Engagement accelerator	`gc:hasEngagementAccelerator`	`poe:EngagementAcceleratorScheme` (the Toolkit's 12 domains)	In which Toolkit domains is it active?
Organizational capability	`gc:hasOrganizationalCapability`	`gc:OrganizationalCapabilityScheme` (19 capabilities, 94 functions)	What is it equipped to do?

These are independent and compose at query time. IMB, for example, is a Mission Agency active in Mobilization/Sending, Research/Cultural Insights, Training/Equipping and Multiplying Efforts, whose capabilities include Pioneer Church Formation, Cross-Cultural Deployment, Worker Recruitment, People Group Research, Reproducible Discipleship Frameworks and Trainer-of-Trainers Programs. Belief and denomination classifications sit alongside these on the organization.

Every capability concept is also an at:Capability — the faith-market instance of the shared Agentic Trust base's capability concept — so an organization's capabilities are visible to any consumer of that base (agent cards, skills, capability requirements) through at:hasCapability, of which gc:hasOrganizationalCapability is a sub-property.

Property reference: `gc:hasEngagementAccelerator`

Detail	Value
Type	`owl:ObjectProperty`
Values	The twelve top concepts of `poe:EngagementAcceleratorScheme` — nothing narrower
Multi-valued	Yes
Applies to	`at:Organization`, `gc:EngagementAttestation`, `at:Need`
Sibling properties	`gc:commitmentAcceleratorScope` (on `at:Commitment`), `gc:currentEngagementAccelerator` (on `gc:EngagementStateManifestation`), `gc:focusAccelerator` (on `gc:ServiceFocusAssociation`) — same values

On an organization it declares the Toolkit domains the organization is active in. On an attestation it declares the domain(s) of the engagement the organization is reporting for a specific people group. SHACL requires every value to be a skos:topConceptOf poe:EngagementAcceleratorScheme.

Querying

The twelve domains with their codes

Code
 
PREFIX poe:  <https://ontology.global.church/poe#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>

SELECT ?concept ?label ?code WHERE {
  ?concept skos:topConceptOf poe:EngagementAcceleratorScheme ;
           skos:prefLabel ?label ;
           skos:notation ?code .
}
ORDER BY ?code

Organizations active in Multiplying Efforts

Code
 
PREFIX gc:   <https://ontology.global.church/core#>
PREFIX at:   <https://agentictrustlabs.dev/ns/agentic-trust#>
PREFIX poe:  <https://ontology.global.church/poe#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>

SELECT ?org ?orgName WHERE {
  ?org a at:Organization ;
       rdfs:label ?orgName ;
       gc:hasEngagementAccelerator poe:AccMultiplication .
}
ORDER BY ?orgName

Organizations equipped for a specific function (the capability axis)

Code
 
PREFIX gc:   <https://ontology.global.church/core#>
PREFIX at:   <https://agentictrustlabs.dev/ns/agentic-trust#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>

SELECT ?org ?orgName WHERE {
  ?org a at:Organization ;
       rdfs:label ?orgName ;
       gc:hasOrganizationalCapability gc:CFnPioneerChurchFormation .
}
ORDER BY ?orgName

Combine the two to ask a coordination question — which organizations active in Multiplying Efforts are equipped for house-church development? — by joining gc:hasEngagementAccelerator poe:AccMultiplication with gc:hasOrganizationalCapability gc:CFnHouseChurchDevelopment.

The Toolkit's diagnostic questions for an accelerator at a phase

gc:AcceleratorPhaseProfile carries the Toolkit's own appendix — for each of the 12 accelerators × 7 phases, the diagnostic questions a team asks itself. It asserts no priority ranking (the Toolkit removed its priority matrix; so did the ontology in v0.45.0).

Code
 
PREFIX gc:   <https://ontology.global.church/core#>
PREFIX poe:  <https://ontology.global.church/poe#>

SELECT ?question WHERE {
  ?profile a gc:AcceleratorPhaseProfile ;
           gc:acceleratorDomain poe:AccPrayer ;
           gc:engagementPhase poe:Phase1 ;
           gc:diagnosticQuestion ?question .
}

Provenance

The curated organization seed in <https://data.global.church/orgs/> describes itself: the graph is a void:Dataset attributed to Global.Church with gc:derivationMethod gc:dm-public-web-research ("curated by Global.Church staff from each organization's own public materials; desk research; no organization has confirmed its own record"), and each organization carries prov:hadPrimarySource naming the site read. Treat the classifications above as Global.Church's reading of public materials, not as the organization's own statement, until an organization confirms them.

Last modified on October 27, 2026

HIS Registries The Ekklesia Model