The same confusion runs through questions of permission. A design that is technically feasible may still be legally prohibited. A direction that is mandated by policy is not thereby made physically possible. Treating what is merely permitted as if it were obligatory, or what is impossible as if it were merely prohibited, produces a specific kind of argument, one that cannot be resolved by adding more information, because the parties are applying different kinds of constraint.

Modalities name these categories precisely. They describe the different kinds of conditions that can govern what may, must, or can be part of strategy, design, architecture, and Interweave.

Note: There are no ready-made recipes in this article. It is intended for readers who wish to understand the foundations of strategy, design, architecture, and Interweave.

What Is Modality?

A modality is the mode or manner in which something exists, occurs, or is expressed. In the context of strategy, design, architecture, and Interweave, modalities describe conditions.

Where an attitude belongs to an agent, it is held, ascribed, or performed; a modality belongs to the constraint. It answers the question: what kind of condition does this place on the work? Is it logically or physically necessary? Is it normatively obligatory? Is it merely permitted, or is it prohibited altogether? Is it contingently true — it is so, but could have been otherwise?

Modalities serve as qualifiers. They add precision to conversations and descriptions by making explicit which constraint is in play. Without them, the phrase "this must be done" can mean a logical necessity, a physical constraint, an authority-backed mandate, or nothing more than a strong preference, and the appropriate response to each is entirely different.

The Deontic Modalities

Deontic modalities concern what is permitted, required, or forbidden. They are the modalities of norms, governance, and authority, the constraints that arise not from the nature of things but from the rules, regulations, and decisions of institutions and decision-makers. They are particularly relevant in regulated and governed environments, where architectural decisions carry compliance implications.

• Obligatory: Something that is required, mandated, must be included or considered (physically, logically, morally, or legally bound to do).
• Non-Obligatory: Something that is not required or mandated. It is optional; there is no duty to implement or follow them, though they may still be chosen (free from obligation).
• Permitted: Something is allowed or acceptable to implement; authorisation exists even if not required (having permission).
• Prohibited: Something is forbidden or not allowed to be implemented; there are rules, constraints, or policies preventing it (expressly forbidden or banned).

The Alethic Modalities

Alethic modalities concern truth, possibility, and necessity, what is logically or physically possible, regardless of what is permitted or intended. They are the modalities of reality itself: the constraints that hold not because anyone decided they should, but because the nature of systems, logic, or physical law makes them so.

• Necessary: Fundamentally required for the system to exist, function, or be true. Removing it would violate a core constraint (cannot be removed without breaking the system).
• Non-Necessary: The system can exist or function without it. Not logically or physically required (the system remains coherent without it).
• Possible: Can be true or implemented within given constraints, context, technology, budget, physical laws. It is achievable (nothing in reality prevents it).
• Impossible: Cannot be true or implemented regardless of effort. A fundamental constraint prevents it (ruled out by logic, physics, or the nature of the system).
• Contingent: True for the current system, but could have been otherwise. Its status depends on specific choices made during design or implementation, not on necessity (true now, but a different design could have made it otherwise).

Why This Matters

Many arguments about strategy, design, architecture, and Interweave are arguments about modality without either party realising it. A developer who says "we cannot do this" may mean it is technically impossible (alethic) or that it violates a regulation (deontic). A director who says "this is required" may mean it is logically necessary or that it is mandated by authority. An architect who says "this is permitted" may mean it passes regulatory review or simply that no technical constraint prevents it. None of these is the same claim, and they require entirely different responses.

The confusion compounds when alethic and deontic constraints are conflated. What is physically impossible is not merely prohibited, no authority can make it possible by lifting a prohibition. What is normatively obligatory is not thereby made physically necessary, the obligation can be changed, the physical constraint cannot. Keeping these categories distinct is not a philosophical nicety. It is the prerequisite for honest conversation about what is actually constraining the work, and who has the authority to change it.

Naming modalities does not reduce the complexity of the work. It makes the distinctions explicit, precise, and negotiable, or, where they are not negotiable, it makes clear why.

The deontic and alethic modalities described here set the constraints within which strategy, design, architecture, and Interweave operate. The companion article Beyond Blueprints — Attitudes addresses how agents hold stances toward that work, including the full Evolutionary Attitudes arc through which work passes from consideration to realisation, sensing, and interpretation. Both articles complement the three manifestations of knowledge explored in Beyond Blueprints — Manifestations.

Anders W. Tell — Senior Enterprise Architect and Master Interweaver

• Interweawing
• Enterprise Architecture
• Book of Interweaving
• Architectural Thinking