Decision Register
Single source of planning truth
This page consolidates the key operationalization decisions into one register so the team can track owners, dependencies, status, and next actions without jumping between multiple planning pages.
Use this page to
- review current decision ownership
- spot blocked work quickly
- prepare stakeholder meetings
- keep planning and rollout aligned
Consolidated register
This register uses a more realistic internal stakeholder model while still staying generic enough to be adapted later. Replace these placeholders with exact team names or named owners when the program has formal assignment.
| Workstream | Decision | Current direction | Owner | Status | Depends on | Next action |
|---|---|---|---|---|---|---|
| Identity | Workforce sign-in path | MongoDB Okta SSO | Corporate Identity and Security Engineering | Needs decision | approved Okta integration pattern | confirm preferred SSO pattern and claims model |
| Identity | Break-glass admin policy | explicit and audited exception flow | Security Engineering and App Administrators | Drafted | privileged-access expectations | define exception process and review cadence |
| Org-aware access | Builder Relations source of truth | HRIS or approved org graph | Builder Relations Operations and Org Systems | Needs decision | authoritative org data source | confirm system of record and refresh model |
| Org-aware access | Entitlement mapping layer | app-managed mapping from trusted identity and org inputs | Product Management and Application Engineering | Drafted | identity and org inputs | define role-mapping rules and exceptions |
| Hosting | First Kanopy target | admin control plane and internal service layer | Internal Platform Engineering and Application Engineering | Drafted | runtime boundary and hosting pattern | confirm first hosted workloads |
| Hosting | Environment model | explicit dev, staging, and production separation | Internal Platform Engineering | Drafted | internal environment standards | define environment boundaries and promotion flow |
| Hosting | Secret management path | central managed secrets | Internal Platform Engineering and Security Engineering | Needs validation | platform secret management standard | confirm secret and config handling path |
| Hosting | Deployment verification standard | health checks plus rollback playbook | Internal Platform Engineering and Application Engineering | Drafted | deploy and rollback expectations | define verification and rollback checklist |
| Observability | Telemetry stack | approved internal logging, metrics, and tracing stack | Internal Platform Engineering and Application Engineering | Needs decision | platform telemetry guidance | confirm supported stack and collection model |
| Observability | Reliability dashboard ownership | engineering and operators | Application Engineering | Drafted | telemetry baseline | define dashboard scope and owner |
| Observability | Product usage dashboard ownership | product and leadership-facing analytics owner | Product Management and Builder Relations Operations | Drafted | usage metric definitions | define adoption metrics and reporting owner |
| Observability | Audit-event scope | auth, role changes, privileged routes, exports | Security Engineering and Application Engineering | Drafted | security expectations | confirm event scope and retention expectations |
| Rollout | Internal readiness gate | checklist-based pilot or rollout decision | Product Management and Application Engineering | Blocked | upstream identity, hosting, and telemetry decisions | revisit once core decisions move forward |
Decision
Working rule
Any stakeholder meeting that changes a recommendation, owner, or dependency should update this register immediately. This page should become the fastest way to understand the program state.