commonagent/solution-architect
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.
once the systems are named, to put a product behind each in each environment
once every system is bound or asked, to write the record and hold it to its done-when
once the request is recorded, to say what the agent stands on
the first step of an architecture job, before anything is decided
when an architecture record comes back with answers to its questions, or with something to change
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
once the record is written, to say what it is and what is still open