4 min read - Open vs Closed AI Models: A Control, Capability and Cost Matrix
AI Architecture
Published April 4, 2026 · Author Exceev Consulting
In April 2026, the Gemma 4 announcement supplied the dated context for assessing capability fit. The announcement sets the external boundary. Your own evidence must establish whether the idea fits your organisation.
Decide how to handle capability fit
Proceed only after verifying Capability fit, Control boundary, Total operating cost, Exit options before selecting a design or provider.
Architecture should make constraints visible before implementation. Map data movement, trust boundaries, failure modes and reversibility before selecting a platform or model. Apply that rule to capability fit and control boundary.
Start with capability fit. That check determines which evidence will be useful for the other dimensions.
What the Gemma 4 announcement source contributes to capability fit
Gemma 4 announcement was reviewed on 27 August 2026 for its treatment of capability fit. Check the current source before a procurement, architecture or compliance decision. An announcement describes the offer or initiative. Your internal evidence determines whether it meets the need. This operational framework is not legal advice.
Examine capability fit, control boundary, total operating cost, exit options
1. Capability fit
For capability fit, record the current state, the owner and the decision that depends on this dimension. Keep the inventory limited to verifiable facts.
2. Control boundary
For control boundary, map the dependencies, data and affected people. Test any assumption that could invalidate the initiative before investing further.
3. Total operating cost
For total operating cost, choose observable evidence and a minimum threshold. The test should tell you whether to proceed; an impressive demonstration is not enough.
4. Exit options
For exit options, set the boundary, escalation path and exit condition. The team must be able to stop, replace or return the solution to manual operation.
Decision matrix for capability fit
| Dimension | Decision question | Minimum evidence |
|---|---|---|
| Capability fit | What exists today, and who owns it? | A dated inventory and a named owner |
| Control boundary | Which dependencies or constraints could block the initiative? | A dependency map and the assumptions to test |
| Total operating cost | Which result would justify proceeding? | A test result measured against a defined threshold |
| Exit options | How will the team contain, stop or replace the solution? | A boundary, escalation path and exit condition |
Leadership, business, technology and security teams should assess the same evidence on capability fit and control boundary before deciding.
Test capability fit in five steps
- Scope capability fit. Write down the question, owner and date by which an answer is required.
- Establish the control boundary baseline. Measure the current process, including quality, incidents and review effort.
- Test total operating cost. Limit data, users, permissions and duration so the change remains reversible.
- Review exit options. Examine errors, manual rework, escalations and effects on affected people.
- Answer the original question. Record proceed, change or stop, together with the evidence supporting that choice.
Evidence to retain for control boundary
The evidence pack keeps the findings on capability fit with the other material needed for the decision:
- the decision, its owner and consulted stakeholders;
- the inventory associated with capability fit;
- the baseline and test results for control boundary;
- the access, risks and approvals connected to total operating cost;
- the rollout, monitoring and exit plan for exit options.
If this initiative stops, retain its findings on capability fit and exit options so the next review does not repeat the same assumptions.
Mistakes that weaken total operating cost
Avoid:
- selecting a platform before mapping data and trust boundaries
- assuming a successful demo proves production feasibility
- ignoring reversibility, portability and failure containment
A 30-day plan for exit options
- Days 1 to 5. Name the owner of capability fit, define the boundary and collect available sources.
- Days 6 to 12. Map control boundary, including its data, access, dependencies and failure scenarios.
- Days 13 to 20. Test total operating cost against a baseline and pre-agreed stop criteria.
- Days 21 to 26. Ask the responsible functions to review the findings on exit options.
- Days 27 to 30. Compare the four findings with the decision above and define the next required proof.
Record the decision on capability fit
Keep a short record with the owner, evidence reviewed and decision. Add the condition that would trigger another review of capability fit or exit options.
Thinking about AI for your team?
We help companies move from prototype to production — with architecture that lasts and costs that make sense.