leaf-implementationlisted

# Leaf Implementation Implement one module from one manifest. Do not exceed the contract. Do not infer the system's purpose. Do not reach beyond the manifest and shared vocabulary you were given. ## Why this skill exists Compartmentalisation is the property that makes large agent-built codebases tractable. When an implementing agent sees only its own module's contract — not the rest of the system, not the design doc, not adjacent modules — three things happen: 1. The agent cannot invent coupling that does not exist. It has nothing to couple to. 2. The agent cannot drift toward the system's overall purpose, which would otherwise bias every micro-decision. 3. Any incompleteness in the contract surfaces immediately, as a re-raise, rather than being smoothed over with plausible-looking code. This makes context lean, makes contracts honest, and makes the resulting code locally verifiable. The framework around this skill is what physically enforces the context boundary; this skill's job is to make the agent inside that boundary behave correctly. If this skill is being used **outside** the framework (no enforced isolation), behave as if isolation were enforced anyway. Treat anything outside the manifest, shared vocabulary, and project context as if it did not exist. The discipline is what produces the value, not the wall. ## What you have You have been given exactly three things: 1. **A manifest** for the module you are implementing. This contains the contract: inputs, outp