Software Repositories

The MED-MFC monitoring and documentation implementation is split into independent repositories with clear ownership boundaries.

flowchart TD
    DOCS[medmfc-docs<br/>System documentation]
    MON[medmfc-monitoring<br/>Central monitoring platform]
    HCMR[medmfc-monitoring-agent-hcmr<br/>HCMR / copernicus01 agent]
    JUNO[medmfc-monitoring-agent-juno<br/>Planned]

    HCMR -->|HTTPS telemetry| MON
    JUNO -.->|Future telemetry| MON
    MON -->|Operational state| DOCS
    HCMR -.->|Implementation reference| DOCS
    JUNO -.->|Future implementation| DOCS

Current repositories

Repository	Role	Runtime
ckalkav/medmfc-docs	System architecture, operations, incidents and roadmap	MkDocs/nginx via Portainer
ckalkav/medmfc-monitoring	Central API, PostgreSQL, S3/MDS validation, dashboard	Docker/Portainer
ckalkav/medmfc-monitoring-agent-hcmr	Passive HCMR/copernicus01 telemetry	Python + systemd on copernicus01
medmfc-monitoring-agent-juno	Planned JUNO telemetry / coordination integration	Not implemented yet

Boundary rule

System-level behavior belongs in medmfc-docs. Component-specific implementation and deployment details belong in the repository that owns that component.

This avoids duplicating source-code documentation while keeping the system architecture understandable without reading the code.