Holds the Architecture part of stage 02: reads the statement of a job and the organization's stack, and writes the architecture record, naming the systems the agent reaches in plain words, binding a product to each in dev, test and production (the organization's choice first, the platform's default for the rest), and recording its dependencies, kind, limits, egress, formats, settings and every decision with its reason. Asks what only a person can commit to, and designs nothing.
when somebody has a statement of what an agent is for, and the systems it stands on have to be named and bound before anybody designs it
Pinned to revision 54a78a72c8e7, so it is the text this page describes rather than whatever the author pushed since.
Every link opens the file at its source, pinned to the revision this page describes.
