Understand it

These pages explain how Agni works, grouped by subsystem rather than by the order the pieces were built. Read them in any order. Each stands on its own.

• Projects and designs: naming a design and a set of designs, so “which file is this design” and “whose config applies” stop being guesses.
• Ingestion and IR: readers into one neutral representation, with provenance and maturity tiers.
• Net solving and hierarchy: how implicit connectivity becomes nets, and how the multi-sheet hierarchy walk works.
• Geometry and rendering: the geometry sidecar and the SVG/WebGL renderers.
• Semantic diff: comparing two revisions at the level of meaning, not text.
• Rules and checks: the evaluation model and the rules-assert / analysis-computes boundary.
• Checks contract: the check-result document, and why a run’s evidence is an artifact rather than terminal output.
• Datasheet layer: parameters and source documents as contracts, and the join into checks.
• Web app and presenter: the browser viewer, the mount model, and the presenter contract.
• Web service contract: the Connect services behind agni serve and the contract details a caller has to know.
• Picking and querying: how a reader names an entity in the viewer and what the viewer can then say about it.
• Working in the web client: the edits a new panel takes, and the traps that ship green in CI and broken in the browser.
• Stack and platform: the Go engine, the proto IR, and the boundaries.