Algebraic Architecture Theory / Software Field Theory

Software architecture as a formal object of change.

This site is the public home for AAT, SFT, and ArchSig: a research program for reasoning about architecture operations, invariant preservation, obstruction witnesses, signature trajectories, and bounded software evolution.

Research

Four entry points, one claim discipline.

Algebraic Architecture Theory

AAT decomposes design judgment into architecture objects, operations, invariant families, obstruction witnesses, architecture signatures, and theorem boundaries.

Read the AAT pages

AAT / SFT Interface

The interface fixes the direction of dependency: AAT provides local algebra, while SFT uses that algebra as architecture projections, observables, local law premises, and claim boundaries.

Read the interface

Software Field Theory

SFT treats software evolution as bounded computation over field models, operation support, policy, forecast cones, consequence envelopes, and feedback updates.

Read the SFT pages

ArchSig

ArchSig connects repository artifacts to measurable signature axes, witness candidates, theorem precondition reports, and explicit non-conclusions.

Read the ArchSig manual

Reading paths

The nav follows the intended sequence.

The top-level pages are not independent slogans. They form the public reading route from formal architecture theory, through the AAT-to-SFT interface, into field-shaped software evolution and bounded observation artifacts.

For theory readers Start with AAT, then read the chapter clusters and Lean status. For boundary readers Use the interface before translating AAT claims into SFT terms. For SFT readers Read SFT after the dependency and claim boundary are explicit. For tooling readers Use ArchSig as measurement and reporting, not theorem promotion. For public articles Route outreach essays back to the canonical English pages. For maintainer context Use the profile for author identity, contact routes, and publication boundary.

Canonical sources

Primary claims still live with the repository.

The public website is a reading surface. Repository documents remain the source of truth for definitions, proof status, tooling boundaries, and empirical hypotheses.

Research Goal Program overview and boundary discipline AAT Mathematical Theory Objects, operations, invariants, witnesses, and signatures AAT / SFT Interface One-way dependency, translation rules, and forbidden readings SFT Monograph Computable software evolution, forecast boundaries, and governance Lean Theorem Index Implemented API and proved declarations Proof Obligations Future proof work and empirical hypotheses

Outreach

Articles point back to the canonical theory.

Hashnode, Zenn, Qiita, and other essays should act as entry points. Formal claims, theorem status, and empirical boundaries remain in the repository documents.

Outreach hub Outreach drafts Hashnode MVP draft

Author

Profile

The public profile records the maintainer identity, repository contact routes, and publication boundary for the AAT / SFT research program.

Read the profile