Home
A governed, evidence-first, map-first, time-aware spatial knowledge system for Kansas and the surrounding frontier.
Kansas Frontier Matrix (KFM) is designed to make spatial and historical knowledge useful without hiding where it came from, what it means, what may be shown, or how it can be corrected. It brings together domain data, maps, time, evidence, policy, review, and release controls around a common goal: the inspectable claim.
Important
This wiki is an orientation surface. Canonical repository evidence, adopted KFM doctrine and ADRs, contracts, schemas, policy, tests, lifecycle records, and release decisions outrank wiki prose. A wiki page is not implementation, approval, release, or data-publication evidence.
| Reader goal | Wiki page | Canonical repository entry point |
|---|---|---|
| Understand KFM in ten minutes | Architecture | Repository README |
| Set up a development environment | Getting Started | Contributing guide |
| See what is actually present now | Project Status | Current main tree and current checks |
| Learn where files belong | Repository Map | Directory Rules |
| Understand evidence and trust | Governance and Evidence | Doctrine index |
| Browse Kansas knowledge lanes | Domains | Domain index |
| Understand maps and AI | Map, UI, and AI | Explorer Web and Governed API |
| Contribute safely | Contributing | CONTRIBUTING.md |
| Maintain this wiki | Wiki Maintenance | docs/wiki/README.md |
KFM connects source material to public-safe products through an explicit lifecycle:
RAW -> WORK / QUARANTINE -> PROCESSED -> CATALOG / TRIPLETS -> PUBLISHED
Promotion is a governed state transition, not a file move. Public clients use governed APIs and released public-safe artifacts rather than canonical or internal stores. Consequential claims resolve EvidenceRef -> EvidenceBundle; when support is missing or unsafe, the system abstains, denies, holds, or reports an error.
Maps, tiles, graph projections, indexes, dashboards, screenshots, stories, 3D scenes, and AI responses are downstream carriers. They do not become sovereign truth merely because they render successfully.
- Place: a map-first operating surface centered on Kansas.
- Time: observations, source versions, valid periods, releases, corrections, and supersession.
- Evidence: resolvable source and support chains for consequential claims.
- Domains: hydrology, soil, ecology, geology, atmosphere, infrastructure, history, archaeology, agriculture, people, and more.
- Governance: source roles, rights, sensitivity, policy, review, promotion, correction, and rollback.
- Delivery: governed APIs, public-safe geospatial artifacts, Evidence Drawer views, and bounded Focus Mode interpretation.
- Reversibility: auditable changes, deterministic identity where practical, correction lineage, and rollback targets.
Trust-bearing runtime surfaces converge on four outward states:
| Outcome | Meaning |
|---|---|
ANSWER |
Released, policy-safe, evidence-supported response |
ABSTAIN |
Evidence is missing, stale, conflicting, or outside the supported scope |
DENY |
Rights, sensitivity, role, release state, or exposure risk blocks the response |
ERROR |
A validator, resolver, adapter, policy service, or runtime failed safely |
Negative states are first-class behavior. The system should never turn uncertainty into a confident answer merely to keep the interface moving.
KFM is a large, actively evolving repository with real documentation, application, schema, policy, test, pipeline, data-lifecycle, and release-supporting surfaces. Maturity is uneven and must be assessed claim by claim. File presence does not prove deployment, full validation, rights clearance, release readiness, or publication.
The source set for this wiki was authored against main@391e05b13600bda01b243bb97a0156002d73f0b7. Always inspect the current branch, files, tests, workflow runs, and emitted artifacts before relying on a current-behavior claim.