Commitment report
Tracks a configured cost-reduction commitment (created by log10x_configure_engine) and reports promised vs delivered week by week. Attributes variance to four buckets (cap_fired, drift, new_patterns, leakage) and projects forward Bayesian confidence.
Contract-aware: at contract_type='committed' tier (year-one committed-volume deals), bytes-saved is the primary KPI and dollar savings are reported as a shadow number with caveat. At on_demand or past term-end, dollars become the primary KPI.
Example
You
weekly commitment report for payment-svc
Log10x
Commitment weekly: 38.4% delivered vs 40% committed on payment-svc · 90d Bayesian confidence p10/p90: 34%/44%. Attribution: cap_fired=94%, drift=4%, new_patterns=2%, leakage=0%.
More to ask
- "commitment report last 90 days"
- "why is confidence low?"
- "commitment report for all services"
Prerequisites
log10x_configure_engine must have been run and a commitment record created. Reporter and Receiver deployed for metrics. Engine >= 1.0.8 for the isDropped label.
Schema and samples
Input schema
Agent-facing JSON Schema (the canonical shape the MCP server publishes via tools/list):
{
"type": "object",
"properties": {
"commitment_id": {
"type": "string",
"description": "Commitment record id (created by log10x_configure_engine on PR-merge). If omitted, resolves the most recent commitment for the active service."
},
"service": {
"type": "string",
"description": "Service name to resolve a commitment by — used when commitment_id is omitted. When both are present, commitment_id wins."
},
"period": {
"type": "string",
"enum": [
"30d",
"90d",
"ytd"
],
"default": "90d",
"description": "Reporting window. 30d=last 30 days, 90d=last 90 days, ytd=since Jan 1 of current year."
},
"format": {
"type": "string",
"enum": [
"cfo_md",
"summary",
"json",
"weekly_digest"
],
"default": "cfo_md",
"description": "cfo_md=executive markdown with weekly chart and forward confidence; summary=typed envelope only; json=full structured data; weekly_digest=7-day operational digest from the recurring tick audit trail."
},
"history_path": {
"type": "string",
"description": "Override path to the recurring-tick JSONL audit trail (default: $LOG10X_RECUR_HISTORY_PATH or /tmp/log10x-recur-history.jsonl). Used only when format=weekly_digest."
},
"action_intent_path": {
"type": "string",
"description": "Override path to data/action-intent.json (relative to the gitops repo root or absolute). Used only when format=weekly_digest."
},
"environment": {
"type": "string",
"description": "Environment nickname; defaults to the active env."
}
},
"additionalProperties": false
}
Source: src/tools/commitment-report.ts.
Output schema
The data block inside the StructuredOutput envelope:
interface ToolData {
commitment_id: string;
service: string;
target_percent: number;
period: string;
delivered_pct: number;
variance_attribution: {
cap_fired_pct: number;
drift_pct: number;
new_patterns_pct: number;
leakage_pct: number;
};
weekly_series: Array<{
week_start: string;
delivered_pct: number;
delivered_bytes: number;
delivered_dollars: number | null;
rate_source: 'list_price' | 'customer_supplied' | 'unset';
}>;
aggregate: {
delivered_pct_mean: number;
delivered_dollars_total: number;
annual_projection: number;
};
bayesian_confidence: { p10: number; p90: number };
human_summary: string;
}
Envelope-level fields: summary.headline, actions[], schema_epoch.