harmony/MISSION.md

Mission: Learn the Harmony Codebase

Why

Learn Harmony well enough to contribute small, correct changes that preserve its architecture: typed infrastructure-as-code, Score-Topology-Interpret, and minimal implementation discipline.

Success looks like

• Trace a change request to the right crate and owning module.
• Explain whether a change belongs in a Score, Topology capability, adapter, deploy crate, CLI, or test harness.
• Make a small change and choose a focused verification command.
• Avoid architectural regressions such as handrolled manifests outside Scores or speculative abstractions.

Constraints

• Prefer short, code-grounded lessons over broad surveys.
• Use repository docs and source as primary material.
• Keep exercises practical for future contribution work.

Out of scope

• Becoming expert in every provider backend at once.
• Deep fleet-agent or hardware-discovery internals until the core contribution workflow is clear.