Unit of value
Cost per token is an input metric. Cost per accepted investigation or incident is the decision metric.
MODULE 07 / 10
All modules ↑CONTROL · TARGET L4 · 4–5 days
07
Token cost per incident
Attribute model and tool consumption to each incident and identify actionable cost drivers.
Create the unit economics needed for engineering control, client pricing and credible GenAI FinOps content.
Prerequisites
- Modules 02 and 06
- FinOps allocation basics
- Basic data aggregation
01 / CONCEPT LESSONS
Build the mental model first.
Attribution
Join provider usage to trace, incident, team, environment and outcome.
Effective cost
Include retries, failed runs, observability and supporting infrastructure.
Budgets
Apply per-run limits, daily anomaly thresholds and environment budgets.
Optimization
Reduce unnecessary work before switching models: context, loops, caching, routing and tool precision.
02 / SYSTEM FLOW
Trace the complete path.
Usage event→Trace ID→Incident ID→Rate table→Effective cost→Outcome status→Dashboard + budget
For every arrow, the engineer must name the data, identity, trust boundary, failure mode and evidence produced.
03 / GUIDED LAB
Build it in bounded steps.
AI and documentation are allowed. The learner owns every generated artifact and must preserve the stated safety boundaries.
- 01Define the cost-event schema.
- 02Capture usage by model and operation.
- 03Join usage to incident outcome.
- 04Include failed and retried runs.
- 05Build cost-per-incident distribution and anomaly view.
- 06Recommend one optimization and measure it again.
04 / INCIDENT SIMULATION
Average incident cost rises 3× after a release.
Mentor injects
- Repeated context in every loop
- Fallback model route changed
- Failed runs excluded from the dashboard
Required evidence
- Driver decomposition
- Reconciled total to provider usage
- Before/after unit cost
Investigation loop
Symptom → impact → hypothesis → evidence → test → root cause → containment → correction → verification.
05 / DESIGN CHALLENGE
Start with a blank page.
Propose budget controls that reduce runaway cost without suppressing high-value investigations.
06 / VERIFY & SUBMIT
Verification checklist
Submission package
- Metric definition
- Cost schema
- Dashboard
- Anomaly incident report
- Optimization decision
Review questions
- What is the denominator?
- Who owns unallocated cost?
- How do retries appear?
- Can lower cost reduce value?
- Which control stops runaway spend first?
07 / MENTOR-ONLY GUIDANCE
Change the denominator during review. The engineer should immediately explain how that changes the apparent economics.
SCORING1 · cannot explain2 · explains with gaps3 · implements and verifies4 · designs and handles trade-offs
Record the achieved L-level only from observed evidence. Course completion and certification do not automatically change the skill matrix.