Table of contents
Infrastructure
Formal definition
An Infrastructure is a sextuple :
where:
- is the substrate — the base category or site; the set of infrastructure objects (histories, servers, contexts, earthworks)
- is the supported practice — the family of objects that depends on ; what enables (fibers, applications, domain logic, trains)
- is the position measurement — a function from substrate objects to a measurement space quantifying where in the substrate each object sits (distance in the principal cycle, configuration state, obligation gap, network capacity)
- is the enabling projection — every supported object lives over a substrate object; is the substrate that runs on
- is the convergence operator — the operation that sends any substrate state to its canonical/reduced/desired form; (idempotent)
- is the installed-base order on — a partial order recording that means can only exist given ; the substrate at any moment is constrained by the substrate at prior moments
Seven invariants. is an infrastructure iff it satisfies:
- Enabling: for every , and cannot be defined without existing. is a necessary condition for .
- Substrate priority: is defined independently of . The definition of any does not reference .
- Transparency in use: when (substrate at a fixed point), the elements of are accessible and agents attend to , not to . The substrate is invisible.
- Visibility upon breakdown: when (substrate not at fixed point), the fibers may be inaccessible or inconsistent, and agents must attend to directly.
- Installed-base constraint: for , the fiber restricts coherently to . New substrate states are compatible with old ones; history is not retracted.
- Substitutability: two substrates are interchangeable for practice iff there exist projections and and an equivalence with . cannot distinguish from through the interface .
- Dependency direction: the only morphisms between and are those of (going from toward ). There are no morphisms from into . Infrastructure never depends on what it supports.
In this system
The relational universe instantiates the infrastructure tuple as:
where:
- — the history site ; the base category whose objects are histories and whose morphisms are prefix extensions
- — the fiber doctrine; the sheaf of nuclear Heyting algebras over ; the practice the infrastructure supports
- — the obligation gap at each history: for a representative ; measures how far the current fiber is from
- — the stalk projection; sends each fiber to its base history ; the enabling projection of the sheaf fibration
- — the joint projection; the convergence operator sending any element to the doubly-quiescent fixed fiber;
- — the prefix order on ; iff is a prefix of ; the installed-base order: the restriction maps for carry old observations forward intact
Transparency / visibility in : when — when the fiber at is fully settled — agents work with elements of without attending to the site. The history site is transparent. When a covering condition fails or a restriction map is missing — when the sheaf axiom is violated — the site becomes visible and must be repaired before the fiber can be used.
In the FARS
The FlatfileAgentialResourceSystemLocale instantiates a second infrastructure layer above :
where:
- — the locale structure: (AGENTS, SOUL, MEMORY, INBOX, PLANS, IDEAS, skills/); the substrate for all agent work
- — the skill library; the morphisms agents invoke; the practice the locale supports
- — the PLANS.md state: which tasks are open, their ordering, their dependency gaps
- — the scoping projection: every skill is scoped to the locale it belongs to
- — the runbook convergence: applying a runbook to the locale’s state converges to the desired output (idempotent when all steps are Process-kind)
- — the git commit order; every state of the locale is a commit; commits are ordered by ancestry; the installed base is the git history
The conceptual gradient
The research tradition gives six framings of infrastructure, each contributing a distinct formal property:
| Tradition | Formal contribution |
|---|---|
| Number theory (Scheidler-Stein) | Near-group with distance function ; quasi-additive composition; = ideal reduction |
| IaC / systems | Dependency DAG; idempotent Apply; desired-state semantics; drift = |
| Software architecture | Dependency direction invariant (7); substitutability via fixed interfaces (6) |
| Category theory | is a Grothendieck fibration; cartesian liftings implement substitutability |
| STS (Star & Ruhleder) | Invariants 3, 4, 5: transparency, visibility-upon-breakdown, installed base |
| Civil engineering | Network structure on ; long asset lifetime; public goods; enabling-without-representing |
The irreducible tension: infrastructure is ontologically prior (must exist before the practice) and functionally posterior (is identified and classified by the practice it supports). Roads are roads because people travel; contexts are contexts because types inhabit them; the history site is infrastructure because the fiber doctrine lives over it. Infrastructure is the enabling background shaped by what it enables.
Open questions
- Whether the near-group structure of number-theoretic infrastructure (quasi-additivity of , bounded deviation from group laws) has a correlate in — whether the obligation gap satisfies a quasi-additivity condition across histories.
- Whether is a morphism of infrastructures over — a map of tuples commuting with and .
- What the correct notion of infrastructure morphism is: a map should preserve the enabling projection and commute with the convergence operator.