insigz docs
Product Spec

Product Specification

The full product spec — every feature, surface, and agent in insigz, chapter by chapter.

A complete specification of every feature, function, and surface in insigz. Each chapter is self-contained and cross-references the others — read in order for the full mental model, or jump to the area you're working on.

Product in one line: insigz is a geospatial intelligence-fusion platform — it connects live and documentary data sources into one canonical, queryable model of the world, lets an analyst investigate it on a map with a citation-grounded AI analyst, and (optionally) turns the same world model into a multiplayer war-game. It runs as single-tenant instances managed from a platform-owner control plane.

Chapters

ChapterCovers
Product OverviewWhat insigz is · the three-layer mental model · operating modes · blueprints · personas
The Canonical ModelThe Source→Observation→Entity→Event→Case→Report pipeline · Observation schema · entity resolution · framework lineage
App ArchitectureThe SPA shell · full route map · theme system · shared state primitives · the Projects layer
App SurfacesEvery app screen in detail (Overview, Explore, Sources, Cases, Reports, Sessions, Workshop, AAR, detail views)
Agents & the Analyst ChatThe analyst chat · prompt library · in-chat action widgets · chat projects & history · the agent roster
The Ontology AgentSource onboarding — the staged wizard · Observation schema contract · entity-resolution rules · the Q9 gate
The Wargame ExtensionSessions · cells · phased turns · Workshop editors · Adjudicator / Inject / After-Action agents · AAR
Settings & AdminOrganization & project settings sub-routes, including the Security posture configure flows
Notifications & UXAlert model & inbox · the toast/status system · merge-review · responsive & dead-end-closure patterns
The Marketing WebsiteEvery public website page, section by section
Design SystemTokens · type · color · spacing · component vocabulary
Doctrine & BoundaryThe Q1–Q10 doctrine principles · what's real vs. simulated · development roadmap
The Autonomy LayerWatches · Proposal Inbox · Trust Evals · Analyst Studio · the DataLayer seam · Q10
The Entity NetworkThe network surface · the graph-data seam · 3D force layout · community & centrality · grounded / suggested ties
Pattern of LifeBaseline bands · robust-z anomaly scoring · brush / inspect · the hand-off to Standing Watches
Experience ArchitectureThe chat-first journey · verbs-in-chat / nouns-on-canvas · the widget engine · the six-step journey rail
The Control Planeinsigz Control — the platform-owner console: fleet · tenants · provisioning · billing · audit · RBAC + break-glass

For the build manual — backend, data layer, AI/RAG, security, and Google Cloud deployment — see Engineering.

Glossary

  • Organization / tenant — the top isolation boundary (billing, KMS keys, connector catalog).
  • Project — one focused theatre of work inside an org; owns its sources, surfaces, members.
  • Surface — an individual work screen (Overview, Explore, Cases, …) toggled per project.
  • Source — a connected external feed (AIS, OFAC, PubMed, …).
  • Observation — one atomic, timestamped, signed, sourced fact. The unit the AI is grounded on.
  • Entity — a thing observations are about (vessel, cable, org, channel).
  • Event — a change in entity state fused from observations.
  • Case — an investigation binding events + entities + a hypothesis.
  • Report — a signed, shareable deliverable.
  • Session — a multiplayer war-game run (wargame extension).
  • AsOf — the time-pinning control: replay the world as it looked at a past moment.
  • Q1–Q10 — the doctrine principles that shape the UX (see Doctrine & Boundary).
  • Control plane — the platform-owner console that spans all tenants: provisioning, billing, support, observability, audit. The customer-facing app is the data plane.
  • Break-glass — an operator's scoped, time-boxed, reason-required, logged entry into a customer's live instance.

On this page