No books match that search. Try a broader term or clear the search.
Turning the metaphor into an operating model
The book is the unit of design.
A book can be a charter, policy, playbook, workflow, register, data contract, or enforced control. Each has an accountable owner and an approved scope. Agents draw from several shelves for a task; knowledge, governance, security, and learning connect the whole bookcase.
Where your original items moved
| Starting item | Placement in this model | Reason |
|---|---|---|
| Mission & vision | Founding | They express enduring intent; strategy describes choices for achieving it. |
| Codes of conduct | Governance | They set behavioral boundaries for decisions and execution. |
| Finance | Strategy → Management → Execution | Financial direction, operating budgets, and transactions need distinct artifacts. Spending authority sits in Governance. |
| Procurement | Strategy → Governance → Execution | Separate sourcing choices, purchasing rules, and the procure-to-pay process. |
| Roles & departments | Management; connected to Execution | The organization assigns ownership and mandates; processes describe the work. |
| Monitoring | Management, Agent capabilities, Infrastructure | Business performance, agent evaluations, and runtime telemetry answer different questions. |
| Storage | Infrastructure; connected to Knowledge | Storage holds bytes and records. Knowledge defines meaning, authority, freshness, and appropriate use. |
| Tools & endpoints | Integration & systems | These expose capabilities. Runtime access, secrets, and network controls sit in Infrastructure. |
How the loop works: approved intent and rules guide work. Actions produce results and evidence. Reviews turn that evidence into proposed changes, which follow the decision rights and controls set by Governance.