Visual models
Diagrams are source-controlled Field Guide artifacts with rendered SVG assets, captions, and doctrine anchors.
This diagram explains the Field Guide architecture itself. It should make clear that the prose surface is not a pile of separate essays. Doctrine provides the internal source field, the semantic garden holds concept...
This diagram gives the memory architecture a publicfacing security shape without exposing implementationheavy vocabulary first. The reader should see that an access request is tested against identity, purpose, boundary...
This compact loop is the reusable visual grammar for the Field Guide method. It keeps the reader from treating observation as raw data capture, interpretation as private opinion, or application as unreviewable output...
This diagram gives the Field Guide a visual anchor for the corrective loop that turns contact with consequence into bounded action. It should prevent the reader from reading the method as a straight project ladder. The...
This diagram supports the Field Guide claim that memory needs boundaries to remain useful. It shows a context handoff as a governed sequence rather than an open link. A requester carries a purpose, the scoped reference...
This diagram gives shape to the difference between connected information and governing warrant. It should help readers see why a raw trace, private note, public draft, doctrine statement, and governing standard cannot...
This diagram keeps the agency story from collapsing into either heroic individual action or monolithic automation. The workflow begins with human or group intent, routes through scaffolded role support, uses tools to...
This diagram makes the boundary crossing visible. A reader should see that digital coordination starts before the dashboard, model, or record. It starts when a situated condition is sensed and turned into a portable...