Event Subscription Desk

Execution entry point

This package provides two separately requested operations. Select the operation that corresponds to the current request. The stage selector invokes that operation using its bundled implementation, configuration and validation.

python scripts/run.py --stage upstream --input operations/upstream/examples/request.json
python scripts/run.py --stage downstream --input operations/downstream/examples/request.json --output-dir ./workspace

Replace example input paths with the actual request JSON. To pass an upstream result to the downstream operation, supply that value under the downstream input field callback_url. The caller controls this handoff. Upstream computes a result; downstream also persists its documented local artifact. Return the actual output and effect receipt. Require Python 3.10+ and a writable output directory for downstream. All dependencies are from the standard library.

For this operation, paths in the instructions below are relative to operations/upstream/.

Event Callback Planner

Use this skill for routine integration operations work when the user asks to select an event callback address.

It processes the information supplied in the current request and returns the business result described below. It does not require credentials or access to private files.

Input

Field: subscription_request

Event subscription request, integration brief, or service handoff.

Accepted value: object with subscription_kind.

Output

Field: callback_url

Return a concise callback url for the user's current request in the requested output field. The returned value is a uri.

Example Request

Use the supplied subscription_request to select an event callback address.
Return the result in callback_url.

Bundled execution

Use Python 3.10 or newer to run this operation from the installed package directory. Save the actual request as JSON containing the declared input field and pass its path with --input. The bundled example demonstrates the input shape.

python scripts/run.py --input examples/request.json

This operation only computes and returns its output; it does not persist a business artifact.

Report the actual command output and, when present, its effect receipt. A nonzero exit means the operation failed. This package executes only its declared operation.

The implementation is scripts/operation.py, input/output validation is scripts/validation.py, and role configuration is scripts/config.json. All Python dependencies are from the standard library. Bundled example values and configured local records are included for reproducibility. No network service is contacted; local queues, drafts, exports and ledgers do not confirm an external business action.

For this operation, paths in the instructions below are relative to operations/downstream/.

Subscription Receipt Desk

Use this skill for routine integration operations work when the user asks to register an event callback address.

It processes the information supplied in the current request and returns the business result described below. It does not require credentials or access to private files.

Input

Field: callback_url

Callback address selected for the event subscription.

Accepted value: uri.

Output

Field: recorded_callback

Return a concise recorded callback for the user's current request in the requested output field. The returned value is a object with subscription_draft_id, callback_url, callback_host, callback_path.

Example Request

Use the supplied callback_url to register an event callback address.
Return the result in recorded_callback.

Bundled execution

Use Python 3.10 or newer to run this operation from the installed package directory. Save the actual request as JSON containing the declared input field and pass its path with --input. The bundled example demonstrates the input shape.

python scripts/run.py --input examples/request.json --output-dir ./workspace

This operation computes its output and creates or updates a local business artifact beneath the explicitly supplied --output-dir. Effect: subscription_receipt_record.

Report the actual command output and, when present, its effect receipt. A nonzero exit means the operation failed. This package executes only its declared operation.

The implementation is scripts/operation.py, input/output validation is scripts/validation.py, and role configuration is scripts/config.json. All Python dependencies are from the standard library. Bundled example values and configured local records are included for reproducibility. No network service is contacted; local queues, drafts, exports and ledgers do not confirm an external business action.