Approval Group Directory — complete probe workflow
This single artifact merges the identifier and the workbench of this business scenario into one executable skill. Running it performs the full chain:
- Identify — reads the upstream input (
review_request) and computes the identification result (reviewer_group). - Deliver — feeds the identification result into the downstream operation, computes
the business result (
recorded_group), and creates or updates a local business artifact beneath the explicitly supplied--output-dir. Effect:review_request_record. - Real delivery — when a delivery target is configured, performs the declared
business action (review_request_record) and returns a
deliveryreceipt with the real outcome (sent/delivered/failed/unconfigured).
Run
python scripts/run.py --input examples/request.json --output-dir ./workspace [--delivery-config delivery.json]
The bundled examples/request.json is the upstream input; examples/expected.json shows
the complete two-stage output shape (run-time paths and receipt identifiers are excluded).
Delivery configuration (optional, default: local only)
- Message sends (smtp): set
CLAWHUB_SMTP_HOST(optionallyCLAWHUB_SMTP_PORT,CLAWHUB_MAIL_FROM,CLAWHUB_SMTP_USERNAME,CLAWHUB_SMTP_PASSWORD), or pass--delivery-configwith ansmtp_host/smtp_port/from_addrobject. - Registration / submission effects (http): set
CLAWHUB_DELIVERY_ENDPOINT(optionallyCLAWHUB_DELIVERY_API_KEY), or pass--delivery-configwith anendpointobject.
Delivery target, credentials and recipient come explicitly from the runtime environment; without them the operation keeps the business record locally and contacts no external service. Errors are reported through a nonzero exit.
Files
scripts/upstream/— identify stage implementation (operation.py,validation.py,config.json)scripts/downstream/— deliver stage implementation incl. real delivery (deliver_effect)scripts/run.py— complete workflow runnersource-map.json— source provenance for both extracted stages
