coulomb/fin-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: reporting-allocate AI-plan cost across work

Browse source 
Split a booked AI-plan fact across workplans or repos using measured
tokens, measured+estimated tokens, session counts, or an even split.
Unmeasured remainder stays a residual. The record is not resource-control
AllocationEvidence and does not create booked spend.
This commit is contained in:
tegwick 2026-08-15 19:35:43 +02:00
parent 8916f3c4d0
commit efd1b31001
10 changed files with 646 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
workplans/FIN-WP-0007-ai-plan-token-effectiveness.md
View file

@ -275,7 +275,7 @@ slices require a method. No session files are parsed and no
```task
id: FIN-WP-0007-T05
status: todo
status: done
priority: medium
state_hub_task_id: "db098143-90b7-475c-8846-e4c274e50b4a"
```
@ -299,6 +299,12 @@ Done when a one-plan, two-workplan fixture reconciles to the booked
effective amount, names its method, keeps residual when coverage is
incomplete, and is not stored as `AllocationEvidence`.
Completed 2026-08-15: `ledger allocate-plan` writes a reporting
allocation for an `ai-plan` fact. One plan / two workplans at 100 and
50 measured tokens of a 200-token pool leaves a 0.25 unmeasured
residual and still sums to the booked €200. The record is not stored
as `AllocationEvidence` and does not change booked totals.
## Publish an effectiveness report
```task