KTAPEOUTCapabilities and status
The engineering distribution now has a separate TN10 naming deployment, ktape.official.adapter.registry 1.0.0, and a configured release coordinator. Neither is bundled in this minimal checkout. The included Compact Registry evidence remains scoped to its declared historical lineage; do not use it as a current root or as admission evidence for a different adapter. Engineering deployment, formal Profile admission, browser startup, retained bytes and private data recovery are distinct claims. Mainnet and production recovery remain outside this candidate.
| Surface | Status in 0.5.0 | What it proves | What it does not prove |
|---|---|---|---|
| Rust Core and canonical vectors | Available | Canonical local encoding and bounded verification | Mainnet or generic VM support |
Rust ktape CLI | Available preview | Local project, Profile, artifact and plan workflows | Signing, custody or broadcast |
ktape package build | Available local preview | Deterministic KTAPEOUT-STATIC-RUNTIME-MANIFEST-V1 package with browser-verifier limits and secret-file rejection | Upload, locator publication, signing, broadcast, activation or L1 admission |
| Generic storage provider and cross-device recovery | Not bundled | Storage identity, locator and verification boundaries are documented | No generic live upload/download adapter, production retention service, private backup service or cross-device restore |
| Private Directory Tree V2 Rust structure verifier | Included source preview; local structural verification only | Recomputes a bounded decrypted Root/Page/Object tree and its V2 commitments | Receipt authentication, transaction verification, predecessor/CAS authority, selected-chain inclusion or production Native Host admission |
Source Manifest ktape dev workflow | Declaration validation only; overall INCOMPLETE until supported execution stages exist | Manifest/workflow binding; unexecuted vectors remain STRUCTURE_ONLY, build/package/publishability NOT_RUN | Application behavior execution or publishability |
Source Manifest ktape app test | Structural vector-presence check; ToolResult WARNING | Required vector field exists and manifest shape is valid | Vector execution or application behavior correctness |
| Native-KAS bounded adapter | Source-line only; outside this candidate | The broader release workspace contains a Profile-specific adapter boundary | This minimal package does not bundle the adapter or imply generic L1 admission |
| Client-neutral contract boundary | Available in the public contracts | Equivalent clients can consume the same schemas, vectors and evidence labels | A client implementation, provider or UI becomes protocol authority |
| Browser SDK / Studio | Available in the broader release workspace; outside this candidate | Bounded authoring, handoff and client-integration surfaces when their declared contracts are present | This minimal candidate does not bundle a generic live runtime, provider, signer or application host |
| Direct-L1 Bridge | Evidence-gated | Declared dual-source reads and receipt checks | Official authority without Registry evidence |
| Public TN10 Registry identity | Historical included evidence | Versioned manifest, Bridge trust anchor and recorded readback for the declared Compact Registry root | The current engineering deployment's root configuration, fresh live readback, consensus finality or Mainnet authority |
| Supported Profile-specific TN10 application paths | TESTNET_ADMITTED only for paths with the required Profile/adapter admission evidence, declared NetworkPolicy, external signer and fresh readback | Path-specific Testnet-10 publication and readback | Package status alone admitting an application; generic L1 adapter admission, consensus finality or Mainnet authorization |
| Runtime maintenance and genesis provenance tooling | Available local/read-only | Hash-bound maintenance, provenance, rebuild and evidence validation | Migration, signing, broadcast or L1 authority |
| Namespace Registry compiler / genesis builder | Deferred from this candidate | The source release contains unsigned local tooling under a separate adapter/toolchain review | This package does not bundle the adapter, compiler inputs, signer handoff or Genesis publication path |
| Wallet/session boundary | External | Caller/provider authorization when supplied | KTAPEOUT custody or automatic signing |
Use conservative labels in downstream applications: LOCAL_ONLY, PROFILE_ONLY, PROOF_INCOMPLETE, UNAVAILABLE and L1_VERIFIED only when the corresponding evidence rules are satisfied. Never upgrade a weaker label because a command returned successfully.
V6 Profile integration is deferred from this curated candidate. The complete engineering deployment workflow and provider implementations are not bundled.