Ecosystem Map

The preservation chain keeps original evidence immutable while allowing modernization to iterate safely on derived copies.

flowchart LR
    A["Authorized acquisition"] --> B["Quarantine and intake"]
    B --> C["Immutable original artifacts"]
    B --> M["Provenance, rights and checksums"]
    C --> D["Lossless normalized copy"]
    D --> E["Generated working copy"]
    M --> E

    U["Upstream Git repositories"] --> G["Forgejo pull mirrors"]
    G --> O["Offline bundles and checksums"]
    G --> E

    E --> L["Pinned server/client baseline"]
    L --> T["Build, login and restore tests"]
    T -->|"pass"| R["Verified preservation level"]
    T -->|"fail or unknown"| F["Finding and Forgejo issue"]
    F --> P["Patch, shim or runbook"]
    P --> E

    M --> K["Machine-readable catalog"]
    K --> W["Wiki dashboards and profiles"]
    F --> W
    R --> W

    C --> X["Independent encrypted backups"]
    O --> X
    K --> X
    X --> Y["Scheduled restore drill"]
    Y --> L

Boundary rules

• Originals never flow backward from a working copy.
• Restricted bytes stay outside the public wiki and source repository.
• A Forgejo mirror is one copy; an independently stored, tested bundle is the recovery copy.
• Findings and patches must identify exact artifact IDs and hashes.
• Dashboards summarize catalog evidence; they do not replace it.