Skip to content

[Governance follow-up] Refactor CheckContext into hook-specific models #129

@radu-mocanu

Description

@radu-mocanu

Follow-up from #120.

CheckContext is currently a broad field bag shared by all lifecycle hooks. This allows invalid hook/payload combinations and narrows structured runtime payloads to strings.

Refactor toward hook-specific context models, e.g.:

  • BeforeAgentContext
  • AfterAgentContext
  • BeforeModelContext
  • AfterModelContext
  • ToolCallContext
  • AfterToolContext

Expose a union type for evaluator input and keep structured payloads structured until explicit evaluator/text extraction logic handles serialization.

Metadata

Metadata

Assignees

Labels

governanceLinks to new governance feature

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions