Explanation¶

Explanations are understanding-oriented. They clarify and illuminate the design decisions, architecture, and concepts behind imarina-load-researchers.

• Architecture overview — why the pipeline is five independent commands talking only through a filesystem convention.
• How build matches researchers between A3 and iMarina — the update algorithm behind each generated file.
• The end-to-end workflow — the full, human-and-system journey from a submitted request to a published file.
• Data protection and GDPR — purpose limitation, data minimization and the storage-limitation gap this design still has.
• Secrets and credentials — why credentials are read through one cascading function instead of per-environment code.
• Why filenames encode dates — the "latest file" convention this pipeline relies on throughout, and its one exception.