Start from the capability
Why Components matter
A Component is more than a code snippet. It gives business behavior:- a stable platform identity and version history;
- an explicit type and ordered implementation elements;
- current runtime declarations and approved libraries;
- Sandbox validation and execution evidence;
- dependency relationships to Endpoints, Jobs, plugins, and other Components;
- a governed change path instead of an out-of-band script.
Choose an authoring path
Build a capability for Agents
When a business operation already exists as a Component, it can become a component tool plugin instead of being reimplemented inside a prompt or remote service.- Keep the Component contract narrow and deterministic.
- Define an explicit input and output schema.
- Classify whether it reads, writes, executes, affects an external system, or can be destructive.
- Attach the plugin only to the Interactive or Autonomous Agents that need it.
- Validate the read path first, then test writes with the intended approval policy.
Delivery workflow
The selected surface determines completion semantics. An Endpoint response, accepted Job, dispatched Event, and finalized Storage artifact are different durable facts; design the caller around the one that proves its business outcome.Components
Choose a Component type and lifecycle.
Low-code runtime
Use managed runtime APIs and libraries.
Custom Node.js
Build trusted package-based workloads.
Agent plugins
Expose business capabilities to Agents.