Documentation
Glossary
- Artifact
- An engineering file you import: a station backup, a controller application file, an equipment schedule, a register map. Stored by hash, encrypted, never served.
- Assertion
- One fact with one provenance. The unit of the model.
- Binding
- The native address a point can be read at through a connector, with provenance. A station backup supplies BACnet bindings for its proxied points.
- Connector
- A plug-in that reads a live source (BACnet/IP, Modbus, a vendor station). Read-only by type.
- Drift
- Disagreement between the imported engineering, the live controller configuration, and the supervisory representation. Detected by diffing snapshots.
- Edge
- The local runtime: one binary that imports, stores, serves the web app, the API and MCP, and hosts connectors. Works with the WAN unplugged.
- Equipment instance
- One piece of equipment as an individual record of a shared type: its own parameters, relationships and commissioning state, each with a source.
- Importer
- A plug-in that reads a file offline and produces assertions, binding hints, questions and a coverage report. Needs no connection.
- MCP
- Model Context Protocol: a standard way for an assistant to call tools. Archipelago's tools are read-only and scoped.
- Provenance
- Where a fact came from: observed, imported, inferred, or confirmed.
- Question
- An inference below the confidence threshold, or a conflict between sources, queued for a technician with the evidence attached.
- Snapshot
- An immutable, hashed set of assertions plus the hashes of the artifacts it came from.
- Template
- A shared definition per equipment type that renders a view for any instance according to that instance's own data.
- Available, Preview, Planned
- The three status badges. Available: a versioned download exists. Preview: public code, no release. Planned: design only.