EVOLV Configuration Model and Tagcodering

The intended long-term configuration authority for EVOLV is the database-backed tagcodering model.

Role Of Tagcodering

tagcodering is intended to hold:

machine information
asset metadata
runtime configuration
the basis for configuration exchange across edge, site, and central layers

Configuration Direction

flowchart LR
    CFG["Tagcodering"] --> API["Config / Integration API"]
    API --> SITE["Site Layer"]
    SITE --> EDGE["Edge Layer"]
    EDGE --> NODES["EVOLV Node-RED Nodes"]

Architectural Principle

Node-RED flows should consume configuration, not silently become the only source of truth for configuration.

That means EVOLV should move toward:

database-backed machine and asset metadata
versioned configuration flows
controlled rollout from central to site to edge
less duplication between flows and platform data

Current Status

tagcodering already exists partially but still needs more work to behave as the full configuration backbone.

That gap should be treated as platform work, not as a secondary cleanup task.