Canary is a store operations platform for independent specialty retailers — the kind running NCR Counterpoint or RapidPOS, one to thirty locations, owner-operator. It sits above the POS and connects inventory, receiving, replenishment, and task management to the intelligence layer those merchants have never had access to. The platform enforces three accountability rails that don't exist in any off-the-shelf retail software: Operational (no unknown inventory loss), Financial (L402-gated open-to-buy), and Evidentiary (cryptographic hash-anchoring on every state-mutating event). This is the Go implementation — 29 services, GCP, ARTS-native data model, built for the RapidPOS channel.
Rail 1
Operational
No unknown inventory loss. Every receiving, transfer, and adjustment is reconciled before it clears the store ledger.
Rail 2
Financial
L402-gated open-to-buy. Purchase authority is metered and enforced at the protocol level — the budget is provable, not just promised.
Rail 3
Evidentiary
Every state-mutating event is hash-anchored and cryptographically sealed. The audit trail is not a log — it's a ledger.
Design Documents — Reading Order
- 01Platform OverviewWhat Canary is, who it serves, and why the three accountability rails matter
- 02ArchitectureService topology: 29 modules, Chi HTTP, pgx, Valkey streams
- 03Go Module LayoutRead this before touching any file — repo structure, naming, service boundaries
- 04Canonical Data ModelARTS-anchored, SMB-2030 scoped, GSLM provenance — the master data contract
- 05IdentityMerchant identity, tenant model, API key auth, federated identity path
- 06Webhook PipelineHMAC-validated event ingestion gateway — Node 2 of the protocol pipeline
- 07TSPTransaction Stream Processor: hash-seal → parse-route → Merkle-ordinal pipeline
- 08Chirp Detection Engine37 detection rules, threshold tuning, alert routing
- 09MCP Service Junctions26 MCP tools across 7 modules — the agent interface to the platform
- 10DriftPOS IntegrationWire protocol between Canary and RapidPOS (CAN-DESIGN-001)
- 11Landed Cost RollupGo types, DB schema, calibration, and settlement for per-event metered billing
- 12Microservice ArchitectureInter-service communication contracts, event schemas, error handling conventions