Reference approval controls what ToolCustody knows about assets and permitted tasks. Gather approved identities, families, capabilities, service requirements, alternatives, time policies and return positions before editing.
Save the intended catalogue
The Author opens References and policies and edits the Reference draft. Use the guided forms for supported ordinary entries or Advanced JSON for the complete definition. Keep exact codes stable. Asset identity and type cannot be casually reassigned through a later metadata release.
Define task family permissions, explicit alternative assets, required capabilities and qualification scope. Keep approved permitted use separate from due-back timing. Return policy must identify the correct review position. Do not infer suitability from a descriptive name or invent a tag that asserts engineering equivalence.
Choose Save a new draft revision and inspect the retained revision. If the page has unsaved or stale content, explicitly reload or save through the offered path before proving. A browser's current text is not automatically the saved proof input.
Write expected situations
Under Check examples and approve the release, supply at least two real situations and their independently expected outcomes. Exercise allowed and refused decisions and each relevant policy stage. Use Advanced JSON examples for return and oversight situations not covered by the simple task form.
Run the proof and inspect its saved results. Correct a disagreement against the approved business method. Do not change expectations just to accept current output. Hard issue checks remain separate and cannot be weakened by an apparently permissive condition.
Activate the unchanged revision
The Reviewer checks the catalogue, examples and proof, enters the Activation reason and uses Activate this unchanged proved revision after recent Accounts authentication.
Activation refuses stale proof, changed positions, changed active release or changed authority. The site's distinct-reviewer setting can also refuse the author or last editor. Where same-person native review is permitted, history records it; additional enrolled review restrictions can be stricter.
Check operational consequences
After activation, check the active release and tell the Supervisor about changed assets and tasks. An asset omitted from a new approved register can become inactive; a metadata change on a loan can require use review. Neither event performs a return or clears a hold.
New assets still need opening custody. Handle a refused or uncertain activation through the current saved state and original request, rather than repeatedly approving an old tab.
Review a plain English proposal
When connected at a real site, Prepare a condition in plain English works on an existing rule whose approved outcome is already defined. Choose Existing rule slot and check Approved outcome, describe When should this rule apply? and use Prepare a condition. Attempted provider calls use the organisation's authoring allowance.
Read the returned restatement, condition and diagnostics. Adopt this condition into the unchanged draft is available only for an eligible proposal. Adoption changes the saved draft condition; it does not replace proof or Reviewer activation. If the draft has unsaved changes, settle those through the page's save or reload controls first.
If the reply is uncertain, keep Original attempt and use Check the original authoring attempt. Do not start a second provider request to replace an unknown result. Structured editing and proof remain available without a model connection; the practice site does not contact a provider.