Tool registry

Free Canadian small business workbook

Tool Registry Planning Template

A worksheet for defining read tools, write tools, approval-gated tools, schemas, permissions, fallbacks, and receipts.

7 pages · PDF workbook · No email required

Actual working-record worksheet from the Tool Registry Planning Template, page 3 of 7.
Preview all 7 pages Read the complete workbook before downloading.
Preview the complete PDF All 7 pages · Free to explore

Scroll through the full workbook below. Download the PDF for selectable text, printing and your own working copy.

Workbook page 1 of 7. For selectable text, use the free PDF download.
Page 1 of 7
Workbook page 2 of 7. For selectable text, use the free PDF download.
Page 2 of 7
Workbook page 3 of 7. For selectable text, use the free PDF download.
Page 3 of 7
Workbook page 4 of 7. For selectable text, use the free PDF download.
Page 4 of 7
Workbook page 5 of 7. For selectable text, use the free PDF download.
Page 5 of 7
Workbook page 6 of 7. For selectable text, use the free PDF download.
Page 6 of 7
Workbook page 7 of 7. For selectable text, use the free PDF download.
Page 7 of 7

What’s inside

A working guide
for a real decision.

Give agentic workflows a deterministic operating layer so tools carry state, permissions, validation, execution, and evidence. Use this guide to make the operating choice explicit, test it with evidence, and record who owns the next decision.

Who this is for

Teams turning architecture work into a reusable operating artifact.

Bring the people who own the work

Include the workflow owner, a person who performs the work, a reviewer with authority to approve or stop it, and the relevant data or tool owner.

Includes an explainer, working worksheet, three illustrative examples and practical considerations. This is a planning PDF, not prebuilt automation software.

Use it with your own work

Five questions
to work through.

Choose one workflow. Record enough context to support a decision, then use the worksheet to name the owner, evidence and next review.

  1. Read tool

    What state can the system retrieve safely?

  2. Write tool

    What state can the system change, create, send, or assign?

  3. Validation

    What schema, permission, or business rule must pass first?

  4. Approval

    Which actions need human approval before execution?

  5. Receipt

    What result proves the tool completed correctly?

Illustrative examples from the workbook

Where this becomes practical.

Consulting Practice

Register document retrieval

An assistant needs files from the active engagement but must never browse another client workspace.

Independent Retailer

Register stock and supplier tools

Read-only stock checks and purchase-order submission need different authority.

Accounting Practice

Register calculation tools

A model should call a verified calculation service rather than improvise arithmetic in prose.

AI-supported role
Choose only approved tools, pass validated inputs, and attach execution receipts to the workflow.
Human authority
Tool owners set permissions, test failure modes, and approve consequential writes.
What to measure
Count rejected calls, tool failures, unlogged actions, retries, and permission changes.

Illustrative scenarios, not client results or a promise of performance. The workbook includes additional case-specific prompts.

A useful first step

Use the workbook.
Bring us the next question.

Download and use it without booking a call. If you want help applying it, email Chris with the workflow you’re considering and what you want to improve.

Discuss your workflow

Further reading in the library

General operational guidance only. These resources are not legal, privacy, cybersecurity or regulatory advice.