implement

# Implement Execute exactly one bounded experiment described by the resolved bead or caller intent. Implement owns subject edits and factual evidence. It does not create a second planning record or a model-authored candidate packet. ## Workflow 1. Read the intent, acceptance, and scope from their existing source. A runtime may snapshot and hash that source automatically for drift detection. 2. Run the declared first acceptance check before changing behavior. RED-first applies only when acceptance is behavioral: preserve evidence that the check fails for the expected missing behavior. Relocations, doc merges, and pure refactors need no failing-check ritual — record an honest green pre-change baseline instead. 3. Make the smallest in-scope change that satisfies the active behavior. 4. Run the targeted acceptance checks and capture factual results. 5. Refactor only while those checks stay green. Refactoring does not change the acceptance test. 6. Have the runtime derive actual changed paths and `subject-manifest.v1` from the before/after subject. Do not make the model transcribe those facts. 7. Return the manifest digest, author context ID, and exact check receipts in the response or runtime channel. Stop. Specialists such as standards, domain, test, refactor, and security may provide advice. They are never hard dependencies and cannot add lifecycle authority. ## Evidence proportionality During edits, run the smallest deterministic checks that can f...