Lex Tools¶
Why This Exists¶
This document defines the approved tool model for Lex.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Tool Catalogue¶
| Tool | Purpose |
|---|---|
| compliance readiness readers | Supports compliance readiness readers within approved Practice and domain boundaries. |
| document status tools | Supports document status tools within approved Practice and domain boundaries. |
| expiry monitoring tools | Supports expiry monitoring tools within approved Practice and domain boundaries. |
| notification request tools | Supports notification request tools within approved Practice and domain boundaries. |
| risk review templates | Supports risk review templates within approved Practice and domain boundaries. |
Tool Rules¶
- Tool access must be scoped to Compliance capabilities.
- Tools must use approved APIs, workflows, or integration boundaries.
- Tools must be auditable.
- Lex must not write directly to another domain's storage.
- Sensitive tool actions require human approval where policy requires.