See what changed
Each accepted feature update creates another version instead of silently replacing the previous geometry.
terminode.xyz
Spatial records you can prove.
Keep the GIS and field tools your team already uses. TermiNode gives selected boundaries, zones, corridors, and event footprints a version history, audit trail, proof context, and portable evidence package.
Records
Datasets, features, versions
Evidence
Audit, receipts, checksums
Interfaces
Candid, GeoJSON, MCP, sync
Live service
ICP-hosted public MVP
The missing record
A map shows the current geometry. Reviewers often need the history behind it.
When a boundary changes, the earlier state, approval context, and related evidence can end up scattered across files and systems. TermiNode keeps the accepted spatial record readable after the map has moved on.
Inspect only what you need
Dataset, bounding-box, viewport, and paginated reads keep reviews scoped and predictable.
Take the evidence with you
Proof receipts and checksum-backed exports can be archived, handed over, or reviewed outside the DApp.
Available now
Inspect the complete public proof workflow.
The live DApp is open for technical evaluation. Start with the sample layer, follow one feature through its audit context, and export the resulting evidence.
Map and evidence
Query bounded geometry, select a feature, review its proof context, and export dataset or feature evidence.
Import and integration
Validate GeoJSON or WKB, estimate write usage, and follow Candid, TypeScript, REST/OGC, QGIS/ETL, and revision-safe sync recipes.
Read-only agent access
MCP clients can inspect datasets, versions, audit events, snapshots, partner references, and service metrics without write authority.
Where it fits
Add an evidence layer without rebuilding the systems where work happens.
TermiNode is not intended to replace ArcGIS, QGIS, Mapbox, routing, basemap, search, or field software. It sits beside those systems when a selected spatial state must remain explainable later.
For operations
Connect inspections, handovers, media references, or approvals to the zone, corridor, or asset boundary they concern.
For reviewers
Compare versions, inspect audit-safe metadata, and verify the same portable evidence package another team received.
For developers
Use canister APIs and controlled adapters to add spatial accountability to an existing product or data pipeline.
Open the live DAppInspect the ICP-hosted product surface.Inspect map evidenceFollow a public feature from bounded map query to evidence export.Read the documentationPrepare data, choose an interface, and understand production boundaries.Review use casesSee where an accountable spatial record creates operational value.Plan a pilotScope one record, one acceptance question, and one measurable outcome.Follow the roadmapSeparate live capabilities from engineering next steps.
FAQ
Short answers for technical reviewers
What is TermiNode?
A verifiable spatial evidence layer on the Internet Computer. It versions selected GIS records and exposes audit, proof, query, and export workflows.
What is a sensible first pilot?
One public-safe boundary, corridor, zone, or event footprint with a clear review question and a team responsible for accepting the result.
Does a pilot require TRMG trading?
No. TRMG is limited to product utility accounting for write and proof workflows and governance support. Trading, custody, fiat, and operator-run markets are outside the public MVP.