Solid Futures Sector Ontology
type: Ontology
preferred namespace prefix: fut
preferred namespace uri: https://w3id.org/jeswr/sectors/futures#
imports: core
version info: 0.2.0
version IRI: https://w3id.org/jeswr/sectors/futures/0.2.0
description: The participatory-democracy / shared-futures deliberation data sector for the unite platform (jeswr/unite): expression-layer statements (life context, vision, claim, need, satisfier, value) living in the author's pod; tri-state resonance reactions living in the reactor's pod; process-layer deliberations, synthesized shared futures with per-cluster bridging evidence and a mandatory dissent annex; the Max-Neef needs matrix (axiological + existential schemes), the Schwartz-seeded value scheme, and the ODRL consent-action profile. Aligns Mode-A to ActivityStreams 2.0, PROV-O, ODRL 2.2 and the literature sources in futures-alignments.ttl. v0.2.0 ADDITIVE (unite S1 draft, vocab/futures-0.2.0-draft.ttl @ ff18a63 — SCOPE-DIFFERENTIATION §3.2 + §4.2): the scope-B infrastructure-proposal layer (fut:InfraProposal ⊑ wf:Task with targetsSystem / proposalKind / affectsRole / breakingChange / migrationPath / referenceImplementation), the adoption machinery (fut:AdoptionDecision ⊑ fut:SharedFuture — ratification MEASURED via fut:AdoptionObservation records of fedreg:acceptsSpec advertisements, never asserted), scope-C self-describing legitimacy (fut:methodProvenance, fut:decomposedBy), and the Convergence-Room critique unit (fut:Critique) + the VSD prompt (fut:indirectStakeholders). No 0.1.0 term changed; fut:onStatement's rdfs:domain was WIDENED (removed) because Critique reuses it — the section-6 multi-class-property rule.
modified: 2026-07-04
comment: Sector ontology for unite Stage-1 (design/01-data-model.md). Version 0.2.0 is the ADDITIVE delta unite's S1 build drafted (its ratification is the first scope-B deliberation — unite SCOPE-DIFFERENTIATION §3.1 B4); the namespace-governance migration to a steward-circle namespace remains a documented follow-on (unite design/04), carried by fedreg:acceptsSpec dual-advertisement.

SKOS Concept
type: Class

SKOS Concept Scheme
type: Class

wf Task
type: Class

ODRL Action
type: Class

ODRL Left Operand
type: Class

Life Context
type: Class
type: SubKind
subclass of: InformationResource
definition: A self-description of the author's PRESENT circumstances ('my current life'). An information resource describing a situation (the situation itself is not reified in v0.1). Content via as:content; may carry fut:expressesNeed links to the Needs it surfaces.
scope note: gufo:SubKind of core:InformationResource. Lives in the author's pod under the design/01 privacy tiers (private by default).

Vision Statement
type: Class
type: SubKind
subclass of: InformationResource
definition: A narrative description of the best possible future FOR THE AUTHOR ('my ideal future') — and, the author may say, for whom else (fut:scope). Content via as:content; optional target timeframe via fut:horizon / fut:horizonConcept.
scope note: gufo:SubKind of core:InformationResource. Decomposed into atomic fut:Claims via fut:articulates; the scope ladder (self→humanity) matters for convergence (unite design/03 §2).

Claim
type: Class
type: SubKind
subclass of: InformationResource
definition: An ATOMIC, voteable statement — one idea, short, standalone: the Pol.is-style unit of deliberation. Derived from a fut:VisionStatement (prov:wasDerivedFrom / the inverse of fut:articulates) or authored directly. When GenAI performs the decomposition the activity is recorded (prov:wasGeneratedBy with the model+prompt as a prov:Plan) AND the author must approve the claim before it becomes theirs — approval is fut:adoptedBy plus the claim moving into the author's pod. Nothing enters deliberation attributed to a person without that explicit adoption.
scope note: gufo:SubKind of core:InformationResource. as:content is capped at 500 characters (atomicity — futures.shacl.ttl).

Need
type: Class
type: SubKind
subclass of: InformationResource
definition: A need or want FELT BY THE AUTHOR: a link to a concept in a need scheme (fut:needConcept — the Max-Neef seed or any community scheme), free-text context via as:content, an optional 1–5 fut:intensity, and optional fut:metBy / fut:unmetBecause context. One half of the load-bearing needs/satisfiers split: convergence computes common ground at THIS layer first.
scope note: gufo:SubKind of core:InformationResource. THE class the unite Stage-1 client writes (one resource per Need under the participant's deliberation container); its required fields are the NeedShape MUSTs.

Satisfier
type: Class
type: SubKind
subclass of: InformationResource
definition: A culturally-specific WAY OF MEETING one or more needs: a proposal, practice, institution, technology or app. Linked to the fut:Need instance(s) and/or need concept(s) it serves via fut:satisfies; optionally placed on the existential axis of Max-Neef's matrix via fut:existentialCategory. The other half of the needs/satisfiers split — satisfier diversity is a feature to preserve (a portfolio of ways to meet a shared need), never noise to average away.
scope note: gufo:SubKind of core:InformationResource. People who violently disagree about satisfiers routinely share the underlying needs — the data model's convergence thesis (unite design/03 §2).

Value Statement
type: Class
type: SubKind
subclass of: InformationResource
definition: An expression that the author HOLDS a value: a link to a concept in a value scheme (fut:valueConcept — the Schwartz seed or any community scheme) plus free-text as:content. Value proximity between people whose positions differ is a documented depolarisation lever (unite design/03 §2).
scope note: gufo:SubKind of core:InformationResource. The author's own priority ordering may be carried with schema:position (not redeclared here).

Resonance
type: Class
type: SubKind
subclass of: Record
definition: The vote/endorsement primitive: a TRI-STATE reaction (fut:Resonates / fut:Conflicts / fut:Unsure — the Pol.is agree/disagree/pass pattern) to a statement (fut:onStatement → a Claim, Need, Satisfier or ValueStatement), optionally qualified by a fut:dimension (sharing a present condition vs. aspiring to it vs. willingness to support others having it — psychologically distinct signals the convergence math keeps separable). Stored in the REACTOR's pod; announced to the deliberation inbox; only ever published in aggregate (the ODRL consent layer + k-anonymity).
scope note: gufo:SubKind of core:Record. THE second class the unite Stage-1 client writes; resonances are the raw material of opinion-space mapping. Richer than as:Like (aligned Mode-A in futures-alignments.ttl).

Deliberation
type: Class
type: EventType
subclass of: Activity
definition: A SCOPED convergence exercise within a community: a titled activity with a topic, a time window, a method (fut:method → resonance-mapping / mediated-synthesis / mini-public) and a participating community. All statements and resonances entering a deliberation reference it via fut:inDeliberation.
scope note: gufo:EventType rooting in core:Activity; aligned Mode-A to prov:Activity and as:Event in futures-alignments.ttl.

Shared Future
type: Class
type: SubKind
subclass of: InformationResource
definition: The CONVERGENCE ARTIFACT: a synthesized shared-future statement. Carries the synthesis text (as:content), full derivation provenance (prov:wasDerivedFrom → every input statement, subject to each input's ODRL policy), the generating activity (prov:wasGeneratedBy, with the mediator — human WebID or GenAI agent — and its prov:Plan: GenAI mediation is NEVER invisible), per-cluster endorsement evidence (fut:bridgingEvidence — the proof this is common ground, not one cluster's position), post-synthesis endorsements (fut:endorsedBy), and a MANDATORY dissent annex: at least one fut:dissent OR an explicit fut:noDissentRecorded true. A SharedFuture without its dissent annex is INVALID (SHACL-enforced) — convergence must never mean erasure.
scope note: gufo:SubKind of core:InformationResource. Signed as a Verifiable Credential (fut:SharedFutureCredential) with a Data Integrity proof so downstream consumers can verify integrity + provenance without trusting the wire.

Shared Future Credential
type: Class
type: SubKind
subclass of: InformationResource
definition: The W3C Verifiable Credential (VC 2.0, Data Integrity proof) issued by the facilitating community over a fut:SharedFuture — the signed, wire-verifiable form handed to downstream consumers (unite Stage-3: governance reporting). Aligned Mode-A to cred:VerifiableCredential in futures-alignments.ttl; issued via the @jeswr/solid-vc proof-suite seam.
scope note: gufo:SubKind of core:InformationResource. The credential WRAPS the SharedFuture; the dissent annex travels with it.

Dissent Record
type: Class
type: SubKind
subclass of: InformationResource
definition: A FIRST-CLASS minority report attached to a synthesis: the dissenting position (as:content), the dissenting cluster/cohort in aggregate, and optionally authored dissent statements whose authors opted in. Mandatory companion of fut:SharedFuture (unite design/01; critique C1/C8 — convergence must never mean erasure).
scope note: gufo:SubKind of core:InformationResource. Attached via fut:dissent.

Bridging Evidence
type: Class
type: SubKind
subclass of: Record
definition: Per-cluster endorsement statistics for ONE opinion cluster over a statement/synthesis: the resonates / conflicts / unsure counts (and the total seen), the raw material of the bridging-based ranking (group-informed consensus across EVERY cluster, not majority preference). A SharedFuture carries one BridgingEvidence per cluster — the evidence that it is common ground.
scope note: gufo:SubKind of core:Record. Counts are k-anonymous aggregates; the unite Stage-1 client computes them as { resonates, conflicts, unsure, seen } per cluster.

Convergence Metrics
type: Class
type: SubKind
subclass of: Record
definition: The PUBLISHED aggregate for a deliberation: cluster count, cross-cluster consensus rate, bridging-score distribution and participation counts stratified by verification tier (T1 community-vouched vs. T2 ZK-personhood — unite design/02 §5: tiers are honestly labelled, never silently mixed). Open data, k-anonymous.
scope note: gufo:SubKind of core:Record.

App Proposal
type: Class
type: SubKind
subclass of: InformationResource
subclass of: wf Task
definition: A proposed Solid app in a Stage-1 co-design deliberation. Because it IS a wf:Task in the shared task model (@jeswr/solid-task-model), it federates into solid-issues and Pod Manager for free (kanban, assignment, state). MUST trace to at least one need or value via fut:motivatedBy — what keeps Stage 1 value-centric rather than feature-listing.
scope note: gufo:SubKind of core:InformationResource and ⊑ wf:Task (http://www.w3.org/2005/01/wf/flow#Task, punned above).

Spec Synthesis
type: Class
type: SubKind
subclass of: Shared Future
definition: The converged app spec handed to GenAI implementation: a fut:SharedFuture that adds acceptance criteria (fut:acceptanceCriterion), each linked back to the fut:Need it operationalises (the closing-the-loop check, unite design/05 §4), and a pointer to the implementation tracker (fut:implementationTracker → a wf:Tracker).
scope note: gufo:SubKind via fut:SharedFuture; inherits the mandatory dissent annex and bridging evidence.

Acceptance Criterion
type: Class
type: SubKind
subclass of: InformationResource
definition: One testable criterion of a fut:SpecSynthesis, linked via fut:operationalises to the fut:Need it operationalises — every criterion MUST trace to a need (SHACL-enforced), so the implemented app can be checked against the needs that motivated it.
scope note: gufo:SubKind of core:InformationResource. Criterion text via as:content.

Infrastructure Proposal
type: Class
type: SubKind
subclass of: InformationResource
subclass of: wf Task
definition: A proposed change to a shared digital system: a spec version, protocol profile, vocabulary, shared service, or governance-of-infrastructure decision. Inherits the fut:motivatedBy ≥1 requirement — infrastructure proposals stay value-centric too (what stops scope B degenerating into a feature-request tracker).
scope note: gufo:SubKind of core:InformationResource and ⊑ wf:Task like fut:AppProposal, so it federates into the shared task model unchanged.

Adoption Decision
type: Class
type: SubKind
subclass of: Shared Future
definition: A converged recommendation to adopt a spec version; ratification is MEASURED on the wire, never asserted. There is deliberately NO adoptionStatus decree property: an AdoptionDecision carries its bar (fut:adoptionBar) and its evidence (fut:adoptionEvidence), and any consumer recomputes Current/Proposed/Superseded from evidence against bar — a captured room can sign a recommendation; it cannot sign adoption.
scope note: gufo:SubKind via fut:SharedFuture: inherits the mandatory dissent annex, bridging evidence and Data-Integrity signing.

Adoption Observation
type: Class
type: SubKind
subclass of: Record
definition: One observed fedreg:acceptsSpec advertisement: who advertises which version, observed when, at which source IRI. An index entry is a cache, never authoritative (unite design/02 §2) — the observationSource is where the claim is re-checked.
scope note: gufo:SubKind of core:Record. The evidence unit fut:adoptionEvidence carries.

Critique
type: Class
type: SubKind
subclass of: InformationResource
definition: One critique in a Convergence-Room critique round (unite design/03 §4 step 2: critiques are captured AS DATA). design/01 assembles the DissentRecord FROM surviving critiques but never assigned the unit a class — v0.2.0 does. Carries as:content, fut:onStatement → the candidate synthesis, dct:created/creator, fut:inDeliberation; lives in the critic's own pod like every statement. Standing critiques at endorsement time are the raw material of the mandatory dissent annex.
scope note: gufo:SubKind of core:InformationResource. THE third class the unite client writes (S1, app/src/lib/model.ts serializeCritique); its required fields are the CritiqueShape MUSTs.

Stance
type: Class
type: Category
subclass of: Category
definition: The tri-state reaction value of a fut:Resonance: resonates / conflicts / unsure — the Pol.is agree/disagree/pass triple. A coded value (core:Category); the members are skos:Concepts in fut:stanceScheme. CLOSED for interoperability: the unite client drops a resonance carrying any other stance IRI.
scope note: gufo:Category of core:Category. 'Pass/unsure' is a first-class signal (counted in seen), distinct from 'never saw it' — the distinction the bridging smoothing depends on.

Resonance Dimension
type: Class
type: Category
subclass of: Category
definition: The optional qualifier of a fut:Resonance separating three psychologically distinct positive signals: I SHARE this (a present condition), I ASPIRE to this (a hoped-for condition), I would SUPPORT others having this (solidarity without personal stake). The convergence math wants them separable.
scope note: gufo:Category of core:Category. Members are skos:Concepts in fut:dimensionScheme.

Scope
type: Class
type: Category
subclass of: Category
definition: The scope ladder of a fut:VisionStatement — WHOM the envisioned future is for: self / household / community / nation / humanity. The ladder matters for convergence (unite design/03 §2).
scope note: gufo:Category of core:Category. Members are skos:Concepts in fut:scopeScheme.

Deliberation Method
type: Class
type: Category
subclass of: Category
definition: The convergence method a fut:Deliberation uses: resonance-mapping (Pol.is-style opinion mapping), mediated-synthesis (a human or GenAI mediator drafts syntheses — always visibly attributed), or mini-public (a sampled deliberative body).
scope note: gufo:Category of core:Category. Members are skos:Concepts in fut:methodScheme.

Need Concept
type: Class
type: Category
subclass of: Category
definition: A fundamental-human-need concept in a need scheme — the AXIOLOGICAL axis of Max-Neef's needs matrix. The seed members are the nine Max-Neef needs in fut:maxneefScheme; any community may publish its own scheme and cross-map (skos:closeMatch), so fut:needConcept accepts ANY skos:Concept, and this class types only the canonical seeds.
scope note: gufo:Category of core:Category. Needs are few, finite and universal; satisfiers vary — the load-bearing split.

Existential Category
type: Class
type: Category
subclass of: Category
definition: The EXISTENTIAL axis of Max-Neef's needs matrix: being (qualities), having (things/institutions), doing (actions), interacting (settings). Crossing the nine axiological needs with these four columns yields the matrix whose CELLS satisfiers occupy — fut:existentialCategory places a Need or Satisfier on this axis.
scope note: gufo:Category of core:Category. Members are skos:Concepts in fut:existentialScheme.

Value Concept
type: Class
type: Category
subclass of: Category
definition: A basic-value concept in a value scheme. The seed members are the ten Schwartz basic values in fut:valueScheme (a stable circumplex: adjacent values compatible, opposing values in tension — replicated across dozens of cultures), giving cluster interpretation a psychologically meaningful prior rather than an ad-hoc tag soup. Communities may publish and cross-map their own schemes.
scope note: gufo:Category of core:Category. fut:valueConcept accepts any skos:Concept; this class types the canonical seeds.

Proposal Kind
type: Class
type: Category
subclass of: Category
definition: The coded change kinds a fut:InfraProposal may carry (v0.2.0): spec change / new spec / service operation / deprecation. CLOSED for interoperability (the fedreg:status pattern): the unite client drops a proposal-kind value outside the coded set.
scope note: gufo:Category of core:Category. Members are skos:Concepts in fut:proposalKindScheme.

Stakeholder Role
type: Class
type: Category
subclass of: Category
definition: The coded stakeholder strata scope B's role-cohort lens partitions by (v0.2.0): implementers / operators / participants. Role STANDING is declared-then-verified against the public federation web and fails closed to participant (unite SCOPE-DIFFERENTIATION §3.2) — the vocabulary only records whom a change touches.
scope note: gufo:Category of core:Category. Members are skos:Concepts in fut:stakeholderRoleScheme.

expresses need
type: ObjectProperty
domain: Life Context
range: Need
definition: Relates a LifeContext to a Need it surfaces — the elicitation edge from 'my current life' to the needs felt in it.

articulates
type: ObjectProperty
type: InverseFunctionalProperty
domain: Vision Statement
range: Claim
definition: Relates a VisionStatement to an atomic Claim decomposed from it. Inverse-functional: a Claim is articulated by at most one Vision (the composition edge). GenAI decomposition is recorded via prov:wasGeneratedBy on the Claim; the Claim only becomes the author's on explicit adoption (fut:adoptedBy).

adopted by
type: ObjectProperty
domain: Claim
range: Agent
definition: The agent who explicitly ADOPTED a derived Claim as their own — the consent gate: nothing enters deliberation attributed to a person without this assertion plus the claim living in their pod.

horizon
type: DatatypeProperty
domain: Vision Statement
range: gYear
definition: The optional target YEAR of a VisionStatement's envisioned future. For a coarser, scheme-based period use fut:horizonConcept instead.

horizon concept
type: ObjectProperty
domain: Vision Statement
range: SKOS Concept
definition: The optional target timeframe of a VisionStatement as a SKOS period concept (e.g. a community's 'next generation' concept), for visions whose horizon is not a calendar year.

scope
type: ObjectProperty
domain: Vision Statement
range: Scope
definition: WHOM the envisioned future is for: self / household / community / nation / humanity (the scope ladder).

need concept
type: ObjectProperty
domain: Need
range: SKOS Concept
definition: The need-scheme concept a Need instantiates — a member of fut:maxneefScheme (the nine Max-Neef seeds) OR any community-published scheme concept. Deliberately ranges over skos:Concept, not fut:NeedConcept: no scheme is closed or centrally owned; the unite client accepts foreign concept IRIs.

intensity
type: DatatypeProperty
domain: Need
range: integer
definition: The optional felt intensity of a Need, an integer 1–5 (futures.shacl.ttl enforces the band). An ordinal self-report, never a measurement.

met by
type: DatatypeProperty
domain: Need
range: string
definition: Free-text context on HOW a Need is currently (partially) met — the author's own account, feeding satisfier elicitation.

unmet because
type: DatatypeProperty
domain: Need
range: string
definition: Free-text context on WHY a Need is unmet — the author's own account of the obstacle.

satisfies
type: ObjectProperty
domain: Satisfier
definition: Relates a Satisfier to what it meets: a fut:Need INSTANCE (someone's felt need) and/or a need CONCEPT (a scheme member). Deliberately rangeless — both targets are first-class (the needs/satisfiers split).

existential category
type: ObjectProperty
range: Existential Category
definition: Places a Need or Satisfier on the EXISTENTIAL axis of Max-Neef's matrix (being / having / doing / interacting). No rdfs:domain — it applies to both halves of the needs/satisfiers split.

value concept
type: ObjectProperty
domain: Value Statement
range: SKOS Concept
definition: The value-scheme concept a ValueStatement instantiates — a member of fut:valueScheme (the ten Schwartz seeds) OR any community-published scheme concept. Like fut:needConcept, deliberately open to foreign schemes.

on statement
type: ObjectProperty
definition: The statement a reaction is about: for a fut:Resonance a fut:Claim, fut:Need, fut:Satisfier or fut:ValueStatement; for a fut:Critique (v0.2.0) the candidate synthesis under critique. Deliberately rangeless — the union is documented here and closed per-deliberation by the aggregator, not by OWL. No rdfs:domain since v0.2.0 (the section-6 multi-class-property rule): v0.1.0 domained it onto fut:Resonance; with fut:Critique reusing it, keeping that domain would have entailed every Critique to be a Resonance.

stance
type: ObjectProperty
domain: Resonance
range: Stance
definition: The tri-state reaction of a Resonance: fut:Resonates / fut:Conflicts / fut:Unsure. Exactly one; a resonance carrying any other IRI is dropped by conforming readers.

dimension
type: ObjectProperty
domain: Resonance
range: Resonance Dimension
definition: The optional qualifier of a Resonance: fut:IShareThis / fut:IAspireToThis / fut:IWouldSupportThis — present condition vs. aspiration vs. support, kept separable for the convergence math.

in deliberation
type: ObjectProperty
range: Deliberation
definition: The Deliberation a statement or resonance enters. No rdfs:domain — every expression-layer and reaction-layer resource may carry it; the unite Stage-1 client always writes it.

method
type: ObjectProperty
domain: Deliberation
range: Deliberation Method
definition: The convergence method a Deliberation uses (resonance-mapping / mediated-synthesis / mini-public).

bridging evidence
type: ObjectProperty
domain: Shared Future
range: Bridging Evidence
definition: Relates a SharedFuture to the per-cluster endorsement statistics (one BridgingEvidence per opinion cluster) that EVIDENCE it as common ground rather than one cluster's position. At least one is mandatory (SHACL).

endorsed by
type: ObjectProperty
domain: Shared Future
range: Resonance
definition: A POST-synthesis Resonance record endorsing (or contesting — the stance is in the Resonance) a SharedFuture.

dissent
type: ObjectProperty
domain: Shared Future
range: Dissent Record
definition: The MANDATORY dissent annex of a SharedFuture: a first-class minority report. May be absent only when the synthesis explicitly asserts fut:noDissentRecorded true — a SharedFuture with neither is invalid (SHACL-enforced). Convergence must never mean erasure.

no dissent recorded
type: DatatypeProperty
domain: Shared Future
range: boolean
definition: The EXPLICIT assertion that a deliberation produced no dissent to this synthesis. Required (true) whenever a SharedFuture carries no fut:dissent — silence is never treated as consensus.

cluster label
type: DatatypeProperty
domain: Bridging Evidence
range: string
definition: The opaque label of the opinion cluster a BridgingEvidence aggregates (e.g. 'cluster-0'). A k-anonymous aggregate identifier, never a member list.

resonates count
type: DatatypeProperty
domain: Bridging Evidence
range: nonNegativeInteger
definition: How many participants in this cluster resonated with the statement/synthesis.

conflicts count
type: DatatypeProperty
domain: Bridging Evidence
range: nonNegativeInteger
definition: How many participants in this cluster conflicted with the statement/synthesis.

unsure count
type: DatatypeProperty
domain: Bridging Evidence
range: nonNegativeInteger
definition: How many participants in this cluster passed/were unsure. Counted in seen — 'unsure' is a first-class signal, distinct from never having seen the statement.

seen count
type: DatatypeProperty
domain: Bridging Evidence
range: nonNegativeInteger
definition: How many participants in this cluster SAW the statement (resonates + conflicts + unsure). The denominator of the Laplace-smoothed group-informed-consensus score.

bridging score
type: DatatypeProperty
range: decimal
definition: A group-informed-consensus score in [0,1]: the product over opinion clusters of the (Laplace-smoothed) per-cluster resonance probability — high only when a statement earns positive reception in EVERY cluster. No rdfs:domain — carried on a BridgingEvidence (per-cluster factor) or a statement/synthesis (the product).

cluster count
type: DatatypeProperty
domain: Convergence Metrics
range: nonNegativeInteger
definition: The number of opinion clusters the deliberation's resonance matrix produced.

cross-cluster consensus rate
type: DatatypeProperty
domain: Convergence Metrics
range: decimal
definition: The share of statements in [0,1] clearing the bridging threshold (minimum resonance in EVERY cluster) — the deliberation-level common-ground signal.

participant count
type: DatatypeProperty
domain: Convergence Metrics
range: nonNegativeInteger
definition: How many verified participants entered the deliberation. Report per verification tier (fut:verificationTier) — T1-only cohorts are honestly labelled, never silently mixed with stronger tiers.

verification tier
type: DatatypeProperty
domain: Convergence Metrics
range: string
definition: The personhood-verification tier a participation count refers to: 'T1' (community-vouched membership credential) or 'T2' (ZK personhood). Until a T2 provider exists nothing may claim sybil-resistance beyond the vouching community's diligence (unite decisions/0001 Q1).

motivated by
type: ObjectProperty
domain: App Proposal
definition: The fut:Need or fut:ValueStatement an AppProposal traces to. EVERY proposal must carry at least one (SHACL-enforced) — what keeps Stage-1 co-design value-centric rather than feature-listing. Deliberately rangeless: both targets are first-class.

acceptance criterion
type: ObjectProperty
domain: Spec Synthesis
range: Acceptance Criterion
definition: A testable criterion of a converged app spec. Each criterion MUST link back (fut:operationalises) to the fut:Need it operationalises — the closing-the-loop check.

operationalises
type: ObjectProperty
domain: Acceptance Criterion
range: Need
definition: The Need an AcceptanceCriterion makes testable — so the implemented app can be verified against the needs that motivated it, not just its feature list.

implementation tracker
type: ObjectProperty
domain: Spec Synthesis
definition: The task tracker (a wf:Tracker in the shared task model) where a SpecSynthesis's implementation is tracked. Rangeless — wf:Tracker is not imported into the reasoned closure (Mode A; see futures-alignments.ttl).

targets system
type: ObjectProperty
domain: Infrastructure Proposal
definition: The governed artifact being changed — an owl:Ontology version lineage, a protocol profile document, a fedreg:Registry, or a shared-service descriptor IRI. ≥1 (SHACL MUST). Deliberately rangeless: the governed surface is heterogeneous.

proposal kind
type: ObjectProperty
domain: Infrastructure Proposal
range: Proposal Kind
definition: The change kind, as a coded individual (the fedreg:status pattern): fut:SpecChange / fut:NewSpec / fut:ServiceOperation / fut:Deprecation. A non-coded value on read drops the field (closed set — conforming readers).

affects role
type: ObjectProperty
domain: Infrastructure Proposal
range: Stakeholder Role
definition: Blast radius by stakeholder role (≥1, SHACL MUST): fut:ImplementerRole / fut:OperatorRole / fut:ParticipantRole. Role STANDING is declared-then-verified against the public federation web and fails closed to participant (unite SCOPE-DIFFERENTIATION §3.2) — this property only records whom the change touches.

breaking change
type: DatatypeProperty
domain: Infrastructure Proposal
range: boolean
definition: Interop honesty: whether the change breaks running implementations. SHACL: breakingChange true ⇒ fut:migrationPath present.

migration path
type: DatatypeProperty
domain: Infrastructure Proposal
range: string
definition: The plain-language migration story a breaking change must carry.

reference implementation
type: ObjectProperty
domain: Infrastructure Proposal
definition: Running code (a repo/commit IRI). unite design/04 §2: REQUIRED before endorsement, not before compose — the endorsement-time requirement binds fut:AdoptionDecision's prov:wasDerivedFrom inputs (a cross-resource check the aggregator enforces), not drafts. Displayed as a link, never fetched/executed by the client (unite §7 security posture). Rangeless.

proposes version
type: ObjectProperty
domain: Adoption Decision
definition: The immutable owl:versionIRI the decision recommends adopting. Rangeless — the target is a version IRI of any governed artifact.

adoption bar
type: DatatypeProperty
domain: Adoption Decision
range: string
definition: The measured ratification criteria (default: unite design/04 §2 — ≥2 independent implementations + ≥2 communities advertising via fedreg:acceptsSpec).

adoption evidence
type: ObjectProperty
domain: Adoption Decision
range: Adoption Observation
definition: The observations the computed adoption status rests on.

observed party
type: ObjectProperty
domain: Adoption Observation
definition: The implementation/community whose advertisement was observed. Rangeless — implementations and communities are both first-class.

observed version
type: ObjectProperty
domain: Adoption Observation
definition: The advertised spec version IRI.

observed at
type: DatatypeProperty
domain: Adoption Observation
range: dateTime
definition: When the advertisement was observed.

observation source
type: ObjectProperty
domain: Adoption Observation
definition: The registry/storage-description IRI the observation can be re-checked against — an index entry is a cache, never authoritative (unite design/02 §2).

method provenance
type: ObjectProperty
domain: Shared Future
range: Deliberation Method
definition: Convenience mirror so a SharedFuture is self-describing about legitimacy (unite design/03 §5: anything forwarded to governance carries which method produced it): the deliberation-method concept (resonance-mapping / mediated-synthesis / mini-public). SHACL: REQUIRED on any SharedFuture whose inputs permitted fut:governmentUse — a cross-resource condition the forwarding service enforces.

decomposed by
type: ObjectProperty
domain: Claim
definition: The decomposition activity's seam-recording (unite design/03 §1), mirroring the SynthesisMediator PROV pattern for the compose-side assistant: a derived fut:Claim → the prov:Activity (with prov:hadPlan) that split it from its narrative. Either way, fut:adoptedBy is what confers authorship. Rangeless — prov:Activity is not imported into the reasoned closure (Mode A; see futures-alignments.ttl).

indirect stakeholders
type: DatatypeProperty
range: string
definition: The VSD prompt (unite design/03 §5; Friedman & Hendry, Value Sensitive Design, 2019): who is affected that is not in the room — free text on a proposal. No rdfs:domain — it applies to both fut:AppProposal and fut:InfraProposal (the section-6 multi-class-property rule). Part of the compose grammar in scopes A and B (unite SCOPE-DIFFERENTIATION §1 row 1, §3.3 step 3).

Stance scheme
type: SKOS Concept Scheme
definition: The tri-state reaction value set for fut:stance (the Pol.is agree/disagree/pass pattern). Closed for interoperability.

Resonates
type: Stance
type: SKOS Concept
in scheme: Stance scheme
notation: resonates
definition: The statement resonates with the reactor — agreement/endorsement. (IRI written verbatim by the unite client.)

Conflicts
type: Stance
type: SKOS Concept
in scheme: Stance scheme
notation: conflicts
definition: The statement conflicts with the reactor's experience or view — disagreement. (IRI written verbatim by the unite client.)

Unsure
type: Stance
type: SKOS Concept
in scheme: Stance scheme
notation: unsure
definition: The reactor saw the statement and passed — a first-class signal counted in seen, distinct from never having seen it. (IRI written verbatim by the unite client.)

Resonance Dimension scheme
type: SKOS Concept Scheme
definition: The optional qualifier value set for fut:dimension — three psychologically distinct positive signals the convergence math keeps separable.

I share this
type: Resonance Dimension
type: SKOS Concept
in scheme: Resonance Dimension scheme
notation: share
definition: The reactor shares this as a PRESENT condition of their own life. (IRI written verbatim by the unite client.)

I aspire to this
type: Resonance Dimension
type: SKOS Concept
in scheme: Resonance Dimension scheme
notation: aspire
definition: The reactor aspires to this as a hoped-for condition they do not yet have. (IRI written verbatim by the unite client.)

I would support this
type: Resonance Dimension
type: SKOS Concept
in scheme: Resonance Dimension scheme
notation: support
definition: The reactor would support OTHERS having this, without personal stake — solidarity, kept separable from sharing/aspiring. (IRI written verbatim by the unite client.)

Scope scheme
type: SKOS Concept Scheme
definition: The scope ladder for fut:scope — whom an envisioned future is for.

Self
type: Scope
type: SKOS Concept
in scheme: Scope scheme
notation: self
definition: A future for the author themself.

Household
type: Scope
type: SKOS Concept
in scheme: Scope scheme
notation: household
definition: A future for the author's household/family.

Community
type: Scope
type: SKOS Concept
in scheme: Scope scheme
notation: community
definition: A future for the author's community.

Nation
type: Scope
type: SKOS Concept
in scheme: Scope scheme
notation: nation
definition: A future for the author's nation/society.

Humanity
type: Scope
type: SKOS Concept
in scheme: Scope scheme
notation: humanity
definition: A future for humanity as a whole.

Deliberation Method scheme
type: SKOS Concept Scheme
definition: The convergence-method value set for fut:method.

Resonance mapping
type: Deliberation Method
type: SKOS Concept
in scheme: Deliberation Method scheme
notation: resonance-mapping
definition: Pol.is-style opinion-space mapping: participants react to atomic statements; clustering + bridging-based ranking surface cross-cluster common ground. The unite Stage-1 method.

Mediated synthesis
type: Deliberation Method
type: SKOS Concept
in scheme: Deliberation Method scheme
notation: mediated-synthesis
definition: A mediator (human WebID or GenAI agent — always visibly attributed via prov:wasAssociatedWith + prov:hadPlan) drafts candidate syntheses which participants then endorse or dissent from.

Mini-public
type: Deliberation Method
type: SKOS Concept
in scheme: Deliberation Method scheme
notation: mini-public
definition: A sampled deliberative body (citizens'-assembly style) deliberates on behalf of the wider community; the sample's outputs are published as syntheses with dissent.

Proposal Kind scheme
type: SKOS Concept Scheme
definition: The coded change-kind value set for fut:proposalKind (the fedreg:status pattern). Closed for interoperability.

Spec change
type: Proposal Kind
type: SKOS Concept
in scheme: Proposal Kind scheme
notation: spec-change
definition: A change to an existing spec, protocol profile or vocabulary version lineage. (IRI read verbatim by the unite client.)

New spec
type: Proposal Kind
type: SKOS Concept
in scheme: Proposal Kind scheme
notation: new-spec
definition: A wholly new spec, protocol profile or vocabulary. (IRI read verbatim by the unite client.)

Service operation
type: Proposal Kind
type: SKOS Concept
in scheme: Proposal Kind scheme
notation: service-operation
definition: An operational change to a shared service (deployment, configuration, governance-of-infrastructure). (IRI read verbatim by the unite client.)

Deprecation
type: Proposal Kind
type: SKOS Concept
in scheme: Proposal Kind scheme
notation: deprecation
definition: Retiring a spec version, profile or shared service. (IRI read verbatim by the unite client.)

Stakeholder Role scheme
type: SKOS Concept Scheme
definition: The coded stakeholder-strata value set for fut:affectsRole — the role-cohort lens scope B partitions blast radius by.

Implementer
type: Stakeholder Role
type: SKOS Concept
in scheme: Stakeholder Role scheme
notation: implementer
definition: Someone who implements the governed artifact (writes/maintains conforming code). (IRI read verbatim by the unite client.)

Operator
type: Stakeholder Role
type: SKOS Concept
in scheme: Stakeholder Role scheme
notation: operator
definition: Someone who runs an instance of the governed artifact (hosts/operates a conforming service). (IRI read verbatim by the unite client.)

Participant
type: Stakeholder Role
type: SKOS Concept
in scheme: Stakeholder Role scheme
notation: participant
definition: Someone who uses the governed artifact as an end participant — the fail-closed default standing (unite SCOPE-DIFFERENTIATION §3.2). (IRI read verbatim by the unite client.)

Max-Neef need scheme
type: SKOS Concept Scheme
definition: The AXIOLOGICAL axis of Max-Neef's needs matrix: the nine fundamental human needs — few, finite, universal and stable across cultures. The default need scheme unite seeds its pickers and validation from; communities may extend (skos:narrower) or publish their own scheme and cross-map.

Subsistence
type: Need Concept
type: SKOS Concept
in scheme: Max-Neef need scheme
notation: subsistence
definition: Physical and mental health, food, shelter, work — the need to stay alive and well.

Protection
type: Need Concept
type: SKOS Concept
in scheme: Max-Neef need scheme
notation: protection
definition: Care, safety, security, social systems that shield from harm.

Affection
type: Need Concept
type: SKOS Concept
in scheme: Max-Neef need scheme
notation: affection
definition: Friendship, family, love, intimacy — the need to care and be cared for.

Understanding
type: Need Concept
type: SKOS Concept
in scheme: Max-Neef need scheme
notation: understanding
definition: Curiosity, learning, analysis, education — the need to make sense of the world.

Participation
type: Need Concept
type: SKOS Concept
in scheme: Max-Neef need scheme
notation: participation
definition: Responsibilities, rights, work-with-others — the need to shape the decisions that shape one's life.

Idleness / leisure
type: Need Concept
type: SKOS Concept
in scheme: Max-Neef need scheme
notation: idleness
definition: Play, rest, imagination, tranquillity — the need for time that is not instrumental. (Label matches the unite client's picker.)

Creation
type: Need Concept
type: SKOS Concept
in scheme: Max-Neef need scheme
notation: creation
definition: Skills, work, invention, expression — the need to make things.

Identity
type: Need Concept
type: SKOS Concept
in scheme: Max-Neef need scheme
notation: identity
definition: Belonging, self-knowledge, groups, values — the need to be someone in particular.

Freedom
type: Need Concept
type: SKOS Concept
in scheme: Max-Neef need scheme
notation: freedom
definition: Autonomy, equal rights, dissent, self-determination — the need to choose.

Existential category scheme
type: SKOS Concept Scheme
definition: The EXISTENTIAL axis of Max-Neef's needs matrix — the four modes through which every need is experienced and satisfied. Crossing it with the nine axiological needs yields the 36-cell matrix whose cells satisfiers occupy.

Being
type: Existential Category
type: SKOS Concept
in scheme: Existential category scheme
notation: being
definition: Personal or collective QUALITIES/attributes through which a need is lived (e.g. physical health for subsistence; adaptability for protection).

Having
type: Existential Category
type: SKOS Concept
in scheme: Existential category scheme
notation: having
definition: Institutions, norms, tools and THINGS through which a need is met (e.g. food and shelter for subsistence; social security for protection).

Doing
type: Existential Category
type: SKOS Concept
in scheme: Existential category scheme
notation: doing
definition: Personal or collective ACTIONS through which a need is actualised (e.g. working, resting; cooperating, planning).

Interacting
type: Existential Category
type: SKOS Concept
in scheme: Existential category scheme
notation: interacting
definition: SETTINGS — spaces, times and milieus — in which a need is met (e.g. the living environment for subsistence; social settings for affection).

Value scheme (Schwartz)
type: SKOS Concept Scheme
definition: The default value scheme for fut:valueConcept, seeded from Schwartz's ten basic values — a stable circumplex (adjacent values compatible, opposing values in tension) replicated across dozens of cultures, giving opinion-cluster interpretation a psychologically meaningful prior.

Self-direction
type: Value Concept
type: SKOS Concept
in scheme: Value scheme (Schwartz)
notation: self-direction
definition: Independent thought and action — choosing, creating, exploring.

Stimulation
type: Value Concept
type: SKOS Concept
in scheme: Value scheme (Schwartz)
notation: stimulation
definition: Excitement, novelty and challenge in life.

Hedonism
type: Value Concept
type: SKOS Concept
in scheme: Value scheme (Schwartz)
notation: hedonism
definition: Pleasure and sensuous gratification for oneself.

Achievement
type: Value Concept
type: SKOS Concept
in scheme: Value scheme (Schwartz)
notation: achievement
definition: Personal success through demonstrating competence according to social standards.

Power
type: Value Concept
type: SKOS Concept
in scheme: Value scheme (Schwartz)
notation: power
definition: Social status and prestige; control or dominance over people and resources.

Security
type: Value Concept
type: SKOS Concept
in scheme: Value scheme (Schwartz)
notation: security
definition: Safety, harmony and stability of society, relationships and self.

Conformity
type: Value Concept
type: SKOS Concept
in scheme: Value scheme (Schwartz)
notation: conformity
definition: Restraint of actions and impulses likely to upset or harm others or violate social expectations.

Tradition
type: Value Concept
type: SKOS Concept
in scheme: Value scheme (Schwartz)
notation: tradition
definition: Respect for and commitment to the customs and ideas one's culture or religion provides.

Benevolence
type: Value Concept
type: SKOS Concept
in scheme: Value scheme (Schwartz)
notation: benevolence
definition: Preserving and enhancing the welfare of those one is in frequent personal contact with.

Universalism
type: Value Concept
type: SKOS Concept
in scheme: Value scheme (Schwartz)
notation: universalism
definition: Understanding, appreciation, tolerance and protection for the welfare of all people and of nature.

Consent action scheme
type: SKOS Concept Scheme
definition: The fut: ODRL-profile actions an author's standing consent policy permits or prohibits over an expression-layer resource.

Aggregate
type: ODRL Action
type: SKOS Concept
in scheme: Consent action scheme
notation: aggregate
definition: May be included in opinion-space mapping and convergence metrics — k-anonymous aggregate only, never individual disclosure. Permitted by default. (Profiles odrl:aggregate — see futures-alignments.ttl.)

Synthesize
type: ODRL Action
type: SKOS Concept
in scheme: Consent action scheme
notation: synthesize
definition: May be an input to a fut:SharedFuture — implies being listed in its prov:wasDerivedFrom (pseudonymously if the author is pseudonymous). Permitted by default.

Quote verbatim
type: ODRL Action
type: SKOS Concept
in scheme: Consent action scheme
notation: quote-verbatim
definition: May be quoted verbatim in a synthesis or dissent record. PROHIBITED until explicitly granted.

Government use
type: ODRL Action
type: SKOS Concept
in scheme: Consent action scheme
notation: government-use
definition: Derived artifacts may be forwarded into Stage-3 governance reporting. PROHIBITED until explicitly granted.

k-threshold
type: ODRL Left Operand
type: SKOS Concept
in scheme: Consent action scheme
notation: k-threshold
definition: ODRL left operand for the k-anonymity constraint on odrl:derive: any derived publication must aggregate at least k contributors (unite default k=5).

Futures sector
type: SKOS Concept
comment: The Futures (participatory-democracy / shared-futures deliberation) data sector. The value an app's fedapp:sector names in its Client Identifier Document to declare it operates over deliberation data — the sector the unite platform declares. Backed by this sector ontology.
preferred label: Futures