// evidence ledger · /claims
Every claim has a receipt.
This page is the site-owned review surface for public messaging. Each major claim category maps to shipped source evidence, preview proof, a scoped caveat, or an owner ticket — before broad outreach.
OGC API Features
137 / 137
CITE snapshot · passing
OGC API Tiles · WMS · WMTS
275 / 275
16 + 199 + 60 passing
WFS 1.0 · 1.1
201 / 201
162 + 39 passing
GeoServices REST
partial
per-service gaps tracked
// status vocabulary
How status labels are used.
Source-backed
Claim can be stated as Preview-current when linked evidence supports the exact scope.
Preview partial
Claim can be marketed for evaluation, but partial parity and caveats must stay visible.
Proof pending
Claim may be described as a Preview target, not as validated or generally available.
Roadmap / Beta
Claim belongs to Beta, named pilot, or later roadmap scope.
Deferred
Claim must not be marketed as Preview-ready.
External owner
Release gap belongs to another repo; this site only links the owner ticket or source.
// claims by area
Major public claims and allowed wording.
The public pages can stay forceful where the evidence is exact. Anything proof-pending, Beta, externally owned, or deferred uses the softer wording rule below.
| Claim area | Public wording rule | Status | Evidence / owner |
|---|---|---|---|
| Runtime & single-binary platform | Say the documented compatibility and gRPC surfaces run from one runtime. Do not imply every roadmap capability is GA. | Source-backed Partial | PLATFORM.md |
| OGC & standards conformance counts | Use exact counts only where the CITE evidence snapshot says the same. Do not claim formal OGC certification. Allowed exact counts: OGC API Features 137/137, OGC API Tiles 16/16, WMS 1.3 199/199, WMTS 1.0 60/60, WFS 1.0 162/162, WFS 1.1 39/39. | Source-backed | MVP compatibility contract |
| GeoServices REST · ArcGIS · GeoServer compatibility | Say supported with partial parity. Preserve gaps for FeatureServer, MapServer, ImageServer, Geometry Service, and GPServer. | Preview partial | Parity doc |
| Migration wedge & cutover automation | Say scoped migration evidence exists for supported source families, parity checks, and measured migration-performance fixtures. Keep cutover, SDK-driven migration, and ArcPy/Python GP caveats visible until those release artifacts are attached. | Preview partial | Compatibility & migration evidence |
| gRPC & SDKs | Describe typed protocol and SDK examples as Preview/alpha-aware. Do not imply all SDK families ship stable production packages. | Preview partial | SDK compatibility matrix |
| MCP & AI agent surface | Limit claims to discovery/listing, schema inspection, filtered queries/statistics where supported, and bounded spatial tools. Do not claim completed certification. | Preview partial | geospatial-mcp |
| QGIS plugin | Describe Honua GIS Assistant as a 0.1.0 early-preview, GPL-2.0-or-later QGIS plugin for private/local assisted workflows with local Ollama chat, audit JSONL, default-off remote endpoint settings, and a bounded query bridge. Keep release ZIP, marketplace approval, screenshots, and demo video marked pending until those artifacts ship. Preserve local-first, no-account, no-telemetry defaults. Do not claim QGIS project endorsement or certification. | Preview partial External owner | honua-qgis-plugin |
| Honua-GIS model/eval track | Say Honua-GIS is an open-weights GIS model/eval track with a published benchmark dataset, eval harness, model-card scaffold, and GGUF/Ollama workflow. Do not claim released fine-tuned weights, quality improvements, an Ollama pull tag, a NIM image/endpoint, or production readiness until honua-gis-llm publishes exact artifacts. | Source-backed Proof pending External owner | honua-gis.html · baseline runbooks · live baseline gate · NIM smoke gate |
| Mobile · field · offline · MAUI | Label as Beta or pilot-scoped. Do not present offline sync, conflict handling, or device workflows as Preview-ready. | Roadmap / Beta | honua-mobile |
| Deployment & AI DevOps loop | Terraform and OTel can be stated as Preview today. AI DevOps loop (alert → triage → PR) must be labeled private beta until shipped. | Source-backed Beta | honua-terraform |
| Performance benchmarks | Benchmark claims may cite published GeoBench snapshots when linked and scoped to the snapshot; future proof-hub assets stay pending. | Proof pending | geobench |
| Commercial tiers & pricing | Honua Server is ELv2; SDKs are Apache 2.0. Pro and Enterprise tiers use enterpriseready.io as a capability baseline; describe pricing as "shaped in the open" until tiers are real. | Source-backed In design | open-core.html |
// evidence bar
Self-imposed rules for everything above.
01 · Exact numbers
Use specific counts only where a CITE snapshot, parity JSON, or test artifact says the same number.
02 · Partial parity stays partial
Never describe GeoServices REST coverage as "100% parity" or "drop-in for everything." Gaps stay tracked in the matrix.
03 · No unconditional cutover
"Cut over when ready" / "clients keep working" need an attached parity run for the target estate.
04 · Roadmap labels stay visible
Beta, pilot-scoped, private-beta, and proof-pending labels stay on every page where the underlying claim sits.
05 · External owner = link
If another repo owns the gap, link the owner ticket. Don't restate the work as if it ships from this site.
06 · Examples are examples
Terminal sessions, transcripts, and code diffs that are illustrative get labeled "example" — not "live run."
07 · Benchmarks travel with methodology
Performance numbers cite the GeoBench snapshot or stay shape-only with the methodology linked.
08 · Pricing TBD stays TBD
Until commercial tiers are real, this site says "shaped in the open" — never invents a number.