DOCUMENTATION

Enterprise

Organizations, roles, four-eyes governance, examiner seats, white-label, monitoring, deposit screening, event feeds and the audit trail — what is built today.

An organization shares policies, exceptions, investigations, webhooks and API receipts among its members. The server decides every permission; the table below is the same permission table the app uses to explain a refusal.

Roles

RoleEdit policy draftsSimulate a draft against past verdictsSubmit a draft for activationActivate a submitted policy (not their own)Request an exception on a verdictDecide an exception (not their own)Manage membersRead the audit logGrant and revoke examiner seatsSet the white-label brandRecord exports, alerts and scheduled runs
owner✓✓✓✓✓✓✓✓✓✓✓
admin✓✓✓✓✓✓✓✓✓✓✓
compliance✓✓✓✓✓✓—✓✓—✓
reviewer———✓—✓—✓———
risk✓✓✓—✓——✓——✓
analyst✓✓✓—✓—————✓
auditor———————✓———
viewer———————————
api———————————
regulator———————✓———

Oversight

  • A policy submitted by one member must be activated by another; the server refuses self-activation.
  • Policy exceptions are requested by one member and decided by another, and every decision is written to an append-only audit log.
  • Investigations are opened, prioritised and closed by people. The AI assistant can be asked about a case but cannot create, change or close one.
  • Every call to an AI model is recorded with digests and sizes, so what was sent and when can be shown without keeping a second copy of the text.

Regulator seats

An owner, admin or compliance member can give an examiner a read-only seat for 1 to 180 days (Institutional and above). The examiner signs in with their own NOSHASHI account and reads the organization's policies, exceptions, investigations and audit log; every write the server offers refuses them. The seat stops working at its end date without anyone acting, because membership itself honours the expiry, and each visit is written to the audit log (at most once every 30 minutes). Granting, extending and revoking a seat are audit entries too.

White-label console and reports

An owner or admin can set the organization's display name and accent colour. Members then see that name at the top of the console, credited as running on NOSHASHI, and it is printed on the reports they export: "Prepared for …" on the SHA-256 audit export and the asset passport PDF. The audit export's hash checks its bytes against a recorded reference; it is not a digital signature authenticating its producer. NOSHASHI holds no keys, so there is no wallet to brand; what carries the brand is the record.

What the audit log records

The server records governance itself: policy drafts, submissions and activations, exceptions and their decisions, investigations, webhooks, members, seats and the brand. A member's workstation adds what only it sees, under the member's own identity: every file exported (name, size and SHA-256), every verdict recorded, changes to the monitoring schedule and alert rules, each scheduled stress run, and each custom alert that fired. Examiners and viewers read the log and cannot add to it. Nothing in it can be edited or deleted by anyone.

Scheduled monitoring and custom alerts

PORTFOLIO & RADAR › MONITOR re-runs the redemption stress test for every wallet in the book every 1 to 24 hours while the app is open, with the same readers and model as the Risk screen, and keeps the last 30 readings per wallet. Alert rules test those readings (recovery ratio, freezable share, days to exit, trapped value, mark value, frozen and freezable positions) with conditions joined by ALL or ANY, scoped to every wallet or chosen ones, with a cooldown. A rule sends to the console, a desktop notification, or the organization's webhooks as the signed event custom_alert. A figure that could not be measured never triggers a rule.

Deposit screening (Enterprise)

ADJUDICATION › LEDGER WATCH screens an incoming payment before it is credited, read live from the ledger. It credits what actually arrived (delivered_amount; a partial payment that asks for 100,000 XRP and delivers 0.077 is credited 0.077), holds a familiar ticker whose issuer owes nothing as counterfeit, flags a drop of dust whose memo carries a link as a phishing lure, notes a missing destination tag, the issuer's freeze and clawback rights and your Travel Rule threshold, and reads who created the sender, who created them and who created them, checking all three against the organization's deny list. The verdict is clear, review or hold, with the amount to credit; a fact that could not be read holds the deposit rather than passing it. Watched deposit addresses are screened by the server every minute, without the app open.

XRPL event feeds (Strategic)

An organization can watch up to 100 accounts. The server reads each one's new validated transactions every minute and records payments, trust-line freezes and changes, account settings and issuer flag changes, offers, checks, escrows, clawbacks, NFT and AMM activity; another party's trade that only rippled through the account is recorded as such, not as the account's own act. Every event goes to the organization's webhooks as xrpl_event (and deposit_screened for screened deposits), and can be pulled from GET /functions/v1/noshashi-xrpl-watch/events as JSON, NDJSON or CSV with an organization key; POST …/history reads any account over any ledger range the same way, for backfill.

Custom schemas, bulk export and retention (Strategic)

An export schema names the fields you want (a dotted path such as data.delivered.value) and the column to write each under, for ledger events or the audit log, in CSV, NDJSON or JSON. The same schema shapes a bulk export saved from the console and the feed API (?schema=<id>), which your systems pull on their own schedule. Ledger events are kept for the number of days you set, from 7 to 3,650; the audit log is never removed.

Integrations

Organization API keys record receipts as the organization's (API). Governance events are delivered to your endpoints with a signature (Webhooks).

Plans and contract terms are on the Enterprise and pricing pages. NOSHASHI holds no security certification (such as SOC 2 or ISO 27001) and makes no claim of regulatory compliance. It is software that reads the ledger and applies rules; the decisions stay yours.

Generated from src/lib/org/governance.ts · src/lib/org/webhooks.ts · src/lib/xrpl/ledgerWatch.ts · supabase/functions/_shared/xrplEvents.ts · src/lib/trust/boundary.json