Practitioners.
The team that scopes the work stays accountable for the architecture.
We run this firm the way we expect the work to run for a client: the delivery team owns the decisions, evidence, and runbook instead of handing them through an account layer. Scope reviews, architecture decisions, and code review stay close to the people doing the build.
We are deliberately focused and grow with intent. We default to "no" on work we cannot deliver cleanly, and "yes" on scoped engagements where we can leave a system, policy, or operating model your team can run.