Use Cases

Note: QAZ is an internal accounting unit used for balances and entries, not a currency, token, or asset.

1. Internal Ledger for Complex Systems

Problem:

• Multiple services write financial state and you need consistent balances.

Why a regular DB is insufficient:

• Application-layer bugs or retries can break invariants without a ledger model.
• You need enforced double-entry rules and idempotency across services.

How Qazna helps:

• Provides a deterministic ledger runtime with strict invariants and audit logs.
• Makes balance changes explicit and replayable.

Scenario:

• A microservices-based finance platform retries a transfer after a timeout. An idempotency key ensures the ledger applies the effect once.

{
  "from_id": "acct-a",
  "to_id": "acct-b",
  "currency": "QAZ",
  "amount": 5000,
  "idempotency_key": "transfer-2025-04-01-0001"
}

2. Financial Simulation & Replay

• Deterministic replay of transactions to reproduce incidents.
• Clear audit trail for postmortems and change validation.
• Predictable state transitions with idempotent operations.
• Useful for validating migrations and incident response runbooks.
• Scenario: after a production incident, replay the same transaction set to confirm the exact state transition sequence.

$ qazna replay --from 2025-04-01T00:00:00Z --to 2025-04-01T06:00:00Z

3. Neutral Multi-Party Ledger

Example: a clearing consortium needs a neutral ledger operated by one runtime while multiple parties audit the results.

Participant Systems ---> [ Ledger Runtime ] ---> Audit Log
        |                         |                 |
        +-------------------------+-----------------+

• Not blockchain.
• Governed by legal agreement, not code.
• Single runtime, multi-party audit.

About QAZ (Unit of Account)

QAZ stands for Quantized Accounting Zone. It is an internal, abstract unit of account used by the ledger runtime, not a currency, token, asset, or means of payment.