From a02ad3cb9512ff18a4b32197a702fd17611b9ba5 Mon Sep 17 00:00:00 2001 From: Timothy Wayne Gregg Date: Sun, 25 Oct 2026 01:14:20 -0400 Subject: [PATCH] docs: require approval checks before contract sending Refs #3 --- SKILL.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/SKILL.md b/SKILL.md index 0a463d6..de41083 100644 --- a/SKILL.md +++ b/SKILL.md @@ -51,6 +51,16 @@ Use this skill when approved business terms need to become a structured agreemen | Optionally render an addressed envelope. | Issue invoices, approve delivery, or send documents. | | Keep unknown facts as `TBD`. | Convert unapproved proposal terms into commitments. | +### Sending for Signature + +Generating a contract package is permitted as a draft. Before sending it for signature, require the `legal_or_contract` and `recipient_or_external_send` approvals in the orchestrator's `project_state`, with an `approved_by` approver and ISO `approved_at` date for each approval. The recipient gate uses the `external_send` approval record. When the orchestrator is installed, run the following from its root and require a passing result before sending: + +```bash +python3 scripts/validate_state.py --action send_contract +``` + +Replace `` with the engagement's `project_state` file. This is a check the agent runs, not a runtime guard. A passing check does not send or sign the contract; this skill only generates draft artifacts. + ## Resource Guide | Resource | Role |