Product library / Technical operations

Technology and operating register

The authoritative operating map for where the company’s systems live, what data they own, how changes reach production, which controls protect them and which decisions remain unresolved. This register stores operational facts and ownership—not passwords, private keys or secret values.

Control rule0Secrets stored in this website

Registered systems81 confirmed live in this register

Tier 1 systems3Require recovery and incident ownership

API partners11Planned or approved integrations

Critical decisions3P0 confirmations required

Traceable

Every live URL resolves to a source repository, branch, environment, deployment artifact and accountable owner.

Canonical

Every data domain has one source of truth. Integrations project or reconcile records instead of becoming accidental masters.

Recoverable

Tier 1 systems have an owner, monitoring, rollback, backup, restoration and incident path before external reliance.

Secret-safe

The register stores vault references, custodians and review dates only—never keys, passwords, tokens or recovery codes.

Architecture register

Technology layers and purpose

Confirmed targets, current direction and unmade decisions are deliberately distinguished. “Planned” never implies that an account, integration or production control exists.

Web applicationCurrent direction

React, TypeScript and a Next-compatible application architecture

One responsive Admin, Designer, Provider and Client product using the Registry Component System

Production backendConfirmed target

Supabase

Managed PostgreSQL, Auth, Storage, Realtime, Row Level Security and Edge Functions

Canonical databaseConfirmed target

PostgreSQL

Multi-Workspace Projects, Entities, relationships, workflow, audit, commercial and operational records

AuthenticationPartially implemented

Supabase Auth

Email/password, Google OAuth, sessions, verification and recovery; authorization remains application- and RLS-owned

File storageConfirmed target

Supabase Storage

Permission-scoped files, images, evidence and document versions with database metadata

Server workflowsArchitecture target

Supabase Edge Functions, database events and durable job patterns

Privileged commands, webhooks, outbox delivery, reconciliation and asynchronous AI/integration work

Transactional emailPlanned

Resend

Invitations, notifications, approvals, receipts and system-generated email

Calling and messagingPlanned

Twilio

SMS, calling, purchased numbers, voicemail, recordings and call transcripts

PaymentsPlanned

Stripe

Payment collection, settlement status, refunds and financial event handling

AccountingPlanned

QuickBooks Online

Accounting ledger synchronization, reconciliation and financial reporting

ProductivityPlanned

Google Workspace

Gmail, Calendar, Sheets and selected Drive-connected workflows

AIPlanned

OpenAI API

Document extraction, writing assistance, item enrichment, classification, summaries and Project presentation generation

ObservabilityDecision required

Structured logs, error tracking, metrics and alerting provider to be selected

Release health, incidents, webhook failures, job backlogs, security events and service-level reporting

Internal business hubLive

Sites / Cloudflare-compatible deployment

Living business plan, product specifications, roadmaps, operating registers and company knowledge

System-of-record register

Products, hosting and delivery ownership

This is the operating inventory. Unknown facts are risks to resolve, not blanks to hide.

System	Criticality	Repository and hosting	Deployment and environments	Owner	Status
Design Registry productProduction CRM, Project operating system and network platform	Tier 1	Product repository and default branch need confirmationProduction host and deployment provider need confirmation	Release, preview, rollback and migration workflow need confirmationProduction URL confirmed; local, preview and staging topology need confirmation	Technical owner required	Needs confirmation
Public websiteMarketing, acquisition, Designer signup and Provider applications	Tier 2	Website repository and source branch need confirmationChatGPT Sites URL confirmed; final production domain pending	Published site confirmed; source-to-production workflow needs confirmationCurrent published environment confirmed; preview strategy needs confirmation	Business and technical owners required	Partial
Business operations hubPrivate company knowledge, living specifications, product audit and roadmap	Tier 2	Private Sites source repository; main branch; local internal-site working copyPrivate ChatGPT Sites deployment with Cloudflare-compatible runtime	Validated vinext build → committed source → saved Sites version → private production publishLocal development and private production confirmed; business.design-registry.com pending	Brad Mitchell	Live
SupabaseIntended production PostgreSQL, Auth, Storage, Realtime and server-side workflows	Tier 1	Database migrations and generated types must live with the product repositorySupabase managed	Migration, Edge Function, rollback and seed-data workflow need confirmationProduction target confirmed; project references and non-production separation need confirmation	Technical and data owners required	Architecture confirmed
ResendTransactional email and editable notification delivery	Tier 2	Templates and integration code belong to the product repositoryResend managed	Keys, sending domains, webhook endpoints and suppression handling by environmentAccounts, domains and ownership need confirmation	Communications integration owner required	Planned
TwilioSMS, calling, purchased numbers, voicemail, recordings and transcripts	Tier 2	Communication orchestration and webhook code belong to the product repositoryTwilio managed	API keys, subaccounts, numbers, webhook URLs and recording policy by environmentAccount and subaccount strategy needs confirmation	Communications integration owner required	Planned
StripePayments, refunds, processor settlement and financial events	Tier 1	Payment commands, webhook handlers and reconciliation jobs belong to the product repositoryStripe managed	Test/live keys, signed webhooks and product/account mappings by environmentTest and live account structure needs confirmation	Finance and technical owners required	Planned
QuickBooks OnlineAccounting ledger synchronization and financial reconciliation	Tier 2	Accounting mappings, sync and reconciliation logic belong to the product repositoryIntuit managed	OAuth application, callback, company mapping and disconnect behavior by environmentSandbox and production company setup needs confirmation	Finance and technical owners required	Planned

Environment model

Where changes are allowed to run

Environment separation includes data, domains, storage, OAuth clients, webhooks, secrets and external-provider accounts—not only application URLs.

01Required; exact product setup needs confirmation

Local development

Individual implementation and rapid validation using non-production configuration and synthetic data.

Data: Synthetic or explicitly sanitized fixtures only
Access: Approved developers on managed devices
Promotion rule: Changes move through reviewed source control; local state is never promoted directly

02Required; provider and project topology needs confirmation

Preview

One isolated deployment per change for product, design and QA review before merge or release.

Data: Synthetic or approved test dataset
Access: Team-only or explicit reviewer allowlist
Promotion rule: Built from an identified commit; never shares production secrets or callback URLs

03Required before external portals and payments

Staging

Production-like release rehearsal for migrations, integrations, permissions and end-to-end workflows.

Data: Synthetic production-shaped data; no uncontrolled production copy
Access: Restricted product, engineering and QA
Promotion rule: Same migration and build artifacts intended for production

04Platform and public URLs exist; operating controls need confirmation

Production

Real Designer, Provider, Client and Registry operations.

Data: Authoritative live business and customer records
Access: Least privilege, MFA and audited emergency access
Promotion rule: Approved release with migration, monitoring and rollback plan

Data ownership

Canonical domains and boundaries

Classification follows the data into exports, files, AI prompts and integrations. A lower-risk system does not reduce the classification of the data it receives.

Domain	Authoritative source	Classification	Authorized consumers	Retention basis	Primary control
Identity and access	Supabase Auth plus application User, Membership and permission records	Restricted	Every authenticated surface	Account, legal and security policy	RLS, server authorization, MFA and security audit
Workspace and Entities	Canonical PostgreSQL records	Confidential	Admin, Designer, Provider and Client projections	Active relationship plus governed history	Workspace boundary, field visibility and immutable identifiers
Projects and operations	Canonical Project service and related domain records	Confidential	Project participants and authorized Registry operators	Project lifecycle plus contractual/legal period	Project grants, role scopes, versioning and Activity/Audit
Commercial and financial	Registry commercial records; Stripe processing; QuickBooks accounting projection	Highly restricted	Authorized owners, finance and scoped participants	Tax, accounting, contract and payment policy	Field-level permissions, segregation of duties and reconciliation
Communications	Registry Conversation records plus Resend, Twilio and authorized Gmail projections	Restricted	Thread participants and authorized operators	Channel, consent and legal policy	Participant visibility, internal-note separation, consent and redaction
Files and evidence	Storage objects plus versioned PostgreSQL metadata	Varies by file	Authorized record participants	Record type, approval, contract and legal-hold policy	Signed access, malware checks, versioning and download audit
AI inputs and outputs	Permission-filtered Registry context and approved provider responses	Inherited from source	Initiating user and approved workflow	Purpose-specific and minimized	Server-side keys, source citations, human review and no-training policy confirmation

Release operations

One production delivery standard

The same traceable release logic applies whether the product ultimately uses Sites, a conventional host, Supabase migrations or external integration configuration.

Plan

Name the owner, affected systems, data, migration, feature flag, risk and acceptance evidence.

Review

Review source changes, dependency/security impact, permissions, migration and rollback before merge.

Validate

Build the exact commit and run automated plus audience-specific workflow tests in a safe environment.

Release

Promote an identified artifact and migration set through the approved production path.

Observe

Watch errors, latency, jobs, webhooks and business-critical outcomes during the release window.

Record

Store the deployed version, approver, result, exceptions and rollback outcome in release history.

Control register

Production safeguards and evidence

A control is not complete because it is written here. Its named evidence must exist and be reviewable.

Control	Requirement	Required evidence	Cadence	Owner	Status
Source and release traceability	Every deployment identifies repository, branch, commit, build artifact, migration set, approver and production result.	Release record and deployment history	Every release	Technical owner	Partial
Environment separation	Domains, databases, storage, OAuth clients, webhook endpoints and secrets remain distinct by environment.	Environment register and configuration review	Quarterly and on change	Technical owner	Needs confirmation
Secrets management	No secrets in source, this hub, browser bundles or logs; store values in an approved secret manager with owner and rotation metadata.	Secret inventory without values	Quarterly	Security owner	Decision required
Authorization and RLS	Server authorization and Row Level Security enforce Workspace, Project, record and field boundaries independently of UI state.	Policy tests for Admin, Designer, Provider and Client fixtures	Every protected release	Security and data owners	Planned
Backup and restoration	Databases, storage metadata and critical configuration have documented recovery objectives and a tested restore procedure.	Successful restore exercise	At least quarterly	Data owner	Needs confirmation
Observability and alerting	Errors, latency, webhook failures, job backlogs, security events and business-critical workflow failures reach an accountable responder.	Dashboards, alert routes and response history	Continuous	Technical owner	Decision required
Integration reconciliation	Every external event is signed, deduplicated, retryable and reconciled to the canonical Registry record.	Webhook audit, retry queue and reconciliation report	Continuous and daily summary	Integration owner	Planned
Access review	Production, provider-console, source and billing access is least-privilege, owner-approved and removed promptly.	Named access register and review record	Quarterly and on departure	Workspace owner	Needs confirmation
Incident response	Severity, responder, communication, containment, recovery and post-incident review are defined before external production use.	Incident runbook and completed exercise	Semiannual exercise	Incident commander	Planned

Connected platform

API partners and operating contracts

Every integration needs an approved data boundary, environment-specific authorization, idempotent events, reconciliation, monitoring, disconnect behavior and a named owner.

Core platformConfirmed target

Supabase

Database, authentication, storage, realtime and server-side workflows

Data exchanged: Users, Workspaces, Projects, Entities, files and operational records
Authorization: Service credentials and user JWTs
Events and sync: Database events, Realtime and Edge Function triggers

Artificial intelligencePlanned

OpenAI

Writing, extraction, matching support, summaries and presentation generation

Data exchanged: Permission-filtered prompts, selected Project context and user-approved documents
Authorization: Server-side API key
Events and sync: Asynchronous job completion where required

Email deliveryPlanned

Resend

Transactional messages and editable notification templates

Data exchanged: Recipient, template variables, delivery metadata and suppression state
Authorization: Server-side API key
Events and sync: Delivered, bounced, complained and suppressed webhooks

CommunicationsPlanned

Twilio

SMS, calls, numbers, voicemail, recordings and transcripts

Data exchanged: Phone numbers, messages, call metadata, recordings and consent state
Authorization: Account credentials or API keys
Events and sync: Message, call, recording and status webhooks

CommunicationsPlanned

Google Gmail

Connect the Designer inbox and associate permitted email with Projects and records

Data exchanged: Authorized message metadata, content, participants and attachments
Authorization: OAuth 2.0
Events and sync: Mailbox watch/push notifications and incremental synchronization

SchedulingPlanned

Google Calendar

Two-way calendar visibility for Project meetings, visits, delivery and installation

Data exchanged: Selected calendar events, attendees, times and linked Registry record IDs
Authorization: OAuth 2.0
Events and sync: Calendar watch notifications and reconciliation jobs

Import and exportPlanned

Google Sheets

Mapped import of items, budgets and legacy operational data

Data exchanged: User-selected ranges, column mappings, import results and provenance
Authorization: OAuth 2.0
Events and sync: Manual import first; controlled sync later

PaymentsPlanned

Stripe

Collect payments and track processor settlement

Data exchanged: Customers, payment intents, invoices, refunds and settlement metadata
Authorization: Server-side secret key and connected account authorization if adopted
Events and sync: Signed payment and account webhooks

AccountingPlanned

QuickBooks Online

Synchronize approved accounting records and reconcile financial operations

Data exchanged: Customers, Providers, invoices, payments, taxes and account mappings
Authorization: OAuth 2.0
Events and sync: Change notifications plus reconciliation polling

Products and procurementPartner-by-partner

Approved Vendor APIs

Search approved catalogues, import products and track availability or orders

Data exchanged: Product data, pricing, trade availability, order and shipment status
Authorization: Partner-specific OAuth or API credentials
Events and sync: Partner-specific webhooks, feeds or polling

LogisticsFuture

Carrier and tracking APIs

Expected arrival, shipment tracking and delivery status

Data exchanged: Tracking numbers, shipment events, ETA and proof metadata
Authorization: Partner-specific credentials
Events and sync: Tracking update webhooks or scheduled polling

Recovery and incidents

Minimum runbook register

Production release

Trigger: Approved change is ready for production

Minimum response: Confirm commit, tests, migrations, feature flags, monitoring, owner and rollback

Hub workflow proven; product workflow needs confirmation

Rollback or feature disable

Trigger: Release causes material errors or unsafe behavior

Minimum response: Stop exposure, preserve evidence, revert artifact or disable flag, verify recovery and communicate

Needs product implementation

Database restoration

Trigger: Data loss, corruption or recovery exercise

Minimum response: Declare recovery point, restore isolated copy, validate integrity, approve cutover and reconcile writes

Needs confirmation with Supabase

Integration outage

Trigger: External API, webhook or OAuth service fails

Minimum response: Degrade safely, queue work, stop duplicate effects, notify operators, reconcile after recovery

Defined in Spec 18; implementation pending

Security or privacy incident

Trigger: Unauthorized access, secret exposure or suspected data disclosure

Minimum response: Contain, revoke, preserve logs, assess scope, notify required parties and document remediation

Policy and owner required

User access emergency

Trigger: Owner lockout, compromised account or urgent Membership suspension

Minimum response: Verify authority, require dual control where appropriate, apply time-limited action and write immutable audit

Defined in Specs 03, 08 and 17

Operating rhythm

Required review cadence

Every release

Review diff, tests, migrations, feature flags, monitoring and rollback; record deployed version and owner.

Daily

Review critical errors, failed webhooks, job backlogs, email/SMS delivery exceptions and payment reconciliation alerts.

Weekly

Review platform health, open incidents, integration exceptions, security events and roadmap technical blockers.

Monthly

Review vendor spend, quotas, certificates/domains, backup health, dependency updates and unresolved ownership.

Quarterly

Review access, secrets, recovery tests, data retention, RLS coverage, vendor risk and production readiness.

Decision queue

What must be confirmed next

These are explicit operating decisions. Once resolved, update the affected register row and retain the decision date, owner and evidence.

Confirm the Design Registry product repository, default branch, hosting provider and production deployment workflow.

The live product cannot have traceable releases, rollback or migration ownership until this is known.

Decision owner · Brad + technical lead

Confirm Supabase project references, environment separation, migration ownership, backups and restoration procedure.

Supabase is the intended source of truth and authentication boundary.

Decision owner · Technical and data owners

Select observability, error tracking and alert routing for the product and integrations.

Provider, payment and communication failures must reach an accountable operator.

Decision owner · Technical lead

Confirm the public website repository, deployment path, production domain and application handoff contract.

Provider and Designer signup must preserve the correct application type and referral context.

Decision owner · Marketing + technical lead

Choose the production secret manager and document account ownership, billing ownership and emergency access.

Keys must not be shared informally or stored in source and documents.

Decision owner · Workspace owner + technical lead

Define recovery objectives, retention periods and legal/privacy requirements by data domain.

Backup, deletion, audit and incident obligations depend on explicit policy.

Decision owner · Business, legal and technical owners

Map business.design-registry.com to the private operating hub when domain and access policy are approved.

The current private Sites URL is functional; the custom domain improves internal discoverability.

Decision owner · Brad

Required production record

Account and environment checklist

Complete this record for every production system and external provider. Store references and ownership here; keep secret values in the approved manager.

01Legal account owner02Day-to-day administrator03Billing owner and renewal date04System criticality and data classification05Development account or project06Preview/staging account or project07Production account or project08Repository, default branch and protection09Build, migration and deployment commands10Environment variables by environment11Secret-manager reference and rotation owner12Domain, DNS and certificate owner13OAuth callback and webhook URLs14Backup, RPO, RTO and restoration test15Monitoring, alert route and incident contact16Last access, vendor-risk and key review