NUMINA OS 4.0 / INTELLIGENCE IN MOTION.
One core.
A complete operating system.
One root. Five architecture layers. Service work, agent authority, treasury records and release evidence in one connected workspace.
Move through Numina.
Explore the five architecture layers ↗Your workspace starts here.
Sign in to save requests, follow scope review, and receive delivery notes. Each request stays private to you and Numina’s operator.
Sign in to view your requests.
Success criteria
Payment evidence
Consulting payment amounts come from signed Stripe events, before processing fees. NUSD scope requests have no payment or token allocation.
Activity and delivery
Numina 4 · runtime connection
Loading deployed release…
Loading current release…
Signed runtime records are separate from provider submission, custody and settlement.
Inspect the 3.0 release & runtime ↗NUSD runtime.
Built with a traceable record.
Loading verified build record…
The source archive, Linux image archive and inventory have their own dated build evidence.
The recorded build produced a Linux image. Production hosting and financial execution are not established by that build. Current application capabilities are reported separately below.
Inspect the three verified artifacts
- Source revision
Unavailable- Builder revision
Unavailable- Built image configuration digest
Unavailable
- Source archive verification result ↗
- Linux image verification result ↗
- Inventory verification result ↗
GitHub CLI verified these artifact signatures against the pinned builder and source revisions. This page checks the retained review and inventory fingerprints; it does not repeat Sigstore signature verification in the browser. The contract was a precompiled input. This record does not establish a security audit, reserves, custody, settlement or a new SLSA level.
Current NUSD application status
Current application status unknown
- NUSD contract address
Unknown- Token identity verification
- Unknown
- Treasury backing status
- Unknown
- NUSD service pricing status
- Unknown
- NUSD quotations
- Unknown
- Issuance
- Unknown
- Transfers
- Unknown
- Settlement
- Unknown
- Redemption
- Unknown
Mint preparation and recipient evidence guide ↗ · Read mint workflow
These fields come from the current public application status response. Enabled capabilities describe application configuration; transaction receipts and reserve evidence are separate. The canonical Numina treasury and private provider observations remain in their authenticated views.
Consulting services use the existing USD Stripe checkout after an authenticated request is saved. Review service scope and pricing ↗
Network deployment
Loading network record…
Checking application node connection…
Read current node connection ↗
Network details & activation status ↗Numina Treasury
The canonical Numina-native balance and journal record. Verification applies to the Numina model.
Read canonical treasury record ↗OWNER / STRIPE FINANCIAL ACCOUNT
Stripe account observation
Stripe reports the currencies shown above. The owner designates this account as a backing source for the singular Numina-native NUSD treasury. Reserve allocation and holder redemption rights require their own evidence. Read treasury policy.
One set of Treasury records.
All Numina-native treasury views read one canonical balance and journal. Open the control plane for its current records.
Owner access is required. The native treasury is recorded in NUSD under NUMINA authority.
Agent operations
Open the authenticated control plane to manage internal requests, delegated authority, evidence and recorded decisions.
The control plane records authorized internal operations. External execution and NUSD settlement require their own provider and transaction evidence.
Numina agent control
Manage delegated agents, policy decisions, approvals and signed records in the production workspace.
Open control room ↗