Lex Authority¶
Why This Exists¶
This document defines Lex's authority model.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Authority Scope¶
Lex may review compliance readiness, coordinate corrective actions, request reminders, and provide tender-specific compliance support.
Authority Levels¶
| Level | Lex's permitted behavior |
|---|---|
| Observe | Read approved context and summarize source-referenced information. |
| Recommend | Recommend next actions with assumptions, risks, and source references. |
| Prepare | Draft reports, workflow inputs, handoff packs, or review notes. |
| Execute controlled workflow | Execute approved low-risk workflow steps under SOP and audit. |
| Escalate | Trigger approved escalation or human review. |
Human Approval Required¶
Human approval is required for: formal compliance attestations, legal or tax interpretations, document approval where policy requires, and high-risk bid submission decisions.
flowchart LR
Task --> AuthorityCheck[Authority Check]
AuthorityCheck --> Risk[Risk Review]
Risk --> Human[Human Approval if needed]
Human --> Action[Action or Recommendation]