tegwick
09ef7fa967
Record the FIN-WP-0007 split after checking resource-control: they keep intelligence resource identity and provision-level class I metering; session tokens stay with State Hub; work-effectiveness is a reporting join. Missing token counts are now unknown, not zero.
25 lines
1.3 KiB
Markdown
25 lines
1.3 KiB
Markdown
# Fin Hub Intent
|
|
|
|
Provide the **Financial Allocator** and authoritative booked-cost surface for
|
|
the FOS federation. Fin-hub owns booked financial facts and their corrections,
|
|
budgets, financial commitments, burn, runway, viability signals, and
|
|
client-level price, cost-attribution, and margin reporting.
|
|
|
|
Fin-hub consumes resource identity, technical usage, allocation evidence,
|
|
forecasts, commitment candidates, and optimization scenarios from
|
|
`resource-control` without becoming authoritative for those concepts. A
|
|
forecast or allocation never becomes booked spend merely because fin-hub
|
|
stores or reports it.
|
|
|
|
Intelligence follows the same split. Resource-control owns portfolio
|
|
identity and provision-level class `I` metering when Railiance procures a
|
|
model API, reserved weights, or inference host. State Hub owns agent-session
|
|
token evidence. Fin-hub books the plan invoice, records entitlement, joins
|
|
those inputs, and reports effectiveness. It does not invent a `resource_id`,
|
|
parse sessions, or emit technical usage or allocation as if it were
|
|
resource-control.
|
|
|
|
Fin-hub does not generate legal invoices, perform bookkeeping, execute or
|
|
track payments, approve contractual commitments, own client/resource identity,
|
|
or provision infrastructure. It records, reconciles, reports, projects, and
|
|
signals within that boundary.
|