Public Review Announcement
Status: Public Review · pre-
v0.1.0 Public Preview. APIs, contracts, deployment instructions, and SDK interfaces may still change before thev0.1.0cut.
What this is
Xtrape Capsule is a lightweight, self-hosted, agent-based runtime governance control plane for Capsule Services — small services, automation workers, integration adapters, background jobs, private tools, and AI Agent runtimes that connect to a single Opstage console through an embedded Agent SDK.
We're inviting Public Review before the v0.1.0 Public Preview release cut. This means:
- The Public Review repositories are open and runnable.
- Contracts and SDK packages are published to npm under the
public-reviewdist-tag. - During Public Review, the source-build Docker Compose path is canonical. GHCR images may be produced from
mainfor validation, but the stableghcr.io/xtrape-com/xtrape-capsule-ce:0.1.0image becomes the primary documented path only after thev0.1.0 Public Previewcut. - Documentation, README content, and deployment guides are stable enough to follow end-to-end.
The pieces that are still moving:
- Wire protocol may shift in additive minor versions before
v1.0. - The agent token cache and a handful of helpers (
newId,apiList) are marked provisional in the Schema Stability table. - A few v0.2 polish items are tracked as open issues across the repos.
What we're asking from reviewers
- Run the Quick Start. Build CE from source via Docker Compose, sign in, and create a registration token. See Quick Start.
- Connect a service. Either follow the first Capsule Service guide or clone
xtrape-capsule-demoand run it as-is. - Try a full action lifecycle. Trigger the demo
echoaction, watch the command transitionPENDING → RUNNING → SUCCEEDED, then inspect the audit trail. - Tell us what broke. File issues against the relevant repository:
- CE backend / UI / deployment →
xtrape-capsule-ce - Agent SDK behavior →
xtrape-capsule-agent-node - Contract / Zod schema mismatches →
xtrape-capsule-contracts-node - Docs / site →
xtrape-capsule-site
- CE backend / UI / deployment →
We are particularly interested in feedback on:
- Quick Start friction in fresh environments (Docker / port / env-var surprises).
- Cases where the SDK API doesn't match the docs.
- Public-facing wording — we want the site to be technically accurate and free of internal-engineering shorthand.
- Security model edge cases — see Security Overview for the deployment checklist; if you find a path we missed, please file a private security report per each repo's
SECURITY.md.
What we are explicitly not ready for
- Business-critical HA production. CE is single-node with SQLite. HA belongs to the future Enterprise Edition.
- Public-internet exposure without a hardening layer. No built-in IP allow-list, no rate-limit on admin login, no SSO. Put Opstage behind a reverse proxy with SSO / VPN.
- Regulated environments requiring compliance controls. Audit and RBAC are present but not certified.
Cross-package compatibility
| Package | This release | npm dist-tag |
|---|---|---|
xtrape-capsule-ce | 0.1.0 | n/a (Docker image) |
@xtrape/capsule-agent-node | 0.1.0-public-review.0 | public-review |
@xtrape/capsule-contracts-node | 0.1.0-public-review.0 | public-review |
xtrape-capsule-demo | matches | n/a |
xtrape-capsule-site | matches | n/a |
Pin matching 0.1.x minors across CE, Agent SDK, Contracts, and Demo during Public Review.
What changes between Public Review and Public Preview
When the v0.1.0 Public Preview cut lands, expect:
- The stable npm release path will start tracking the matching
v0.1.0packages. - The git tag
v0.1.0and the GHCR image tag0.1.0will be promoted from the current pre-release artifacts. - The site will switch Quick Start and Install to the published image path as the primary instruction.
- A changelog entry per repo will pin the cut.