For developers
Developer architecture
Implementation notes, design proposals, performance investigations, and build-system records for contributors working on the αLoop codebase.
Developer notes
Implemented architecture
How the current runtime, physics layers, parsers, and symbolic engines are organized.
GammaLoop architecture
Application shell, domain core, state lifecycle, integration and event pipelines, persistence, concurrency, and tests.
Read noteIntegration dashboard architecture
Renderer-neutral status flow, Ratatui terminal ownership, suspend/shutdown behavior, keyboard controls, and verification boundaries.
Read noteUV renormalization architecture
Orchestrator ownership, sign conventions, projections, disconnected composition, and current boundaries.
Read noteSpenso parsing flow
Dispatch, shorthand modes, structure inference, materialization, chain and trace expansion, and parser edge cases.
Read noteSchoonschip network architecture
Entry points, fixed-point execution, opaque parsing, contraction, settings, and comparison with pattern rewriting.
Read noteGammaLoop drawing style migration record
The implemented Typst callback architecture, canonical source locations, and the superseded design sketch that led to it.
Read noteGammaLoop Drawing Architecture
The current GammaLoop/Linnest/Kurvst drawing pipeline, DOT data ownership and style callbacks, with the superseded evaluated-field proposal kept behind an explicit historical boundary.
Read noteSpenso Symbolica Syntax And Rewrite Idioms
Implemented Spenso surface forms, tag-aware builders and patterns, and the Idenso pass boundaries used for static and dynamic algebraic rewrites.
Read noteSpenso implementation architecture
Tensor structures and payloads, direct contraction, network graph/store execution, Symbolica parsing, serialization and ownership boundaries, invariants, and tests.
Read noteIdenso implementation architecture
Representation and symbol initialization, symbolic tensor/network boundaries, rewrite families, Schoonschip execution, feature and serialization limits, index ownership, invariants, and tests.
Read noteIdenso FORM color and Dirac source map
FORM sources, Symbolica and Spenso target patterns, implementation mappings, historical validation commands, and unresolved provenance retained behind the concise public convention contract.
Read noteLinnet implementation architecture
Half-edge storage, subgraph views, mutation and DOT flows, feature and serialization boundaries, invariants, and verification.
Read noteVakint implementation architecture
Topology construction, canonicalization and tensor-reduction flow, backend selection, external-process ownership, persistence boundaries, invariants, and tests.
Read noteDeveloper notes
Design proposals
Possible changes that are deliberately kept separate from the implemented architecture.
GammaLoop architecture roadmap
Candidate service boundaries, cache sessions, pipeline unification, error handling, orchestration, and observability improvements.
Read noteCFF surface-cache ownership
A proposal for expression-local surface ownership, its migration path, invariants, and rejected alternatives.
Read noteDeveloper notes
Engineering investigations
Dated measurements and diagnostic records. Treat their results as experiment context, not timeless API guarantees.
GammaLoop Evaluated-Field Proposal
The superseded proposal for executable Typst fields in DOT drawing data, preserved separately from the maintained callback-based drawing architecture.
Read noteBNL Benchmark Investigation
A 2026-05-25 threshold-subtraction and four-mass integration study whose cards and graph remain, but whose generated states, workspaces, command blocks, and result logs are absent.
Read noteBNL Contraction Order Performance Notes
A 2026-05-27 to 2026-05-28 contraction-order comparison with retained input atoms and example code, but incomplete machine and dependency controls.
Read noteBNL Scalar Alias Capture
An undated four-alias evaluator rendering preserved as a concise provenance page plus a hashed ANSI data artifact instead of 9,500 lines of authored prose.
Read noteThree-Loop aa to aa Performance Smoke
A 2026-06-15 generation and integration smoke record with retained cards, DOTs, scripts, and CSV summaries, explicit missing-state boundaries, and a warning for 400--570 GiB attempts.
Read noteNetwork simplification status
Direct sum contraction behavior, profiling controls, current bottlenecks, reproduction commands, and open experiments.
Read noteSpenso large-input improvement effects
A historical timing matrix whose branch, fixture, test, and environment controls no longer exist in the current checkout.
Read noteSpenso network execution test baseline
An archived test/timeout record with unresolved revision and removed tests; preserved as non-reproducible evidence only.
Read noteBNL evaluator-atom capture
An undated GammaLoop 0.3.3 evaluator-atom output capture retained as non-reproducible BNL performance evidence, with its missing controls made explicit.
Read noteUV scalar profile benchmark notes
A 2026-05-18 dev-optim profiling record for UV scalar tests, preserved with its removed extraction hooks and missing revision controls made explicit.
Read noteCI test failure summary
A 2026-03-25 workspace failure inventory retained as historical triage evidence rather than a current CI status page.
Read noteNetwork execution rebase record
A trace-label-indexed record of changes preserved during the symbolic-network-simplify-v2 rebase, retained as implementation history rather than current guidance.
Read noteRatatui integration dashboard implementation history
The design plan and chronological implementation notes that led to the maintained integration dashboard architecture.
Read noteSuperseded records
Spenso large-expression pathology record
A superseded large-input investigation whose root fixtures and controls are no longer present; retained as historical evidence.
Read noteDeveloper notes
Build system
Contributor-facing architecture for reproducible builds and continuous integration.
Nix and Crane artifact reuse
A living cache-architecture contract embedded in a chronological experiment record, with historical sections explicitly separated.
Read noteDeveloper notes
Documentation system
Quality reviews and improvement plans for the manuals, developer notes, validation, navigation, and publishing pipeline.
Architecture notes
How contributor architecture records are classified, reviewed, scoped, superseded, and kept separate from supported product interfaces.
Read noteDocumentation quality review and improvement plan
A critical review and phased plan for truthful Python/CLI reference, deeper manuals/examples, an integrated corpus, verified developer architecture, and measurable quality gates.
Read noteManual content debt register
A maintained inventory of audience, scientific-explanation, workflow, terminology, result-interpretation, and product-handoff gaps in the authored manuals.
Read noteAPI documentation debt register
A maintained inventory of inaccurate, incomplete, provisional, and example-deficient Rust and Python reference surfaces, with stable IDs and completion conditions.
Read note