One place to direct your AI, tools, and computer.

Nucleus is designed to turn what you ask into governed missions—planned, approved, executed, and verified.

Open Nucleus Console Explore the platform

Authority: You remain in control
Execution: Approval-gated effects
Evidence: Receipts you can inspect

Nucleus ConsoleILLUSTRATIVE FLOW

Mission in progress

Prepare the Nucleus public release.

Plan overview

I’ll prepare the release, pause for approval, then verify every published effect.

1PlanRelease scope and content.Completed
2ApprovalOwner review required.Awaiting approval
3ExecutePublish approved artifacts.Pending
4VerifyIssue evidence receipt.Pending

One intelligence · three interface editions

Make Nucleus feel like yours.

Air, Atelier, and Living System change the visual experience—not your missions, authority, usage, files, or receipts. Switch at any time from inside Nucleus.

Luminous pearl and cyan energy visual for the Nucleus Air edition

Air

Bright, spacious, and quietly expressive.

Atelier

Cinematic, editorial, and built for focus.

Living System

Immersive, conversational, and alive.

Open the edition switcherInterface choice stays on this device.

See governance in action

From intent to evidence, without losing your authority.

Nucleus keeps the plan, decision, effect, and verification connected as one mission.

01
Plan
Nucleus turns the outcome into bounded steps.
READY
02
Approval
You review protected or irreversible effects.
OWNER
03
Execute
Approved tools operate through scoped authority.
GOVERNED
04
Verify
Receipts record what actually happened.
EVIDENCE

Trust & receipts

Claims carry a status.

VERIFIED

Backed by reproducible local evidence.

BETA

Working capability with bounded release scope.

SPECIFICATION

Defined contract that is not yet a production service.

PLANNED

Direction only; no operational claim.

A clear first step

Choose the path that matches what you want to do.

These paths explain what is available now, what stays local, and where an owner approval is required. Selecting a path does not install, connect, publish, or transact.

DESKTOP OWNER PATH

Direct Nucleus through one governed console.

Begin with the signed desktop release, review the first-run guide, then describe an outcome. Nucleus keeps planning, approval, execution, and evidence in one mission.

1Verify the releaseUse only a signed artifact with a published digest.
2Open the desktop shellThe browser fallback is intentionally read-only.
3Review before effectProtected actions remain owner approval-gated.

Review desktop release

Build, run, and host on IOI

Local-first building. Governed cloud publishing.

Build and version on your computer. Create isolated previews. Publish only after verification and owner approval.

LOCAL BUILDISOLATED PREVIEWAPPROVAL-GATED DEPLOY

Open NOAH AI safely How hosting works

NOAH AIv0.3ILLUSTRATIVE EXAMPLE

01 export default {
02   async fetch(request, env) {
03     const catalog = await env.DB
04       .prepare('SELECT * FROM skills')
05       .all();
06
07     return Response.json(catalog);
08   }
09 };

IOI web hosting

A path from idea to owned deployment.

The production architecture is designed around isolated builds, versioned artifacts, custom domains, and per-tenant limits.

1
Build locally
Nucleus creates a version and digest without executing unreviewed code.
2
Preview safely
Cloudflare Sandbox runs builds in isolated containers.
BETA TARGET
3
Publish deliberately
Workers for Platforms routes approved tenant sites.
SPECIFICATION
4
Own the data
D1 stores metadata; R2 and Artifacts store versioned project content.
SPECIFICATION

A developer network with evidence

Share what works. Inspect before you install.

Packages carry publisher identity, version, permissions, provenance, and verification status.

View source

NameVersionPublisherVerificationRatingUses

Website AuditorRead-only website health evidence1.0.0Nucleus InternalVERIFIED LOCALNot rated—

Repository Health AuditorRepository safety and freshness checks1.0.0Nucleus InternalINSTALLEDNot rated—

Market IntelligenceBounded market research workflow1.3.0Nucleus MarketsINSTALLEDNot rated—

MODELED

Developer rewards require verified contribution.

Verified usage, quality votes, dispute outcomes, and signed payout policy must exist before rewards become payable.

NO REWARDS ISSUED

Catalog provenance: illustrative public rows and local verification labels are separate from a production marketplace. No package is installed, rated, or rewarded from this page.

Developer data host

Repositories, packages, versions, and evidence—one canonical graph.

IOI’s data plane is designed to complement Git workflows, not hide source or lock developers into an opaque builder.

Source & versions

Git-compatible project history and signed package manifests.

SPECIFICATION

Artifacts

Checksummed builds, previews, receipts, and reproducible outputs.

SPECIFICATION

Discovery

Searchable skills and tools with permissions and publisher identity.

BETA CATALOG

Federation

GitHub remains connectable; IOI records canonical mission provenance.

PLANNED

One canonical usage ledger

Models, costs, utility, and receipts stay connected.

Public runtime telemetry is unavailable until the production status API is activated.

Active modelNot published

Input tokens—

Output tokens—

Provider cost—

IOBC settlementSHADOW ONLY

1
Provider receipt
Measured model use and outcome.
RECEIPT
2
Usage credits
Canonical accounting entry.
CREDITS
3
IOBC utility settlement
Recorded in shadow accounting.
NOT ON-CHAIN
4
Burn receipt
Modeled burn tied to the mission.
MODELED

Token access, when legally available

Utility first. Purchase only through an approved path.

IOBC is designed for ecosystem settlement, developer rewards, attestations, hosted builds, and agent-to-agent transactions.

1Eligibility and jurisdiction check
2Regulated purchase or exchange partner
3Self-custody or supported wallet
4Utility settlement receipt

PLANNED · LEGAL REVIEW Understand IOBC utility

Why transactions are unavailable

Legal and jurisdiction reviewPENDING
Audited contracts and chain activationNOT EVIDENCED
Approved purchase and custody providersNOT CONNECTED
Owner production cutoverNOT GRANTED

IOBC is designed for ecosystem utility. Availability, transfer, and purchase features depend on law, approved providers, audited contracts, and owner activation.

Start with Nucleus.
Build into the Internet of Intelligence.

Open the live console Desktop release

One place to direct your AI, tools, and computer.

Prepare the Nucleus public release.

Make Nucleus feel like yours.

From intent to evidence, without losing your authority.

Plan

Approval

Execute

Verify

Claims carry a status.

Choose the path that matches what you want to do.

Direct Nucleus through one governed console.

Build locally, version clearly, publish deliberately.

Connect capabilities without handing over unrestricted authority.

Local-first building. Governed cloud publishing.

A path from idea to owned deployment.

Build locally

Preview safely

Publish deliberately

Own the data

Share what works. Inspect before you install.

Developer rewards require verified contribution.

Repositories, packages, versions, and evidence—one canonical graph.

Source & versions

Artifacts

Discovery

Federation

Models, costs, utility, and receipts stay connected.

Provider receipt

Usage credits

IOBC utility settlement

Burn receipt

Utility first. Purchase only through an approved path.

Start with Nucleus.
Build into the Internet of Intelligence.

Publish a skill

One place to direct your AI, tools, and computer.

Prepare the Nucleus public release.

Make Nucleus feel like yours.

From intent to evidence, without losing your authority.

Plan

Approval

Execute

Verify

Claims carry a status.

Choose the path that matches what you want to do.

Direct Nucleus through one governed console.

Build locally, version clearly, publish deliberately.

Connect capabilities without handing over unrestricted authority.

Local-first building. Governed cloud publishing.

A path from idea to owned deployment.

Build locally

Preview safely

Publish deliberately

Own the data

Share what works. Inspect before you install.

Developer rewards require verified contribution.

Repositories, packages, versions, and evidence—one canonical graph.

Source & versions

Artifacts

Discovery

Federation

Models, costs, utility, and receipts stay connected.

Provider receipt

Usage credits

IOBC utility settlement

Burn receipt

Utility first. Purchase only through an approved path.

Start with Nucleus.Build into the Internet of Intelligence.

Start with Nucleus.
Build into the Internet of Intelligence.