CoreFinOps Glossary
Definitions of migration and financial terms used across the product.
Glossary
| Term | Definition |
|---|---|
| Application | Business-level system containing one or more workloads. |
| Workload | Deployable/operational unit carrying technical and financial context. |
| Legacy estate | Source infrastructure, applications, contracts and costs before migration. |
| CUR 2.0 / Data Export | AWS billing data export used to establish cost facts. |
| Net amortized | Default AWS cost measure used for financial analysis where consistently available. |
| Allocation | Assigning a cost fact to a supported business scope under a documented rule. |
| UNALLOCATED | A cost deliberately left unattributed due to insufficient mapping evidence. |
| Assessment | Strategy and decision-context evaluation for an application/workload. |
| Readiness blocker | A tracked unmet condition affecting migration suitability. |
| Wave | Group of migration workloads planned for a defined execution period. |
| Dual run | Time when source and target environments both remain in operation. |
| Cutover | Technical handoff from legacy to target; not proof of cost removal. |
| Financial decommission | Verified removal of remaining source recurring cost or approved exception. |
| Stranded cost | Legacy obligation that persists after the intended transition. |
| Opportunity | Candidate cost optimization, generally estimated before action. |
| Action Center | Governed work items, approvals, external implementation confirmation and verification. |
| Value Ledger | Evidence-linked record of expected, realized/attested and verified value states. |
| Source freshness | When evidence was observed/ingested, not when a page was opened. |
| ExternalId | Additional STS trust condition used when CoreFinOps assumes a customer role. |
| Entitlement | Server-enforced feature/usage rights derived from the effective subscription. |
| LicenseArn | AWS Marketplace identifier used to distinguish concurrent purchase agreements. |
Important interpretation
The same term can carry different evidence levels. For example, “savings” in a recommendation is estimated; “savings” in a Value Ledger entry must state whether it is customer-attested or independently system-measured. Documentation and reports must use precise qualifiers.
Concept
Precision in language reflects precision in evidence. “Savings” without a qualifier is insufficient — always state the evidence level alongside the number.