Monetizer

Monetizer is an internal, read-only commercial evidence client for Stado's platform catalogue, entitlement, recommendation, and attributed-revenue records. It helps an operator inspect whether the declared commercial control plane agrees with the evidence without turning a reporting command into a billing or access authority.

Boundaries

Monetizer never mutates Stripe, invents or changes a price, grants access, changes an entitlement, moves money, or treats a model response as commercial truth. It reads the versioned platform contract and reports what the owning systems already record. Mutations remain with the catalog, entitlement, ledger, payment, and revenue owners.

The command separates evidence gathering from decisions:

• assess gathers commercial and platform facts without deciding what to sell or change.
• probe checks that the expected registry records and interfaces exist.
• judge asks Brama to evaluate an explicit evidence package only after the operator acknowledges the model cost; the response is advice, not authority.
• suite exposes the approved catalogue, entitlements, recommendations, and attributed-revenue records through one read-only surface.

Contract and interfaces

platform-contract.json is the versioned boundary for the records Monetizer may read. The CLI validates requested operations against that contract before dispatch. Catalogue entries describe approved products and commercial coordinates; entitlement records describe already-issued access; recommendations remain proposals; attributed-revenue records report ownership already written by the revenue ledger.

All output is structured for review and automation. A missing, malformed, or contradictory record is surfaced as a failure or an unknown result rather than filled with a guessed price, entitlement, customer, or revenue claim.

Operations and security

Run the narrowest command that answers the question. Keep Brama-backed judging off unless qualitative review is required and its cost has been explicitly acknowledged. Treat catalogue, entitlement, and ledger services as independent authorities: a healthy response from one does not prove the others are current.

Credentials remain scoped to read-only interfaces and are not printed. Monetizer does not accept payment credentials, write tokens, or a fallback that bypasses the platform contract. Operational assessment files and local strategy notes are not product state; the durable outputs are the owning services' structured records.

Status

Monetizer is an internal operator tool. Its supported contract is the checked-in platform-contract.json plus the command surface implemented by src/main.rs; it is not a public billing API or a system of record.