Skip to content

Deterministic tool-call receipt schema for invocation steps #4502

@davidahmann

Description

@davidahmann

Problem

Tool-call evidence is not fully standardized as a deterministic, machine-readable receipt contract across invocation steps.

Expected behavior

  • Invocation tool steps should emit a stable receipt shape suitable for replay/audit automation.

Acceptance criteria

  • Define/implement receipt schema for tool call step metadata.
  • Add tests validating required fields and deterministic serialization behavior.

Validation

  • Unit tests asserting schema presence and stable field expectations.
  • Existing invocation/tool flow tests continue to pass.

Metadata

Metadata

Assignees

No one assigned

    Labels

    tools[Component] This issue is related to tools

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions