KTAPEOUT

Developer starting point

Bring an idea. Leave with a path.

KTAPEOUT keeps the first version small: discover a compatible Profile, compose a Recipe and Runtime, then verify the result before any wallet or network action.

01 · Workflow

Four steps from idea to publication

  1. Step 01

    Describe

    Write down the state, inputs, outputs, authorities, and what must never happen.

    source-manifest.json

  2. Step 02

    Compose

    Select Profiles and a Recipe that match the application's state and settlement shape.

    profile-lock.json

  3. Step 03

    Verify

    Build deterministic artifacts, inspect the resource envelope, run vectors, and reproduce the result.

    artifact-root

  4. Step 04

    Publish

    Choose a walletless or wallet-enabled experience, then cross the explicit Bridge boundary when ready.

    testnet-10

02 · Public entry point

Start with the Rust CLI

Use the JSON-first CLI for reproducible local projects and CI. Local maintenance, genesis-provenance and Studio-handoff commands validate hashes and evidence. Signing and broadcast use an external provider.

FROM THE REPOSITORY ROOT
cargo run --locked -p ktapeout-cli -- init \
  --template StateMachine --network testnet-10 --output ./my-app
cargo run --locked -p ktapeout-cli -- dev workflow \
  ./my-app/workflow.json

03 · The right first project

Start with one state transition

The most useful first application is not the largest one. It is a small state machine whose invariant can be explained in one sentence and verified with a few vectors. The HalfAdder example shows the shape; your application supplies the meaning.

next_state = Profile(artifact, prior_state, input)Open the worked example →

04 · Interaction mode

Choose the user experience, not a protocol fork

Low friction · read and explore

Walletless

Use for public reads, discovery, demos, simulations, and interactions that do not require user authority.

User authority · settlement

Wallet-enabled

Use where a user must authorize a state transition or settlement. Keep signing explicit and visible.

05 · Boundary

Local first. Testnet-oriented. Explicit about the rest.

The public 0.5.0 surface helps developers discover, compose, prepare, inspect, and validate applications. The Bridge can resolve supported live TN10 state in its read-only shell; signing, broadcast, custody, and Mainnet authorization remain separate operational concerns.

A green local check means “the declared artifact is valid.” It does not silently become an L1 admission or a broadcast permission.