MES+0
MES backend for the edge agent
the MES backend speaks to the laraplate-edge agent as the edge agent spec fixes it: machine sources authenticate through service accounts and api permissions, the ingest route follows the CRUD nomenclature, each source receives a versioned configuration document and records the agent's apply reports, and data the agent dropped becomes a visible incident.
Tasks.
- Task 1: Sources on service accounts4/4
- Task 2: Ingest on the CRUD route through the service account4/4
- Task 3: Losses and the new incident types3/3
- Task 4: Configuration delivery5/5
- Task 5: Filament section on the source page3/3
- Task 6: Documentation and closing2/2