3 knowledge units
Dedicated logging, audit, and evidence planeEach SaaS can maintain a separate logging/compliance database for append-oriented record changes, AI retrieval evidence, authorization context, custom-service events, and integrity-chain data.Domains, API clients, backups, integrations, and asynchronous operationsBuilder-facing domain, credential, backup, and integration changes use scoped stored procedures/services; long-running verification and execution work is asynchronous.Stripe and billing source-of-truth boundariesBuildWithHQ reconciles Stripe payment/subscription state into SQL for entitlements and display while treating Stripe as authoritative for external payment objects and keeping end-SaaS billing separate from platform billing.