Service Statuses

Created: 2026-05-12 · 6 concepts

https://ontology.global.church/core#ServiceStatusScheme

Lifecycle status of a gc:OfferedService: Active (production-ready), Beta (publicly callable but stability not guaranteed), Deprecated (still functional but scheduled for removal), Retired (no longer reachable), Planned (announced, not yet shipped), Maintenance (temporarily unavailable). Required 1..1 on every OfferedService.

Code	Label	Definition
`SST-ACT`	Active	Production-ready service. The offering org commits to current interface stability and to the auth + rate-limit contract documented at gc:hasServiceInterface.
`SST-BETA`	Beta	Publicly callable but contract stability is not guaranteed. The offering org may break compatibility with notice. Suitable for early-integrator partners willing to absorb churn.
`SST-DEP`	Deprecated	Still functional but scheduled for removal. Consumers should migrate to the replacement service (typically named in gc:rateLimit or rdfs:comment until a structured successor property is added). Compatible with gc:validUntil on the ServiceOffering association.
`SST-MNT`	Maintenance	Temporarily unavailable for planned maintenance, infrastructure migration, or incident remediation. Distinct from Retired — the offering org intends to restore availability.
`SST-PLN`	Planned	Announced but not yet shipped. Use for forthcoming services where the design surface is stable enough to model (interface type, capability invocation, target endpoint) but the endpoint is not yet callable. Pair with rdfs:comment naming the expected ship window.
`SST-RET`	Retired	Service is no longer reachable. The OfferedService record is retained for historical traceability — past attestations, dependency-graph queries, and provenance records may still reference it.