C.30:2 - Problem
Engineering teams use “architecture” for several different things:
- the selected structure of a holon;
- a diagram, model, table, dashboard, generated relation graph, or document;
- a module layout;
- a selected transformation-flow structure, flow description, or mathematical graph description;
- a functional, control, information, deployment, logical, or physical structure view;
- an ADR-like publication;
- a project-side claim defined or tested by another FPF pattern.
These uses are all useful in ordinary engineering speech, but they cannot carry the same FPF claim. The core distinction is the one used across FPF: actual subject-relation occurrences; the A.22 structure selected from them; the ArchitectureRelation that may obtain between that structure and one holon; a C.2.1 claim about the holon, relation, or structure; the Description episteme or view; the representation and publication objects; and any project decision about changing architecture are different objects.
The first-minute practitioner asks four questions:
- Are we recovering an actual architecture relation, considering a candidate structure, or only reading a representation?
- For an actual architecture claim, which subject relations obtain and which A.22 structure is selected from them?
- Which structure kind is in view—function, flow, control, module, Work, system-role-kind or assignment, enactor, information, data, placement, deployment, scale, or a declared logical structure—and which adjacent interface, evidence, or assurance relations matter?
- How is the inspected material being used: as claim content, description, view, representation, publication form, decision, source relation, or mathematical lens?
The useful result preserves the distinctions needed by the architecture question. A module diagram may omit a control or flow relation that changes the next action. Conversely, a candidate statement may settle the question before an actual relation or full description is available.