Find your next step.

Ctrl / ⌘ K to open · Esc to close · Demonstration commands use fictional data.

DEVELOPERS / OPEN ECOSYSTEM

Intelligence grows
through well-defined connections.

The ecosystem vision includes agents, skills, tools, models, connectors, policies, and evaluators. Compatibility should come with explicit contracts, permissions, versions, and review.

Explore the live demoPlatform vision
INTELLIGENCEOS / DEVELOPERS01 — OVERVIEW

02 / THE OPERATING CONTRACT

What open ecosystem
brings into view.

01

Agents and skills

Package a task capability with its mission, dependencies, boundaries, and acceptance criteria. Publication does not automatically make it trusted.

02

Tools and connectors

Document supported actions, authentication, data scopes, receipts, and failure behavior. Access is granted through organizational controls.

03

Policies and evaluators

Share reviewable control and evaluation patterns. Context matters: a policy suitable for one workflow may be inappropriate for another.

04

Registry vision

A future publication registry could expose versions, dependencies, reviews, and lifecycle state. This website has no live marketplace.

03 / CONNECTED BY DESIGN

The path
through the system.

Inspect the sequence.
Each stage has a defined responsibility.

Select a node to inspect its role in the workflow.

Before work begins.

Define the source of truth, permitted actions, accountable owner, and acceptance criteria. Scope matters more than an open-ended instruction.

Before work moves on.

Check the outcome, capture unresolved exceptions, and preserve the relevant policy and evidence. A task is complete only within its defined boundary.

04 / A CONCRETE EXAMPLE

A connector is an access boundary.

A future reporting connector would separate fetching records, drafting a report, and publishing a report. Each action needs its own permission and operational contract, so a worker can receive only the capability its mission needs.

ILLUSTRATIVE SCENARIO

Named enterprise systems on this site are source categories in a fictional demonstration. They are not confirmed connector integrations.

Defined scopeEvidence preservedReview when required
Try the control plane

05 / QUESTIONS & BOUNDARIES

Details
that matter.

Architecture descriptions show intended system behavior. Validate implementation, integration, data handling, and operational controls before relying on a production workflow.

Can I publish an agent today?

No. The publication registry and marketplace are platform vision.

Does a connector listing grant access?

No. Tool availability and organizational authorization are separate requirements.

How does this fit with the rest of IntelligenceOS?

Identity, context, policy, evaluation, verification, execution, and audit form one operating model. Explore the related components below to see their responsibilities.

06 / CONTINUE THE EXPLORATION

See the whole
operating picture.