Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:10:20 UTC

C.30:10 - Rationale

An architecture question concerns how a holon is organized and what a proposed change would affect. ArchitectureRelation connects the holon to a selected structure; ArchitectureClaim can assert, deny, leave unresolved or propose that organization. Keeping these separate lets a candidate guide work before realization, and lets an actual change be distinguished from a new description of the same organization.

C.30 and C.30.ASV establish an FPF architecture kernel: actual subject relations first; selected A.22 structure; ArchitectureRelation to the described holon; separately constituted claim, description, viewpoint, and view epistemes; structure-kind discipline; correspondence and source-return boundaries; and characteristic-claim applications. They do not by themselves provide full measurement, synthesis, decision, causal proof, safety proof, or assurance.

Architecture discussions often need one immediate result: name the holon, choose the structure kind under consideration, recover the use of inspected material, identify the pattern for any separate evidence or assurance claim, or stop. One or two ordinary sentences can suffice, including for retention or handoff. A fuller description earns its cost when the receiving action needs subject, correspondence, view or use conditions that the short account does not supply.

Episteme identity and direct view conformance also preserve plurality. The same holon, architecture-relation occurrence, or selected structure may be described by several independently identified epistemes; one episteme may conform to several viewpoints through distinct occurrences; several publications may render one description. C.30 keeps those variants usable without turning any publication form into architecture or any bundle or list into view membership.