KTAPEOUT Application Engineering Skill

Architecture and version boundary

For a full engineering checkout, choose naming operations from its configured adapter and pinned root. The current engineering TN10 deployment uses ktape.official.adapter.registry 1.0.0; a fixed CompactV2 default or an old Registry receipt does not select that lineage. This minimal checkout does not bundle the adapter, live application Host or configured release coordinator. Do not invent a generic publish command from an engineering deployment example.

For retained-source repair, preserve the release and content commitment, verify all bytes, refresh permitted descriptors and regenerate directory receipt hashes. Check the actual isolated browser runtime and Service Worker. Keep publisher authorization, current-name binding, finality and authenticated save/export/restore as separate results; an unavailable wallet or test space must remain an explicit acceptance gap.

The complete Skill targets KTAPEOUT 0.5.0. Before applying it, read the developer documentation entry, the capability status, and the protocol page relevant to the task. The architecture authority order is: normative specification and schemas; shipped Core, CLI and tests; then explanatory guidance. Where guidance and the installed CLI differ, follow the installed release and report the mismatch.

Use the Skill as a task router: load only the reference needed for the current task, then follow the supported path Discover → Build → Verify → Publish. For this public candidate, publishing guidance stops at preparation and the external signer/readback boundary. It does not authorize signing, broadcasting, deployment or Mainnet use.

For storage work, read Storage, integrity and retention first, then use Plan and verify application storage on TN10. Keep byte integrity, publisher authorization, chain readback, provider retention and clean-device recovery as separate claims; the public candidate does not bundle a generic storage provider or production recovery service.

For local runtime packaging, use ktape package build. It creates a Shell-loadable static runtime package and rejects hidden files, key material and source maps; it does not upload, sign, broadcast, publish a locator, or activate a release.

KTAPEOUT has one application-development Skill: ktapeout-application-engineering. Its authoritative entrypoint in the full 0.5.0 engineering distribution is:

skills/ktapeout-application-engineering/SKILL.md

Install or provide that complete folder to your assistant, including its references/ and scripts/ resources. Load only references needed for the task. Do not install the former Protocol Skill alongside it.

This minimal public protocol checkout does not bundle the engineering Skill, Studio or Native Host. Obtain the complete engineering distribution before using those components; do not assume a protocol checkout exposes them. For public-only work, the engineering Skill provides references/public-checkout-guidance.md for protocol/schema workflows.

Capability and implementation status belongs to docs/reference/capabilities-and-status.md in the engineering distribution. The Skill supplies workflow and routing; plans and local tests do not establish wallet support, admission or live recovery.

The engineering source tree has an unadmitted authenticated archive-verification candidate that reuses the Operation Batch scope digest and pinned Native adapters. It is not part of the signed 0.5.0 contract or a production recovery path; consult the current capability status and do not infer chain inclusion or clean-device availability from archive verification.

For private persistent applications, the full engineering Skill's references/private-persistent-apps.md requires exact canonical-byte budgeting for encrypted directories and a versioned bounded page-tree design when a single snapshot's lifetime growth approaches its byte limit. This public source candidate includes a bounded Rust verifier that recomputes the decrypted V2 tree structure and commitments. It does not authenticate receipts, transactions, predecessor/CAS state or selected-chain inclusion. The full Operation planner, trusted Host, wallet and archive-source integration remain outside this package; local structural verification does not establish production admission or live recovery.

The separate SITE/Cloudflare Web Shell has a browser-local exact Runtime digest TOFU review for routes without a configured publisher policy. It prompts on first use and any changed release identity. This is only a user review aid: it does not authenticate the publisher, release ordering, on-chain binding or protect against compromise of the SITE origin. It does not enable private Host capabilities; consult the full engineering distribution and current status before relying on any private persistence path.

The full engineering distribution also includes an unadmitted separate MV3 private-client candidate that keeps the pin in extension storage and checks Chrome's actual Runtime-frame sender before using the existing Native Host client. Its pin currently trusts the Runtime URL's digest claim; it does not independently verify loaded bytes, and there is no installed production Native Host or real-browser integration evidence. It does not make private recovery available.