📦Vision Deployment
The Vision Deployment view is a read-only consumer feature. The provisional destination vision.talus.network is retained for a later release and is not a claim that the hosted service is live. The page reads the selected network’s public deployment document and compares visible package, immutable-kernel, shared-root, capability, and network identities with state it can read.
The architecture figure keeps the hosted boundary clear: users can inspect public network evidence, but the Deployment view does not grant package upgrade, runtime, or object mutation authority.
The sequence distinguishes a read comparison from a transaction flow. A missing or unavailable read is not agreement, and a matching row is not proof that a consumer can mutate the object.
Public fields
Network and chain show the deployment’s network label,
chain_id, and on-chainnetwork_id.Kernel shows the immutable kernel package and its publication/immutability transaction evidence.
Packages show the six public package lineages with initial id, storage id, version, UpgradeCap, dependency linkage, publication digest, and comparison state.
Shared roots show ToolRegistry, NetworkAuth, AgentRegistry, LeaderRegistry, priority-fee vault, and RuntimeAuthority object ids with initial shared versions.
Capabilities show the public administrative and runtime capability object ids recorded by the environment artifact.
Token metadata shows the configured external
$USpackage, module, type, treasury cap, and coin metadata when the deployment exposes them.Transactions show package publication and deployment transaction evidence carried by the selected document.
Decoded count distinguishes successfully read rows from unavailable or structurally empty rows.
Search can open a singleton row by id; wrapped objects are resolved through the public owner view when the hosted reader supports that relationship.

Drift states
Matches the chain
Every public binding the document carries agrees with the selected network read
Continue inspecting the relevant Explorer page and transaction effects
N field(s) differ
The document and selected network expose different public values
Re-select the intended network or ask the service provider for a valid deployment URL
Not compared
A public read failed or the active configuration is unset
Treat the result as unavailable, not empty or healthy
The page can also compare package linkage, object id, initial shared version, network id, witness type, and owner-cap references when those values are present. Deployment records explicitly omit protocol, protocol_version, and config_hash. The view does not expose private service configuration, deployment commands, process health, or mutation instructions.
Availability boundary
The retained screenshots and provisional URL do not prove a live service. Use the hosted URL and selected network published by the provider, and rely only on fields visible in the selected build. Historical Protocol rows in the screenshot are not deployment-manifest or effect-authority evidence. When Vision omits RuntimeAuthority or Invocation fields, inspect them through matching CLI/SDK bindings, package IDs, objects, and transaction effects.
Next
Use the Talus Vision Explorer Guide for the Explorer map. When you need to create state, use a wallet-authorized CLI or SDK flow and return here for independent readback.
Last updated

