Behind the annotated ledger
Follow the real backend contract. See what this browser demonstrates, and what still needs verification.
Return to the current demoProgress stays in this tab while you explore. Reload to start fresh.
01 / The parties
02 / Real backend
Source review: 4 October 2026, repository snapshot f6adc01. This is an implementation explanation, not a new live-system test.
The API key identifies the Organization. With an active subscription and configured metric, ingestion resolves an existing active Customer by its organization-scoped external ID. Acceptance commits a ledger-only UsageEvent and durable processing intent. Identical retries return the original event; changed billable fields conflict.
Inspect ingestion and retry handlingAccepted is not rated. PENDING processing reconciles as LEDGER_PENDING. PROCESSED without a rating or other outcome remains RATING_PENDING. Rating selects the PriceVersion effective at occurrence time. Explicit UNRATED / NO_APPLICABLE_PRICE means missing price; it is different from a successfully rated zero.
Inspect occurrence-time ratingExact integer arithmetic rounds half-up once per event to the currency scale. For 1,250 calls at INR 0.0025, the exact product is 3.125, the displayed contribution is INR 3.13, and persisted-form evidence is 3.130. Monthly lines sum individually rounded events, without pricing the aggregate again. The demo range of 1–10,000 calls is not an API limit.
Inspect exact money arithmeticA BillingRecord is a comparison calculation for one Customer and month, not a tax invoice or payment request. Occurrence time selects the UTC calendar month. The late window includes the exact close, 72 hours after next month starts. Only strictly after close can reconciled, fully rated usage become READY_FOR_REVIEW; unresolved usage blocks readiness.
Inspect monthly reconciliationReadiness is not approval. The backend checks current owner authority and fresh reconciliation before explicit finalization. It atomically freezes a version and creates the linked invoice.finalized event. Identical bound requests are idempotent. Corrections use linked revisions; the finalized monetary record stays immutable.
Inspect atomic finalizationCreating an event is not successful delivery. The backend records selected targets, attempts, retries and terminal outcomes, with manual replay. No selected endpoint means NO_TARGET. Receivers deduplicate stable event IDs. The historical technical name invoice.finalized describes a BillingRecord notification; it does not collect payment.
Inspect delivery status semantics03 / Browser demonstration
Quantity editing, acceptance, identical retries, processing and rating, scenario-time advancement, owner finalization and successful webhook delivery are all local simulations. Organization, Customer, usage, prices, identities, payload and endpoint are synthetic.
No authentication, production API, database write, worker, receiver request, signature verification or payment collection occurs. Advancing time changes the scenario clock only. Reload clears the in-memory run; other tabs have independent runs.
The demo shows one prepared happy path. It does not demonstrate real infrastructure recovery, receiver compatibility, capacity, instant onboarding or production readiness.
Inspect the local simulation transitions04 / Recorded verification
These are dated repository records. Their original environments and limitations still apply.
Read-only source inspection at fe6d3ae. Relevant backend files remain unchanged at this page’s reviewed snapshot. Includes the ingestion/rating quantity-cap discrepancy. Not an integration or production test.
Read the backend contract verificationRecorded local synthetic PostgreSQL 17, Redis 7 and loopback receiver checks cover delivery, owner actions, secret rotation and deployed-gate behavior. Rollback required a type-only compatibility patch and an isolated Prisma client. No representative migration safety or live receiver compatibility is established.
Read local webhook readiness evidenceLater follow-ups supersede the initial source-backup blocker: an isolated PostgreSQL 17.11 restore, additive migrations, inventory, patched rollback and return to the corrected current build passed within the recorded scope. All 35 current-schema tables matched across application switches. Provider-level provenance remains independently unconfirmed; the copy had no Customer or BillingRecord rows. Authenticated owner behavior, sender replay, original-ID loss and RPO/RTO remain unmeasured.
Read the restored-copy rehearsal and limitationsLocally built static showcase: Chromium and WebKit checks and viewport captures. Firefox failed to launch, so its behavior remains unverified. These browser checks demonstrate local interactions, not backend integration, human usability or full accessibility conformance.
Read recorded browser checks and captures05 / Still outstanding
Deployed Customer ingestion and owner finalization remain gated pending a separate rollout decision. The isolated-copy rehearsal does not establish authenticated owner behavior on representative billing records. Sender replay with original-ID reconciliation, receiver compatibility, and intended-host recovery evidence are still required.
Human usability sessions and a full WCAG 2.2 AA accessibility assessment remain pending. Automated keyboard and layout checks do not establish conformance.
Inspect outstanding operations gatesPilot discussions are exploratory and subject to readiness review.
Contact jatinawankar02@gmail.com for an exploratory discussion. Publication remains blocked: zero-cost static hosting is not confirmed.
Inspect the implementationContinue the current demo