PALO FRAMEWORKKnown cost + open reservations
Cost accountability / version 1.3
AI FinOps.
Account for every AI attempt. Reconcile spending, compare model transitions and evaluate when local-learning investment could pay back at acceptable quality and latency.
Local workspaceYour browser. Your records.
No provider connection.
No provider connection.
New in 1.3: Local learning compares three frozen configurations offline. Research, evidence limits and reproducibility | End users, IT, administrators and finance.
Untitled FinOps
Empty workspaceStart with your own workspace, import a snapshot or explore explicitly synthetic records.
Review workspace replacement
Current records remain unchanged until you confirm. Save or export them first if you need to retain both copies.
01 / Get started
Build a clear account of AI spend.
Set a budget, create a workload and register a route with its rate card. Then reserve an attempt before recording its cost.
Want to see the workflow first?
The synthetic example includes settled costs and an expense awaiting reconciliation.
Budget position
$0.00remaining allowance
Workspace budget$0.00No budget configured
Known cost $0.00Open reservations $0.00Available $0.00
No attempts recorded
No accepted tasks yet
Task-level outcome coverage
Workload allocation
0 workloads| Workload | Known | Reserved | Remaining |
|---|
Known cost breakdown
Recorded amountsIncludes recorded non-token charges. Missing or unreported costs cannot be inferred.
This view accounts for declared records. Estimated comparisons do not establish realised savings. A reference to provider evidence does not independently verify that evidence.
One task, every attempt
Attempts ledger
Reservations remain committed until a known settlement or reconciliation. Failed attempts still contribute to cost.
| Attempt / task | Route | Reservation | Known cost | Status | Provenance |
|---|
Inspect event journal
Events are appended in sequence. This browser snapshot is editable input, not a signed audit trail.
From source cost to accepted result
Billing & showback
Finance exports include attempts, billing, allocation rules and operations records. The main toolbar exports the attempts workspace only. Operations can also be saved and exported separately. Files remain local. Imported source labels are declarations, not authenticated invoices.
Import the documented JSON format to start. Partial or ambiguous imports preserve the previous valid costs.
One currency and cost basis
Correlation, not additional spend
Resolve before finalising metrics
| Source / revision | Kind | Net cost | Unlinked residual | Finality | Evidence |
|---|
Import history and quarantine
| Run | Status | UTC coverage, end exclusive | Reason / resolution |
|---|
Inspect source revisions and provenance
All accepted historical revisions, including replaced records. This history is not added to current totals.
Inspect or correct reconciliation links
| Link ID | Source revision | Attempt | Amount | Measurement |
|---|
Open liabilities and review dates
An overdue review triggers escalation, never automatic release of a reserve.
| Attempt | Reserved | Review state | Owner | Next review |
|---|
03 / Explain shared costs
Allocation rules
Rules match dimensions in priority order. Weights, versions and effective dates are explicit. Missing weights leave costs unallocated. Preview does not change source amounts.
| Source revision | Destination | Amount | Rule |
|---|
Preparing operations workspace...
Before a model change
Assess a route transition
Compare the remaining cost of staying with the current route against switching. Include context replay, cache effects, verification, tools and governance overhead in both estimates.
Research method and input contract
Preparing the local-learning research workspace...
Make the scope explicit
Workspace setup
Register a route and versioned rate card
Review local transition policy
Rate cards & provenance
JSON schema ↗Rate cards remain bound to their version IDs in the event journal. To add a new version for an existing route, export JSON, add a rate card with a new ID and import the validated snapshot.