NOSHASHI

DOCUMENTATION

Architecture

The parts NOSHASHI is made of, and the path every reading takes from the ledger to a receipt.

Parts

PartWhereWhat it does
Desktop appsrc/ · src-tauri/Tauri shell with a React interface. It reads the ledger directly, runs every engine and the rule set on the device, and keeps local history.
Websitesite/ · scripts/build-site.mjsStatic pages rendered at deploy time, including these docs.
Site functionsauthority contact contact-status create-checkout-session locale project-feed stripe-status subscribe support-chat xrp-market xrp-newsVercel functions behind the website: market and news feeds, the project feed, contact and newsletter sign-up, the support chat, checkout and the public authority check.
Edge functionsnoshashi-checkout noshashi-exception-decide noshashi-password noshashi-policy-activate noshashi-stripe-webhook noshashi-verifySupabase Edge Functions: the Compliance API, checkout and billing, policy activation, exception decisions and password screening.
Databasesupabase/migrations/ (17 migrations)Postgres with row-level security: accounts, API keys and rate limits, organizations and roles, policies, exceptions, investigations, webhooks and the audit log.

The repository also holds an earlier FastAPI service (backend/) and Next.js interface (frontend/). They are not deployed, and nothing on this site depends on them.

From the ledger to the receipt

  1. XRPL MAINNET — Public XRP Ledger servers, read over WebSocket and HTTPS.
    src/lib/xrpl/link.ts · src/lib/xrpl/client.ts
  2. VALIDATED STATE — Ledger state is read from the last validated ledger, never an open one.
    src/lib/xrpl/client.ts · src/lib/desk/settlement.ts
  3. NORMALIZATION — Raw ledger fields become comparable facts.
    src/lib/xrpl/client.ts · supabase/functions/noshashi-verify/read.ts
  4. ANALYSIS — Deterministic engines: issuer controls, concentration, liquidity, credentials, provenance.
    src/lib/desk/
  5. POLICY ENGINE — Rules applied to the facts: the domain registry and, when set, an institutional policy.
    src/lib/policy.ts · src/lib/desk/institutional.ts · supabase/functions/noshashi-policy-activate/
  6. DECISION — GO, HOLD, NO-GO or INSUFFICIENT DATA, from the rule results alone.
    src/lib/policy.ts
  7. EVIDENCE — What was read, which rules applied, what each found.
    src/lib/desk/evidence.ts · src/lib/desk/investigations.ts
  8. CRYPTOGRAPHIC RECEIPT — A SHA-256 digest over a fixed, canonical form of the decision.
    src/lib/policy.ts · src/lib/desk/evidence.ts

Generated from src/lib/trust/boundary.json · supabase/functions · supabase/migrations · api