One of four canonical Civic.Social specifications, and the interactive unit of the model. Defines structured, stateful civic processes — voting, participatory budgeting, deliberation — that enable participation between citizens, organizations and institutions. Specifies a process lifecycle (canonical vocabulary plus lifecycle profiles), identity, eligibility and disclosure requirements, integration with the Civic Activity model, and interface contracts for creation, descriptors and actions. A process type is implemented and distributed as a Civic Process Plugin, registered with a host space's process registry; this specification defines the contract a plugin implements, while the companion Civic Plugin Architecture defines how it is packaged, scoped and installed.
LicenseDocumentation only under CC-BY 4.0 — free to reuse and adapt with attribution. No implementation code, licence for implementations, or reference implementation is present in this repository
Dev Status 📝 Draft
OwnerCivic.Social — 501(c)(3) nonprofit civic technology initiative; documentation published through the Mosaic Foundation GitHub organization. Individual specifications carry a named document owner in YAML frontmatter
Governing BodyCivic.Social (501(c)(3) nonprofit) — single-organization specification authorship; individual documents carry one named owner in frontmatter. No external standards body, multi-stakeholder process or independent editorial board
CountryUnited States (Civic.Social is a 501(c)(3), a US federal tax designation; specific location not published in the repository)
Start Year 2026
StackLanguage-agnostic specification; no implementation stack defined in the documentation
FundingNonprofit — Civic.Social is a 501(c)(3); no specific funder or grant disclosed in the repository. The repository contains case materials explicitly directed at funders and partners
OriginsCivic technology / participatory democracy — motivated by the need for a standard, interoperable model for structured civic participation so that processes are portable across host spaces rather than bound to a single platform
DatabaseN/A — a specification; defines no storage layer
Query LanguageN/A — no query language defined in the documentation reviewed
Data FormatsProcess descriptors, action contracts and lifecycle state, integrated with the Civic Activity model; the specification uses RFC 2119 conformance language throughout. Full serialization detail not extracted from the specification
Collaborative Live EditingN/A — specification, not an editing surface
Rich Text EditingN/A — specification
Mobile SupportN/A — specification; client support is a matter for implementations
Web SupportN/A — specification; no implementation exists to assess
Native AppsN/A — specification
TermsFree / open documentation under CC-BY 4.0; no fees and no registration
FundsUnknown — no figures published
Based OnCivic.Social canonical specification set (Civic Space as host, Civic Activity for the emitted activity model, Civic Identity for eligibility and disclosure); Civic Plugin Architecture (companion document governing packaging and installation); RFC 2119 conformance language
Semantic Web CompatibilityIndirect — the specification integrates with the Civic Activity model, which the specifications index describes as designed for ActivityStreams 2.0 representability. ActivityStreams 2.0 is JSON-LD based, so process-emitted activities are plausibly RDF-interpretable; the process contract itself is not described as RDF-native
Protocol Maturity / StandardizationWorking draft (v0.2, frontmatter status 'review') — single-organization specification with no standards-body involvement, no conformance suite and no independent implementation. RFC 2119 conformance language is used throughout, which is more discipline than most early drafts show. Refinement is planned through pilot implementations rather than through a standards process
Vocabulary / Ontology TypeCivic participation process — a domain-specific vocabulary covering process lifecycle states, eligibility and disclosure requirements, and action contracts for structured participation formats such as voting, budgeting and deliberation. Not a general-purpose vocabulary
Usage PatternEmbedded in other protocols and applications — the specification defines a contract implemented by Civic Process Plugins, which are registered with a host Civic Space's process registry. It is explicitly a companion to the Civic Plugin Architecture, which governs packaging, scoping and installation
See something missing or that could be improved? Let us know →