Skip to content

Workflow patterns

Reusable patterns for transforms, diagnostics, comparisons, and evidence-preserving handoffs.

Open Markdown

Start every unfamiliar task with search. Select the smallest set of operations that can answer the question. Inspect their schemas before constructing inputs.

Transforms accept a text artifact shaped as { mediaType, value }. The value remains text even when it contains serialized JSON.

  1. Search for the transform operation.
  2. Build the exact input artifact.
  3. Run the operation with execute.
  4. Parse the output only if the next step needs an object.

Independent public checks can run in parallel within the execution concurrency limit. Keep each result under a descriptive key and retain operation-specific warnings.

const [dns, headers] = await Promise.all([
tamperbox.request({
method: 'POST',
path: '/v1/tools/dns_lookup',
body: { name: 'example.com', type: 'A', resolver: 'google' },
}),
tamperbox.request({
method: 'POST',
path: '/v1/tools/security_headers',
body: { url: 'https://example.com/' },
}),
]);
return { dns, headers };

An operation can feed another when the first output matches the next input contract. A common example decodes a synthetic JWT, then passes its JSON artifact into json_to_yaml.

Keep the first operation’s warning. Decoding still does not verify the signature, issuer, audience, expiry, or trust.

If a probe is partial or unavailable, state what is missing. Do not substitute an invented grade, address, record, or successful check.