Add committed revenue drawdown guard

[IOROHKI]

/claim #20

Summary

• Add a self-contained committed-revenue-drawdown-guard module for the Revenue Infrastructure bounty.
• Evaluate institutional minimum commitments across subscription, AI compute, and analytics licensing streams.
• Detect under-consumption, overage risk, expiring prepaid credits, low-margin compute usage, and amendment/expansion readiness.
• Emit deterministic audit digests plus reviewer-ready JSON, SVG, and GIF demo artifacts.

Scope differentiation

This is not another generic billing ledger, metering module, tax guard, dispute packet, SLA credit calculator, royalty settlement module, recognition close, or forecast. This slice focuses on the contract drawdown boundary: whether prepaid or committed institutional revenue is being consumed at the right pace, and whether the account needs a drawdown plan, paid amendment, or expansion motion before finance review.

Demo artifacts

• committed-revenue-drawdown-guard/reports/demo-output.json
• committed-revenue-drawdown-guard/reports/demo.svg
• committed-revenue-drawdown-guard/reports/demo.gif
• committed-revenue-drawdown-guard/reports/demo.mp4 (H.264 short demo video)

Validation

• node committed-revenue-drawdown-guard/test.js
• node committed-revenue-drawdown-guard/demo.js
• node --check committed-revenue-drawdown-guard/index.js
• node --check committed-revenue-drawdown-guard/sample-data.js
• node --check committed-revenue-drawdown-guard/test.js
• node --check committed-revenue-drawdown-guard/demo.js
• git diff --check

AI-assisted with OpenAI Codex; I reviewed and locally verified the diff before submitting.