This archive is a structured body of work on software architecture as a constraint discipline.
The essays are ordered by conceptual dependency, not publication date. Together they describe the structural conditions required for systems to remain knowable over time.
The corpus is substrate-independent. It describes structural conditions for system knowability, not failures of any specific reasoning mechanism.
For applied essays examining contemporary systems through this lens, see Applied Architecture.
Foundations
- Taxonomy Formal vocabulary used throughout the corpus. Defines constraint, invariant space, enforcement, knowability, translation surfaces, composition, and collapse.
- Knowability Knowability is the preserved ability of a system to justify its behavior through enforceable constraints across time and composition.
Corpus Spine
Read in order.
Knowability Knowability is the preserved ability of a system to justify its behavior through enforceable constraints across time and composition.
Architecture as Practiced Constraint Establishes architecture as lived constraint rather than diagram or framework.
Dependency Management as Constraint Discipline Dependency management is the preservation of invariant space across time and external constraint surfaces.
Reproducibility Formalizes the epistemic floor required to re-establish constraint.
Testability as Epistemic Authority Defines how correctness is enforced rather than inferred.
The Additive Fallacy Explores why locally correct systems fail when composed without preserving constraint.
Systems That Lie Examines what happens when systems lose the ability to justify themselves.
Distributed Truth (Planned) Extends constraint preservation into distributed systems under partial failure.
Inference as Governance (Planned) Examines the structural shift when probabilistic systems move from advisory signal to governing constraint surface.