Draft, validate, and prepare status
The source inventory contains prototype concepts corresponding to draft, validation, and payload preparation. This page intentionally provides no invocation arguments or transaction-shaped example: those details are unreleased and publishing them as a recipe would imply a safety contract that does not exist.
Even an inert-looking prepared payload can be dangerous if its network, nonce, fee, destination, value, expiration, or displayed summary differs from the bytes later signed. Client-side validation also cannot replace consensus-enforced policy or race-safe cap accounting.
What must ship together
Section titled “What must ship together”The pipeline remains unavailable until a tagged release provides an exact schema, SDK support, protocol enforcement, fresh-state reread and simulation, deterministic intent-to-bytes binding, dedicated-key custody, explicit review, replay protection, concurrency tests, durable outbox behavior, and receipt reconciliation.
The hosted Stele MCP remains keyless. The local exact-three lyth_mcp Stele profile remains read/status-only and non-signing. Any future local economic profile is a separate release and remains unavailable until the custody, protocol, approval, and end-to-end gates close.