Commercial boundary
Commercial Boundary
Raven is not purchased from a public checkout as a production system. A quote follows scope, package, support model, legal boundary and human commercial approval.
Audience procurement / finance
Mode quote before activation
Boundary no public production sale
Commercial Path
ResearchPublic findings and briefings help the customer understand whether decision exposure is worth discussing.
ReviewA Raven Operational Intelligence Review can analyze approved offline data without live production access.
PilotA pilot measures whether decision delay, evidence quality or coordination cost is visible in the customer's environment.
ProductionProduction requires a separate contract, security gate, support model, rollback plan and activation approval.
What A Quote Must Define
ScopeEnvironment, incident class, data mode, support hours and expected outputs.
PackageDecision depth, evidence depth, financial analysis, governance level and optional credits.
ResponsibilityHuman approval boundary, support boundary, customer obligations and Raven limitations.
BillingCurrency, tax, invoicing, payment terms and any credit or package model.
Support boundarySupport hours, escalation route, response targets, severity classes and production support activation must be separately defined; the public page creates no SLA.
Quote approvalA quote requires scope reference, legal review, tax review, owner approval, valid-until date, audit reference and evidence-backed quote lines before customer send or checkout.
Quote boundaryQuote readiness does not send a customer quote, create provider price, create checkout session, issue invoice, calculate tax, collect payment or activate a customer account.
Credit Purchase Boundary
ConfirmationAny future credit checkout must require explicit buyer confirmation before payment handoff.
PackagesCredit quantities are selected from an approved package list. Current planning catalog uses 100, 200, 500 and 1000 credits at EUR 15 net per Raven Decision Credit before quote-specific approval and tax review. Unknown package ids are rejected before checkout.
Catalog boundaryThe planning catalog does not create Stripe products, provider prices, checkout sessions, discounts, tax calculations, invoices or payment collection.
Double-charge guardPayment events require idempotency and verified provider signatures before credits can be reviewed. The provider event check requires verified provider signature, allowed event type, idempotency key and payload-hash check.
Provider event ledgerA Stripe event alone does not post credits. Duplicate events return the existing result, conflicts stop for owner review and no customer service activates from checkout alone.
Credit ledger persistenceCredit ledger persistence requires provider event readiness, idempotency, owner approval and owner release gate before persistence. Prepared entries do not make credits available until the persistence gate is closed.
Balance read modelAvailable balance is shown only from ledger_entry_persisted_verified entries. Pending entries remain pending, low-credit notice is Mira draft-only, and no notification or activation is sent from the public page.
Billing portal boundaryFuture billing portal access requires finance, owner or admin role, approved scope, owner approval, audit reference and safe relative return path. Public pages do not create a provider portal session or redirect URL.
Invoice boundaryInvoice artifacts are draft previews until owner release. Public pages do not issue invoices, create provider invoice objects, submit tax documents, perform KSeF submission or collect payment.
Activation boundaryCredits may fund approved decisions, but credit purchase does not activate a customer, tenant, collector or production service.
What Raven Does Not Claim
No automatic activationPayment or checkout cannot activate a customer production environment by itself.
No pre-validated outcomeRaven can estimate and validate decision exposure; savings require customer context and operational action.
No hidden authorityRaven prepares recommendations. The customer keeps decision authority.