Page:
README
Pages
ADR 001 asset as platform contract
ADR 002 plugin versioning
ADR 003 plugin distribution
ADR 004 deployment topology
ADR 005 equipment vs measuringtools
ADR 006 collector contract
ADR 007 product versioning and releases
ADR 008 plugin migration ownership
ADR 009 frontend plugin gating
ADR 010 frontend plugin hooks
ADR 011 machines rename
ADR 012 geenforce manifest ownership
BACKUP RESTORE
COLLECTOR INTEGRATION
CONFIG
CONTRACT STABILITY
DEPLOY WINDOWS IIS
DEPLOY
GE ENFORCE CLIENT
GE ENFORCE DEPLOY
GE ENFORCE
Home
IMPORT ADOPTION
IMPORT API
INSTALL WINDOWS IIS
PILOT DEPLOY
PLUGIN EXTERNAL REPO
PLUGIN GUIDE
PLUGIN HOOKS
PLUGIN QUICKSTART
PLUGINS
PROPOSAL ge enforce plugin
README
ROADMAP
UPGRADE
Clone
1
README
Cameron Proudlock edited this page 2026-07-13 19:51:21 -04:00
Table of Contents
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 | ACCEPTED |
| 011 | Machines rename + modeltypes retyping | ACCEPTED |
| 012 | GE-Enforce manifest ownership in shopdb | ACCEPTED |
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.
Docs
Install and operate
Data import
Plugins
Integrations
Project
ADRs
- ADR-001-asset-as-platform-contract
- ADR-002-plugin-versioning
- ADR-003-plugin-distribution
- ADR-004-deployment-topology
- ADR-005-equipment-vs-measuringtools
- ADR-006-collector-contract
- ADR-007-product-versioning-and-releases
- ADR-008-plugin-migration-ownership
- ADR-009-frontend-plugin-gating
- ADR-010-frontend-plugin-hooks
- ADR-011-machines-rename
- ADR-012-geenforce-manifest-ownership
- README
Proposals