Owner: Lola (Ops) · Reviewer: Purple · Department: Operations · Status: Live · Version: 1.0
Effective Date: 2026-06-13 · Last Reviewed: 2026-06-13 · Next Review Date: 2026-09-13
Source of Truth: this validation + code audits · Maturity: 4 (Operational)
Which operations depend on Jonathan? Goal: minimize founder-dependent execution.
| Decision | Classification | Note |
|---|---|---|
| Authority/decision-rights definition | REQUIRED | Founder must fill the answer sheet — blocks delegation of everything below. |
| Entity bifurcation (who issues Seal) | REQUIRED | Founder + counsel decision (Bifurcation Memo). |
| Lifting provisional banners | REQUIRED | Founder sign-off after counsel execution. |
| Recall approval | DELEGATABLE | To Compliance lead once answer sheet confirms. |
| DSHS communications | DELEGATABLE | To Compliance lead + counsel once confirmed. |
| Vendor suspension/reinstatement | DELEGATABLE | Platform-scoped; delegate to Ops/Compliance. |
| Financial authority (refund/credit/settlement caps) | UNDOCUMENTED | No matrix exists — founder to set, then delegate. |
| Day-to-day workflow execution | DELEGATABLE | Already documented; executes without founder once owners confirmed. |
The single founder dependency that gates everything is authority confirmation. Once the answer sheet is signed, almost all operational decisions become delegatable. The financial-authority matrix is the one genuinely undocumented founder decision.
Program Closeout Report · Final Scorecard · Remediation Plan · Home