Company governance
Decision Queue
One company-wide register for choices that need evidence, discussion and an accountable conclusion. Each item states the actual question, a recommended starting point, what evidence closes it and the source that created it.
Frame
Agree on the exact decision—not merely the surrounding topic.
Challenge
Review the recommendation, risks, alternatives and missing evidence.
Decide
Name the accountable decision-maker, decision and effective date.
Propagate
Update the source document, roadmap, owner and dependent work.
7 of 31 decisions shown
P0DR-001TechnologyReady to discussConfirm the Design Registry product repository, default branch, hosting provider and production deployment workflow.
Confirm the Design Registry product repository, default branch, hosting provider and production deployment workflow.
Confirm the Design Registry product repository, default branch, hosting provider and production deployment workflow.
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.
Confirm the accountable owner and record the selected production approach in the Technology and Operating Register.
Named account owner, current configuration, production evidence and an accepted operating procedure.
- Decision owner
- Brad + technical lead
- Required timing
- Before the next production release
P0DR-002TechnologyReady to discussConfirm Supabase project references, environment separation, migration ownership, backups and restoration procedure.
Confirm Supabase project references, environment separation, migration ownership, backups and restoration procedure.
Confirm Supabase project references, environment separation, migration ownership, backups and restoration procedure.
Confirm Supabase project references, environment separation, migration ownership, backups and restoration procedure.
Supabase is the intended source of truth and authentication boundary.
Confirm the accountable owner and record the selected production approach in the Technology and Operating Register.
Named account owner, current configuration, production evidence and an accepted operating procedure.
- Decision owner
- Technical and data owners
- Required timing
- Before the next production release
P0DR-003TechnologyReady to discussSelect observability, error tracking and alert routing for the product and integrations.
Select observability, error tracking and alert routing for the product and integrations.
Select observability, error tracking and alert routing for the product and integrations.
Select observability, error tracking and alert routing for the product and integrations.
Provider, payment and communication failures must reach an accountable operator.
Confirm the accountable owner and record the selected production approach in the Technology and Operating Register.
Shortlist, cost, product compatibility, alert-routing plan and a tested failure notification.
- Decision owner
- Technical lead
- Required timing
- Before the next production release
P1DR-004TechnologyEvidence requiredConfirm the public website repository, deployment path, production domain and application handoff contract.
Confirm the public website repository, deployment path, production domain and application handoff contract.
Confirm the public website repository, deployment path, production domain and application handoff contract.
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.
Confirm the accountable owner and record the selected production approach in the Technology and Operating Register.
Named account owner, current configuration, production evidence and an accepted operating procedure.
- Decision owner
- Marketing + technical lead
- Required timing
- Before the dependent integration or domain launch
P1DR-005TechnologyEvidence requiredChoose the production secret manager and document account ownership, billing ownership and emergency access.
Choose the production secret manager and document account ownership, billing ownership and emergency access.
Choose the production secret manager and document account ownership, billing ownership and emergency access.
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.
Confirm the accountable owner and record the selected production approach in the Technology and Operating Register.
Named account owner, current configuration, production evidence and an accepted operating procedure.
- Decision owner
- Workspace owner + technical lead
- Required timing
- Before the dependent integration or domain launch
P1DR-006TechnologyEvidence requiredDefine recovery objectives, retention periods and legal/privacy requirements by data domain.
Define recovery objectives, retention periods and legal/privacy requirements by data domain.
Define recovery objectives, retention periods and legal/privacy requirements by data domain.
Define recovery objectives, retention periods and legal/privacy requirements by data domain.
Backup, deletion, audit and incident obligations depend on explicit policy.
Confirm the accountable owner and record the selected production approach in the Technology and Operating Register.
Named account owner, current configuration, production evidence and an accepted operating procedure.
- Decision owner
- Business, legal and technical owners
- Required timing
- Before the dependent integration or domain launch
P2DR-007TechnologyEvidence requiredMap business.design-registry.com to the private operating hub when domain and access policy are approved.
Map business.design-registry.com to the private operating hub when domain and access policy are approved.
Map business.design-registry.com to the private operating hub when domain and access policy are approved.
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.
Keep the private Sites URL as the working address and map the custom subdomain only after access and DNS ownership are documented.
Named account owner, current configuration, production evidence and an accepted operating procedure.
- Decision owner
- Brad
- Required timing
- Before the dependent integration or domain launch
Closure standard