BoxIsModule | A diagram box, package, or file boundary is treated as a module or as proof that a module relation obtains. | Recover the two holons, claim content, boundary, and interface specification; keep the box as representation/publication material and use a direct relation occurrence only after its governing predicate obtains. |
SignatureAsInterface | A signature declaration is treated as implemented compatibility. | Keep signature under A.6.0 and add interface-specification fields only when interface compatibility is being claimed. |
PortAsProof | Matching port or endpoint names are treated as integration proof. | Recover slot specs, protocol or schema, semantic conditions, and evidence, conformance, source relation, or reliance relation named by value. |
FunctionalLinkAsInterface | A functional relation is treated as module boundary. | Keep VP.Functional and add correspondence or allocation only when module allocation or correspondence is being claimed. |
OpenByPublicationOnly | Published interface text is treated as open architecture. | Add substitution policy, conformance expectations, change policy, source or evidence relation, and data or access constraints when those conditions are part of the open-architecture claim; non-module selection, procurement, work, evidence, assurance, gate, mechanism, and decision claims are governed by the patterns named in A.6.M:12. |
TeamBoundaryAsModule | A team boundary, responsibility label, communication boundary, or delivery unit is treated as a module interface. | Recover the admitted Systems, exact system-role kinds and assignments, Work and procedural relations through A.15, A.2, and VP.Procedural; treat VP.AllocationResponsibility only as a cue and cite the direct responsibility predicate or exact missing governor. Add A.6.M only for the declared module-interface relation; use C.29 when a homomorphism-like correspondence claim is being made. |
MoreModulesMeansBetter | More modules, teams, services, threads, or parallel transformation-flow paths are treated as automatic improvement. | Recover serial work, synchronization, communication overhead, shared resources, and bottleneck claims; mathematical speedup or homomorphism claims are governed by C.29, and characteristic tradeoffs are governed by C.31 and C.16. |
PlatformAsKind | A platform label becomes a root kind or quality claim. | Use PlatformGrammarRef and apply subject patterns for quality, measurement, and decision claims. |
StackAsArchitecture | A stack diagram is treated as the architecture itself or as a module-interface relation by label. | Apply C.30.STRAT first; then use C.30 or C.30.ASV for architecture or structural-view use, A.6.M only for a recovered module-interface relation, or ordinary source-label disposition. |