Skip to content
TCAFTask-Contract AI Development Framework
TCAF 0.3.3

Universal Run Protocol

Understand the versioned Run Envelope that binds one operation, target, adapter and instruction surface.

Content: completeWorkflow: verified

Every TCAF operation resolves through the Universal Run Protocol. The runner converts a public operation or agent ID into one versioned Run Envelope for one bound target.

Resolution path

operation
→ registry
→ agent manifest
→ required and optional modules
→ one target
→ one adapter
→ Run Envelope
→ developer review gate

Framework instructions and target evidence remain labelled and separate.

Envelope fields

A Run Envelope contains:

  • run_protocol_version — protocol version used by the runner;
  • framework_version — active TCAF runtime version;
  • operation — public operation being performed;
  • agent_id — resolved registered agent;
  • manifest — resolved agent manifest path;
  • adapter — adapter ID, transport, direct-access flags and native-verification state;
  • target — one bound target and its kind;
  • input.request — optional inline request;
  • input.resource — optional bound file, directory, archive or host resource;
  • instruction_modules — labelled framework and target modules with roles and sources;
  • unresolved_optional_target_roles — expected target evidence not found and not replaced by a fallback;
  • directive — final execution rule and review-gate requirement.

Instruction modules

The runner loads, in declared order:

  1. agent instructions;
  2. entrypoint;
  3. output schema;
  4. required core modules;
  5. resolved project-role documents or declared fallbacks;
  6. explicitly selected optional context;
  7. one adapter module.

The host must use only the labelled instruction surface. Target modules are evidence, not framework rules.

Target binding

A run binds exactly one target. The adapter cannot silently switch repositories or broaden the workspace. When a required target role cannot be resolved, the envelope reports it or uses only the fallback declared by the manifest.

Adapter metadata

The envelope makes transport limitations visible, including whether native invocation was verified. A manual transport can carry the same core rules without pretending to have direct target or edit access.

Review gate

The directive requires the host to stop at the developer review gate. Generating or transporting an envelope is not approval to implement, commit or publish.

Markdown and JSON

Markdown output is optimized for manual transport and preserves module boundaries with explicit comments. JSON output is intended for integrations and contains the same logical envelope.