Koine ships with 11 numbered specifications covering every layer of the product. Each one is the contract — the code is downstream of the docs, not the other way around.
Why Koine exists. The three peer surfaces. Twelve load-bearing principles.
Three layers, three entry paths. Trust boundaries. Read + write request lifecycles.
Bidirectional Connector interface. Portable + raw queries. Dry-run contract. Conformance suite.
Tier 1 / 2 / 3 classification. Dry-run + two-party approval. Subscription-bounded capacity.
Definition format. Authoring flow. Change log. Sub-tools + pipelines.
Four-tier composer. Golden Set evaluations. Per-locale versioning.
RBAC × capabilities. ContextFacts. PII. Audit streams. Residency. Incident response.
Three localisation dimensions. EN / FR / PT day-one. RTL-ready. Domain Vocabulary.
Template shape. Data binding. Rendering. Distribution. AI-narrative opt-in.
HTTP surface. Three entry paths. Error envelope. Versioning + deprecation.
Managed / Dedicated / Self-hosted. Residency. SLAs. Portability guarantee.
Extends the base specs for spatial workloads — census, CRVS geocoding, PostGIS, ArcGIS.
The specs live in the apps/koine/docs/ tree. Customers on Enterprise get source access; everyone gets HTML renderings on request.
Machine-readable OpenAPI 3.1 at /api/v1/openapi.json. Try an authenticated call:
curl -H "Authorization: Bearer <key>" \ https://koine.worksiapps.com/api/v1/admin/me/permissions/