docs(ai): AI Cost & Savings guide#277
Closed
maximelb wants to merge 1 commit into
Closed
Conversation
A user-facing guide to how LimaCharlie computes AI agent cost and the analyst savings figure: the resolution mix (AI-only / AI+Human / Human-only), cost profiles (the ai_cost_model Hive), the savings formula and crediting rule, a worked example, and how to read and tune the panel. Three Mermaid diagrams (inputs→outputs, case classification, savings pipeline). No backend internals — only concepts users see (Cases, Hives, AI usage, the UI). Added to the AI Sessions nav. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014onzsCbKCevowbod9BK2rx
lcbill
approved these changes
Jun 19, 2026
Contributor
Author
maximelb
added a commit
that referenced
this pull request
Jun 21, 2026
Fold the AI Cost & Savings guide (PR #277) into the canonical cost-tracking.md page the web app links to, so there is one page instead of two overlapping ones. Adds from #277: the "who did the work" premise, three Mermaid diagrams (inputs→outputs, case classification, savings pipeline), a fully worked numeric example, logging-human-time, tuning-for- trust, and an FAQ. Keeps the existing per-severity valuation, headline metrics (analyst-hours / FTE / automation rate), per-profile P&L, cumulative trend, CSV exports, fleet/MSSP rollup, and per-session budget relationship. Moves the nav entry up to after User Sessions. Supersedes #277. Claude-Session: https://claude.ai/code/session_012ie78qt9UBuvCBEEfLRKT3 Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A thorough, user-facing guide explaining how LimaCharlie computes AI agent cost and the analyst savings figure — so a user asking "how does this work?" gets a complete, trustworthy picture.
New page:
docs/9-ai-sessions/cost-and-savings.md(added to the AI Sessions nav, after User Sessions).Covers:
ai_cost_modelHive: loaded rate + minutes-per-investigation, one profile per kind of analyst work, per-org/per-tenant.Three Mermaid diagrams: inputs→outputs overview, case-classification flow, and the savings-calculation pipeline.
Audience & scope
Written for LimaCharlie users. Deliberately contains no backend internals — only concepts users actually see and control: Cases, Hives (
ai_cost_model), AI usage, and the web UI. Verified clean of service/storage references.Checks
markdownlint-cli2: 0 errors.mkdocs build --strictcouldn't run in my environment (the config's!!python/nameMermaid fence tag needs the site's plugin env), so the nav addition and links are best validated by CI / a reviewer preview. Mermaid labels are all quoted to parse cleanly.Draft — this documents the AI Cost & Savings feature; merge alongside its rollout.