EVE — Readiness Language (16B)

Precise, approved readiness language for every public surface. Do not use the banned phrases (production ready, unbreakable, impossible to bypass, guaranteed compliant, certified, works with every framework, all adapters supported, complete multimodal understanding, remote exactly-once execution, fully RFC 8785 compliant). See the claims registry.

Component	Approved readiness
EVE SDK core	RELEASE CANDIDATE WITH EXCLUSIONS
Python SDK (`eve-coreguard` 0.2.2)	release-candidate core client
TypeScript SDK (`@eve/coreguard` 0.1.0-rc1)	release-candidate core client
Core governance architecture (CoreGuard, evidence)	pilot-validated
MCP distributed deployment	distributed-pilot validated in the documented test topology
Shadow subsystem	authenticated pilot-ready
Artifact & red-team subsystems	customer-pilot ready at supported boundaries
Framework adapters (OpenAI Agents / Claude / LangChain / LangGraph / CrewAI / Vercel)	experimental
Generic adapter, evidence verification, JCS-1	supported

Readiness levels (registry)

SUPPORTED — validated and covered by tests; safe for the stated pilot boundary.
PILOT_READY — validated for pilots at the documented topology; not a production claim.
EXPERIMENTAL — structurally implemented, not validated against live pinned versions.
DEVELOPMENT_ONLY — for local development; not for pilot traffic.
ENTERPRISE_ONLY — available in enterprise deployments.
UNSUPPORTED — out of scope.

What "RELEASE CANDIDATE WITH EXCLUSIONS" means

The core Python and TypeScript SDKs build from committed source, install cleanly outside the repository, fail closed on service errors, and produce independently verifiable evidence. The exclusions are: the framework adapters (except generic) are not yet validated against live pinned framework versions; the pip client governs via hosted mode (embedded governance is the EVE service); and the release-candidate artifacts are not yet published to public registries. These are release-engineering and integration items, not correctness defects.

Public-registry status (validated 2026-07-20)

Package Public registry state (as validated)

eve-coreguard (Python) The corrected RC client is 0.2.2 (exports EVE; SHA-256 wheel 1bee61c3… / sdist 38952487…, reproducible from committed source), distributed privately for pilots — not yet on PyPI. The only build currently on PyPI is a pre-RC 0.2.1 (SHA-256 4fa7e7fa…, no EVE export), which will be yanked once 0.2.2 is public. Until then, install the pilot 0.2.2 wheel; a plain public pip install eve-coreguard resolves to the pre-RC 0.2.1 where from eve_coreguard import EVE fails.

@eve/coreguard (TypeScript) Unpublished on npm (404); the name is available. When published it will use a prerelease dist-tag (rc) — install @eve/coreguard@0.1.0-rc1, never an unqualified npm install @eve/coreguard.

Package	Public registry state (as validated)
`eve-coreguard` (Python)	The corrected RC client is 0.2.2 (exports `EVE`; SHA-256 wheel `1bee61c3…` / sdist `38952487…`, reproducible from committed source), distributed privately for pilots — not yet on PyPI. The only build currently on PyPI is a pre-RC `0.2.1` (SHA-256 `4fa7e7fa…`, no `EVE` export), which will be yanked once `0.2.2` is public. Until then, install the pilot `0.2.2` wheel; a plain public `pip install eve-coreguard` resolves to the pre-RC `0.2.1` where `from eve_coreguard import EVE` fails.
`@eve/coreguard` (TypeScript)	Unpublished on npm (404); the name is available. When published it will use a prerelease dist-tag (`rc`) — install `@eve/coreguard@0.1.0-rc1`, never an unqualified `npm install @eve/coreguard`.

Publishing 0.2.2 and yanking the pre-RC PyPI 0.2.1 is a credential-gated release-engineering step handled under the publication authorization plan — not a public claim made here.

Limitations

This page describes readiness, not guarantees. No component here is described as production ready or certified. Pilot engagement is via a design-partner pilot (see pricing).