# How the guide is organised

Editorial choices for the September 2026 revision. These are the author's choices about the guide, not external evidence for a technical recommendation.

Author: Murali Sid (https://linkedin.com/in/muralisid)
Source: https://www.agenticarchitectureskills.com/library/decisions
Published: 2026-09-18
Updated: 2026-10-15
Licence: CC BY-SA 4.0, https://creativecommons.org/licenses/by-sa/4.0/
Cite as: Murali Sid. How the guide is organised. Agentic Architecture Skills. https://www.agenticarchitectureskills.com/library/decisions

---


## Start with the reader's question [#start-with-the-readers-question]

Business readers begin with a useful task and a measurable result. Architects begin with the enterprise layers and the system around an agent. Both paths explain how to distill model intelligence into an agentic enterprise.

## Keep six clear entrances [#keep-six-clear-entrances]

[Use cases](/use-cases), [Architecture](/architecture), [Intelligence ladder](/ladder), [Knowledge and memory](/memory), [Research](/research), and [Skills](/skills) provide different ways into shared material.

## Use practical industrial examples [#use-practical-industrial-examples]

Power, water, and mining examples anchor the explanations. Department designs and other industry examples remain available. Proposed extensions are distinguished from the author's past project experience.

## Explain with images and progressive detail [#explain-with-images-and-progressive-detail]

Begin with the overall idea, expand a component, and link to technical depth. Each illustration has a text explanation. Phone layouts use readable images and accessible controls.

## Keep evidence separate from proposals [#keep-evidence-separate-from-proposals]

External claims need dated external sources. Vendor reports are identified. Author experiments carry methods and limitations. Existing writing is material to question and improve. It is not proof that a claim is correct.

## Keep the useful depth [#keep-the-useful-depth]

The fourteen layers, seven planes, two boundaries, four protected action areas, ten cross-cutting concerns, and twenty-five technology choices remain available. They are the guide's reference framework, not a claim of universal consensus.

See [how we evaluate evidence](/research/method), [what changed our advice](/research/what-changed), and the [technology decisions](/decisions).