@lssm-tech/lib.economic-evidence
Provider-neutral economic evidence primitives for ContractSpec applications.
This package is the neutral spine selected by Ultragoal G002 for usage-based and commission-based systems. It records replayable facts and refs for cost, usage, budget decisions, redaction, replay, and projection consumers without owning provider SDKs, BillingOS invoices/payments, FinanceOps advice, or observability implementations.
Exports
@lssm-tech/lib.economic-evidence@lssm-tech/lib.economic-evidence/cost@lssm-tech/lib.economic-evidence/decimal@lssm-tech/lib.economic-evidence/dimensions@lssm-tech/lib.economic-evidence/ledger@lssm-tech/lib.economic-evidence/usage@lssm-tech/lib.economic-evidence/budget@lssm-tech/lib.economic-evidence/replay@lssm-tech/lib.economic-evidence/reconciliation@lssm-tech/lib.economic-evidence/seam-kind@lssm-tech/lib.economic-evidence/projection-policy@lssm-tech/lib.economic-evidence/projection-refs@lssm-tech/lib.economic-evidence/unit-economics
Reconciled Cost Truth
EconomicLedgerEntryV1 models the append-only lifecycle estimate → reservation → execution_usage → provider_actual → invoice_import → correction. Corrections cite the entry they supersede; history is never deleted. reconciliationKey keeps successive observations of one economic fact from being double counted, while independent resources or usage lines remain independently additive.
Authoritative provider, invoice, reservation, and correction entries require exact minor-unit or decimal-string amounts. Estimated number-based compatibility records remain explicitly classified as estimates. Hard budget gates return review_required when cost evidence is unknown, stale, or unit-incompatible.
Allocation dimensions cover organization, tenant, workspace, environment, deployable, service, resource, capability, feature, contract/operation/version, endpoint, GraphQL, MCP, webhook, workflow, job, agent/tool invocation, provider/model, flag/variant, experiment, deployment, goal, and cost center. All calculations and canonicalization are deterministic and side-effect free.
Boundary
Producer packages may emit or cite these records. Projection packages may cite refs. This package must remain side-effect free and must not import provider, billing, finance, observability, or runtime implementations.
Projection And Seam Policy
Use createStandardEconomicProjectionRefs() from @lssm-tech/lib.economic-evidence/projection-policy to produce reference-only projections for BillingOS, FinanceOps, observability, and replay reports. Billing projections carry not_an_invoice; FinanceOps projections carry not_accounting_export; observability and replay projections are display-only.
Monorepo Enforcement
Production declarations use tsconfig.build.json, which extends the strict source configuration and excludes test and spec files. bun run typecheck continues to use tsconfig.json, including source-only tests; the production build does not change their typechecking requirements.
src/adoption-enforcement.test.ts guards the current vertical slice: cost-tracking, ai-providers, ai-agent, and builder-runtime must depend on the neutral evidence package; ai/chat/builder public evidence entrypoints must remain exported; and the neutral package must stay free of runtime, provider, billing, finance, observability, and payment dependencies.
The seam-kind bridge maps canonical economic_* evidence ref kinds into the short contract/runtime seam categories (usage, cost, budget, replay, projection). This keeps OperationSpec and runtime events compact while preserving the canonical neutral ref taxonomy for persisted evidence.
Published export maps include explicit browser conditions for the emitted browser artifacts, alongside the existing Node and Bun conditions. A browser bundler can select these without relying on the default server-runtime condition.
