Infrastructure

Every module has a page here with the same sections: what it does, run it yourself, test, call. The pages are generated from modules.json, the same file the Infrastructure page builds its catalogue from: state, evidence, source and release are there, the how is here.

Two pages apply to all modules: All at once starts the whole chain with one command, Choose modules for a purpose names the smallest set for six common purposes.

Pages in this section

• Dependencies Which module needs which, as a figure and as a list.
• Choose modules for a purpose You do not have to take everything: six common purposes and the modules that suffice.
• All at once: the whole chain locally Gateway, domain servers, API, website and checker from one checkout with one command.
• A2A-Agent The agent-to-agent door: named capabilities on request, not conversation.
• API-Spine The machine-readable spine (OpenAPI) behind this website's facades.
• Gedächtnis (Memory) The platform's versioned fact memory, permission-checked on every access.
• MCP-Gateway The platform's machine door: the same tools over MCP and a JSON shell — 52 capabilities from two domains — with a call budget and typed refusals.
• Politikdaten-Engine The own build over the Federal Chancellery's public LINDAS endpoint: popular votes per canton with the Ständemehr, referendum bills, popular initiatives, the Federal Council and National Council elections — 44 cubes, every figure with its provenance.
• Prüfwerkzeug (oh-check) Probes entries live against their declared endpoints; its measurements are what the entry page shows — passed, failed and «never checked» as distinct states.
• Registry-Standard The manifest standard, schemas, ontology and context the directory stands on.
• Skills Capability building blocks for agent workflows.
• fedlex-Engine The own build over the Confederation's public Fedlex endpoint: SR numbers, versions, article texts — every answer with provenance. The first built area.