# Agent use

Read README, boundary-decision and model-spec, then the pinned schema and companion. Inspect the Dimension's trusted configuration and runtime binding before proposing any changes. The model author, installation actor, accountable party, steward and source writer are separate roles; none implies the others.

An unknown, unranked, contested or authority-contested result is a result to preserve. Ask for the missing predicate scope, governance appointment, rule or source evidence. Never choose a winner from arrival order, majority source count, model maintainer identity or a confidence score. Never promote a proposal or inferred owner into an operative record.

Query through a host that authenticates actors, controls the full register, fixes the subject-to-scope mapping and invokes the companion. Do not let an API client supply a policy, receipt clock or reduced assertion list. A historical route is not current permission to notify a person. This library sends nothing and makes no organization decisions.

For native V3, a syntactically valid outer snapshot is insufficient. Check the installed code/schema digests, explicitly validate the stored nested register, and call admit for new live changes. A report that only says “JSON Schema passed” does not establish authority, authorization, truth or publication authenticity.

Treat admit as a host-internal operation. Never return its complete ledger or raw diagnostics to a write-only caller; return a receipt or generic rejection. Catch Denied distinctly from Invalid. Verify new full snapshots extend the trusted prior one. Native facts use the companion runtime identity, with a separate register operator on the envelope and semantic-only WM-XCT-001 reference.