Authoring flow

Use the current task's owning workflow. This method connects semantic writing and realization without creating another lifecycle, mandatory Plan, or gate.

Integrate against the real baseline

Resolve the exact target, intended behavior, semantic owner, publication owner, observed baseline, success evidence, and available execution and recovery routes. Read and materialize the complete integrated change, then inspect it in its containing surface for duplication, contradiction, hierarchy, terminology, references, and flow. A paraphrase does not prove the actual draft is correct.

When wording is decidable, finish exact replacement text before application or any promotion required by the enclosing workflow. If wording genuinely depends on an implementation or environment that does not yet exist, state its purpose, constraints, and acceptance anchors; complete the exact text after readback makes it decidable. This causal deferral does not defer already decidable prose. Refresh affected comparisons if the baseline changes.

Review and evidence

Choose independent review when concrete semantic risk, ambiguity, interacting rules, or an existing owner requirement makes independent context useful. Materiality alone does not require another reviewer. Reuse sufficient enclosing review. If independence is required, the writer's self-check does not replace it. Recheck materially changed or newly uncertain scope, without repeating completed review solely because a fingerprint changed.

First check the complete text, metadata, local links, package closure, and any machine contracts. Then ask whether a short behavior evaluation can faithfully exercise the changed behavior in the actual workflow. A shared name or file does not establish an identical consumer. A task requiring sustained user participation may be poorly represented by an isolated test. In that case, verify deployment and readback, observe natural use, and keep the untested behavioral claim explicit. A shared global prompt's effect cannot be isolated merely by running another conversation.

Use a faithful evaluation when it resolves material uncertainty within the authorized scope. Record baseline and recovery; use the actual entrypoint or explain the fidelity limits of a substitute. Repair a material failure and recheck affected evidence. Stop broadening checks once the required claims are supported. Add a persistent regression when an observed concrete failure at a stable boundary warrants it and the check catches recurrence more cheaply than real-path evidence; avoid tests that freeze prose or incidental source order.

Realize and report

Apply through the delivery owner, then read back the actual consumer. Honor the user's explicit earlier stopping point. A request to stop at a completed draft does not authorize downstream installation or publication. When delivery belongs to the authorized result, prepared text alone is unfinished.

Present what meaning changed, why, and what evidence supports it in the active conversation. Name the comparison sides: observed baseline versus integrated change for a direct edit; previous delivered draft versus revised draft for an incremental revision; exact approved or promoted text versus installed readback where that owning workflow applies. Organize material differences by judgments the reader can assess, using prose or a comparison table as useful. A link is traceability, not a substitute for explaining the result.

Report any added approval requirement and its actual authorization explicitly. State separately what was authored, published, discovered, and behaviorally observed. Compare the requested purpose with the final result; unresolved required differences retain a next concrete action or boundary. When none remain, say so. Optional improvements are separate from unfinished work.

An unchanged canonical source with a stale deterministic projection normally needs its existing generator and readback, not another semantic draft cycle. Prove the source-to-target relationship and inspect the regenerated effect. Uncertain identity, semantic transformation, or ownership/interface changes return the affected work to integrated authoring.