Software architecture

Architecture is the set of decisions that are expensive to change: where the boundaries are, which way dependencies point, and which data each part owns. Make two decisions separately:

• Macro: how the system splits into modules or services, how they communicate, who owns which data, how it deploys.
• Micro: how code is organized inside one module: layers or slices, where use cases, validation and data access live.

The macro decision constrains how modules talk to each other. The micro decision is local: each module can choose its own, because its public boundary protects everyone else.

Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]