Existence
Identity, lifecycle, events, propagation. The minimum object that can exist reliably.
INTERACTIVE PROFESSIONAL TOPOLOGY
Not a résumé.
A system you can inspect.
One dataset. 22 records. Three views. Twenty-five years of making physical and operational systems legible to software.
Spatial is not a vertical. It is x · y · z through t — position, geometry and state evolving through time.
22 records · 4 domains · 1 method
THE OPERATING METHOD
“Find the objects, geometry, relationships and state hiding in a messy domain; write them down as an explicit, validated model; build the software around it; and keep enough evidence to say what the system knows and how it knows it.”
01PROVENANCEWhat is actually there?
→
02MODELWhat are the objects and relationships?
→
03BUILDWhat should exist?
→
04OPERATEWhat survives contact with reality?
→
05VERIFYWhat can we prove?
ONE DATASET · MULTIPLE PROJECTIONS
Kyle Knoche / professional topology
22 / 22 records visible · SHAPE-03
SELECT inspect a record · R04 R05 R06 R07 run live models · R23 case file ↗ · nodes stay compact; evidence lives in the inspector
NEW CASE FILE · R23 · INDEPENDENT WORK
The same method,
on a public portal.
Cognitive Wall read NAPSG Foundation's public ArcGIS Online organization anonymously and compiled it into evidence-bearing topology. Not a mockup: the live model replays the real run, request by request.
4,861requests8,513nodes20,035relationships754declared gaps
Open the case file ↗
THE THROUGH-LINE
Physical systems have always been data systems.
UAV telemetry and video. LiDAR-corrected rail geometry. Hydrologic time series. Methane sensors. Electric grids. Public-safety state. The domain changes; the architectural problem repeats: establish the objects, contracts, relationships, lineage and tests that let software reason about the real world.
XYZ
TTIME
state evolving through time →
PROVENANCE AS ARCHITECTURE
Prompt engineering asks.
Provenance engineering constrains the world.
Capability
Reusable controls, connections, lists, maps, trees and known object topology.
Specialization
AI works inside the inherited system instead of recreating architecture on every pass.
The repository becomes executable provenance: names, relationships, standards, decisions, constraints and tests survive the conversation that created them.