Give one Capsule a focused capability.
An Assistant is an immutable workload owned by one isolated Capsule. It combines a skill, named operations, explicit Service access, and optional routines without inheriting Space-level authority.
Capsule-owned by construction
- An Assistant belongs to one Capsule and shares only that Capsule's admitted resource budget.
- Its manifest declares named operations with closed input and output schemas.
- Service and Assistant access is allowlisted by interface and operation, never by generic reach.
- Credential declarations are opaque references; secret values stay in the responsible Service.
- Egress is exact and routines start disabled, single-flight, and idempotent.
Ask for an operation, not another workload
Collaboration means invoking one declared operation through a scoped capability. It never grants access to another Assistant's workspace, database, container, secrets, or generic network endpoint. Redpanda may carry durable events later, but a queue does not replace caller identity or authorization.
Prove the smallest useful loop
- Assistant Spec v1 Identity, immutable artifacts, operations, permissions, and routines
- Hello Pulse Scaffold, validate, and call one dependency-free operation locally
- Salesnator Prove read-only campaign health and idempotent notification intent
Salesnator uses only synthetic data. Meta and notification tokens remain in Services, and campaign mutations remain outside this MVP.
Creators may eventually distribute and sell Assistants. That marketplace is a later product layer, not permission to weaken the Capsule boundary or claim an unavailable checkout today.