Open Space Duck exposes the core building blocks of the Spaceduckling stack: trust, identity, lifecycle, and accountable agent structure. It is designed so a small team, a family operator, or a serious self-hoster can run the framework without needing the full hosted platform.
Open Space Duck packages the agent lifecycle, trust model, birth-certificate layer, and surrounding operational doctrine into a framework that can be adapted and extended without losing accountability.
Use the canonical identity flow without re-inventing every state machine from scratch.
Certificate issuance and trust cues stay visible as part of the framework, not as an afterthought.
The canonical object model, lifecycle, and operating structure are intended to be run and adapted openly.
Identity shell, lifecycle states, trust language, and operator-facing structure.
Composable skills and modular capabilities for different agent runtimes and workloads.
The framework is meant to support different use cases, runtimes, and governance shapes without breaking the main canon.
Different agent classes can ship as dedicated skills or runtime packages.
Rules, freezes, and protocol decisions can be maintained as open operational doctrine.
Hosted Space Duck Auth remains deliberately thin: a minimal trust and access layer rather than a bloated control plane. The intent is to store the least data required to prove ownership, manage trust, and support accountable activation.
Auth, trust checks, and minimal registry support where hosting is useful.
Keep the hosted layer light instead of turning it into a grab-bag SaaS backend.