Automation · private app source · not marketplace published

Equivalent decision semantics for Make.

The repository contains five custom-app modules, five JSON blueprints and one integrity-manifested authenticated-QA handoff for the same commercial solutions as n8n. Make connections must be recreated after blueprint import.

Ten-minute setup after owner installation

01
Create the private app
An authorized Make team owner verifies the handoff hash, then imports the base, connection and five module definitions in the documented order. This account-bound step is not performed automatically.
02
Import a blueprint
Create a scenario, choose Import blueprint, select one file from integrations/make/blueprints, and recreate the connection with the RunOnProof HTTPS URL and API token.
03
Replace synthetic inputs
Supply the exact request body, its SHA-256 digest, a correlation ID and a stable idempotency key. Keep scheduling and automatic retries off.
04
Run and inspect
PROCEED is policy-limited. REVIEW and UNKNOWN explicitly block continuation for human approval. STOP terminates.

HTTP 402 is a structured REVIEW result.

The module accepts the quote response without forwarding payment proof, signing, settling or enabling an economic continuation. Importing a blueprint buys nothing.

Remove

Deactivate/delete the scenarios and connection, remove the private app or its invite access, and apply your execution-retention policy.

Current limit:

Native import and Make DevTool QA require an authenticated team owner. No account was accessed and no app was created, invited, submitted, reviewed or published by this foundation.