Current 0.5.0 component model

Compose by meaning

Profiles define bounded semantics. Packages carry verifiable material. Recipes compose components; Runtimes define interaction lanes; Adapters bind supported external shapes.

01 · Project-maintained reference Profiles

Five semantic building blocks

Content · Immutable

ktape.official.profile.content.immutable

Bounded content commitments for reproducible application material.

Package-bound

State · Partitioned

ktape.official.profile.state.partitioned

Independent bounded state objects for composable application semantics.

Composable

Settlement · Value

ktape.official.profile.settlement.value

Explicit value settlement semantics with provider and signer boundaries.

Testnet-oriented

Settlement · Escrow

ktape.official.profile.settlement.escrow

Bounded escrow semantics for supported compositions.

Evidence-gated

Commitment · External

ktape.official.profile.commitment.external

Bounded commitments to externally computed results. The commitment does not make the external computation an L1 execution.

Commitment only

Naming rule

Identity, version and content are separate

New canonical IDs use lowercase ASCII namespaces. Semantic versions live in fields; schema versions describe formats; hashes identify exact content.

Naming reference →

Component boundaries

Use the right object for the right job

A Profile is not a Recipe. A Runtime is not a Profile. An Adapter is not generic L1 authority. These static references are not signed verification results: each use must bind an exact package version and hash, then evaluate its verification evidence. A catalog name is not proof of official status; package, signature, TrustRoot and evidence determine the declared status.

Read the component model →