First Day Reading

1. Read Ecosystem Map.
2. Read Project Boundaries.
3. Pick the project page for your change.
4. For Logidav work, read Logidav Overview, Repository Map, and Queue Model.
5. For Meduse work, choose a catalog journey, then read its architecture and interface map.
6. For Menzzo storefront work, read Magento architecture and follow one product from creation to storefront, then choose a Magento workflow.
7. For incidents, start with Runbooks.

A practical first-day path

Use the reading sequence above to orient yourself, then make the ownership decision explicit before opening code:

1. Name the user-visible behavior or operational outcome you are learning about.
2. Choose the project page that owns that behavior from the project directory. If the symptom crosses systems, use the coverage matrix to see which side has setup, architecture, flow, and runbook evidence.
3. For a Devbox-hosted project, open Devbox Access, select your assigned environment, and follow Devbox Access and Workspace for SSH, editor access, and application URLs. Then read the owning repository's setup instructions; projects outside Devbox use their own documented environment.
4. Trace only the handoffs that matter for the task. Shared flow pages distinguish source-backed steps from documented relationships and unknown contracts.
5. Before running a check, confirm that it is local or otherwise approved for the target system. A command copied from one project may be irrelevant or unsafe in another.

If you have not selected a project yet, start with Ecosystem Map. If you have a bounded change in mind, continue with First Change.