The Periodic Table of AI Architecture: Assigning Clear Roles to Scattered AI Findings
Hugging Face Forums [Unofficial]
April 7, 2026
A Comprehensive Mapping between Quantum vs Semantic Collapse Process is provided below. More detailed explanations each terms may refer to: From Physics to AI Design: A Rosetta Stone for Runtime Architecture - An Ontology-Light Guide to Observer, Structure, Flow, Closure, Trace, and Residual Governance
Physics ↔ AI Design Rosetta Stone
| Observer | Defines what is measurable from a position, apparatus, or frame | Bounded observer | The system only sees through limits of compute, memory, time, tools, and representation |
|---|---|---|---|
| Projection / Measurement | Makes some aspect of a system visible under a chosen setup | Projection path | Prompt frame, retrieval path, schema, toolchain, or decomposition that exposes one structure rather than another |
| State | What the system currently is | Maintained runtime state | The current held object: schema, case state, artifact set, working hypothesis, normalized document state |
| Density (ρ) | How much of something is concentrated / occupied | Held arrangement / maintained structure | What is currently stabilized, loaded, or compactly preserved |
| Phase (S) | Directional organization, relation, or movement geometry | Active flow / directional tension | The way the system is currently moving, coordinating, correcting, or propagating a route |
| Wavefunction / Composite State (Ψ) | Joint description of configuration plus relational dynamics | Composite runtime condition | The combined picture of what is held plus how it is moving |
| Field | Distributed structure over a domain | Distributed runtime influence | Constraints, pressures, or semantics distributed across steps, modules, or artifacts rather than localized in one point |
| Potential | Landscape that shapes motion and preferred directions | Task / viability landscape | What makes some routes easier, harder, cheaper, or more stable than others |
| Force | Push that changes state or motion | Actuation pressure / drive | Goal pressure, correction pressure, routing pressure, closure pressure |
| Flow | Movement through a field or gradient | Runtime navigation | Evidence flow, artifact flow, state transition, route progression |
| Constraint / Boundary | Restricts admissible motion or states | Hard contract / legality boundary | Tool eligibility, schema requirements, policy rules, interface constraints |
| Conservation | What must be preserved under evolution | Invariant preservation | Things the runtime must not silently violate: schema validity, case identity, safety boundary, artifact contract |
| Dissipation | Loss, friction, or irrecoverable expenditure | Cost of movement / structural loss | Drift, degradation, rework, context loss, unstable closure, overhead from bad routing |
| Perturbation | External disturbance to a system | Runtime disturbance | New evidence, contradictory tool output, user shift, API surprise, environment change |
| Stability | Persistence under disturbance | Robust closure | Whether a result remains usable when pressure or context shifts slightly |
| Instability | Small changes grow instead of shrinking | Fragile runtime behavior | A slight mismatch or new fact blows up the route, breaks closure, or triggers cascading drift |
| Attractor | Region toward which trajectories converge | Stable local organization | A repeatedly reused reasoning pattern, route, artifact form, or coordination shape |
| Basin | Region of attraction around an attractor | Regime of easy convergence | Conditions under which a certain skill path or interpretation becomes the default stable route |
| Transition / Phase Transition | Qualitative change of regime | Runtime regime shift | Moving from drafting to verification, from search to synthesis, from cheap closure to escalation |
| Collapse | Reduction from many possibilities to one realized outcome | Closure event | The runtime commits to one stabilized output, route, interpretation, or exportable artifact |
| Decoherence | Loss of phase-consistent superposition into stable classical alternatives | Loss of multi-path coherence | Soft possibilities resolve into one practical route, or unresolved options become unusable as coordinated alternatives |
| Time Variable | The coordinate used to index evolution | Natural runtime clock | Not just token count or wall-clock, but often the coordination episode |
| Tick / Quantum of update | Minimal meaningful unit of evolution under a formalism | Semantic tick / coordination episode | A bounded local episode that begins with a meaningful trigger and ends with transferable closure |
| Trace / Worldline / History | Record of evolution through state space | Irreversible trace ledger | Replayable record of route taken, route rejected, evidence used, closure achieved, residual left behind |
| Scale | Different levels of description | Micro / meso / macro runtime layers | Token step, coordination episode, and long-horizon campaign are different clocks and different control surfaces |
| Coupling | Interaction strength between components | Interdependence between runtime objects | How strongly modules, artifacts, decisions, or tensions affect one another |
| Resonance | Selective amplification under good coupling conditions | Soft recruitment / contextual fit | Which legal options become especially attractive under current context, history, and local need |
| Transport / Current | Directed movement of something through a medium | Artifact / evidence transport | How information, evidence, permissions, or tasks move across cells, tools, and episodes |
| Barrier | Threshold that resists transition | Escalation or route threshold | What prevents premature closure or tool activation until enough support has accumulated |
| Bifurcation | A small parameter shift changes the whole regime structure | Architectural branch point | A small change in context, routing policy, or observer path flips the system into a different behavior family |
The “triple completion” rows
These are architecture grammar.
| Physics-style Family | Semantic / Normative Reading | Control / Accounting Reading | Runtime Reading |
|---|---|---|---|
| Density / Phase / Viability | Name / Dao / Logic | Maintained structure / Active drive / Health gap | Exact / Resonance / Deficit-aware closure |
| State / Flow / Adjudication | Situation / Path / Filter | Held object / Pressure / Viability check | Artifact state / Route pressure / Runtime guard |
| Projection / Tick / Trace | Interpretation path / Closure rhythm / Record | Observer choice / Episode boundary / Replay | Prompt/tool/decomposition / coordination episode / trace ledger |
| Structure / Residual | What became visible / what remains unresolved | Stable usable order / honest leftover gap | Exportable artifact / ambiguity, fragility, conflict packet |
Short reading rule
The table should be read like this:
- not “AI literally is physics”
- but “these physics terms provide a compact vocabulary for recurring AI design roles”
Discussion in the ATmosphere