dc9fe5834e
ADR-010 (PROPOSED): four data-only frontend hooks following the get_reports precedent - get_settings_cards, get_asset_panels, get_map_overlays, get_asset_presentation - batched as a future contract 0.7.0. Warranty proves asset panels first, measuringtools the rest; accept only after both run on the hooks. Display-label swap Equipment -> Machines across nav, list, form, detail, search, map editor, and settings copy (incl the API-failure fallback nav). Identifiers unchanged: plugin name, tables, /api/equipment, asset type, and routes all stay. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Architecture Decision Records
Each ADR captures a single architectural decision: the context, the decision itself, the consequences, and the alternatives considered. ADRs are immutable once accepted. Superseded ADRs stay in this folder with a pointer to the newer ADR.
Status definitions
- PROPOSED: drafted, awaiting decision
- ACCEPTED: decision is in effect
- SUPERSEDED: replaced by a later ADR (link forward)
- DEPRECATED: no longer in effect, no replacement
Index
| ADR | Title | Status |
|---|---|---|
| 001 | Asset model is the platform contract | ACCEPTED |
| 002 | Plugin contract versioning (semver) | ACCEPTED |
| 003 | Plugin distribution model | ACCEPTED |
| 004 | Deployment topology (per-site instances) | ACCEPTED |
| 005 | Equipment vs measuringtools plugin scope | ACCEPTED |
| 006 | Plugin collector contract pattern | ACCEPTED |
| 007 | Product versioning and releases | ACCEPTED |
| 008 | Plugin migration ownership (per-plugin chains) | ACCEPTED |
| 009 | Frontend plugin route gating | ACCEPTED |
| 010 | Frontend plugin hook contract | PROPOSED |
Authoring
When proposing a new decision, copy the most recent ADR as a template, increment the number, and update this index. Do not edit accepted ADRs in place; supersede them with a new one.