Engineering
The build-out spec — stores, agents, RLS, deployment, contracts.
Engineering spec
The full engineering build manual — chapters 01 through 83 — is now in this section (sidebar, left): system architecture, data stores, the canonical model, entity resolution, agent architecture, RAG and Claude integration, auth and tenant isolation, GCP deployment, CI/CD, the API and realtime surfaces, RLS policies, and the OpenAPI inventory. The product-level spec (what insigz is, surface by surface) lives under Product Spec.
These chapters describe how to build the platform for real. Where the spec and the shipped code diverge, the docs describe what is built, with a clearly-marked note for what is planned.
Decisions of record
- Hybrid stack — Payload business plane + raw-SQL data plane on one Postgres.
- Shared DB + RLS first — project-per-tenant GCP silo is a later sovereign tier.
- TypeScript end-to-end — heavy work pushed into Postgres extensions; no Python in the core.
- Three repos —
insigz-app,insigz-ai,insigz-docs.
See Architecture for the design these decisions produce.
The Control Plane — insigz Control (platform-owner console)
The backstage console platform owners use to run the fleet of single-tenant instances, handling provisioning, billing, support, and maintenance.
Build Milestones (the sequence Claude Code executes)
Vertical slices in priority order; each milestone is end-to-end shippable, built fully before the next, driven by the first customer use case.