Skip to content

[P1] Define a vendor-neutral worker adapter and capability contract #31

Closed

Description

@anthonyandrei

Problem

offload currently exposes AGY-specific launch and model assumptions. grill-with-docs needs to remain vendor-neutral while the secure workflow targets workers from multiple vendors.

Deliverable

Define a small vendor adapter contract for one bounded worker assignment. Keep orchestration, verification, security policy, and lifecycle control in offload.

The contract should cover:

  • worker launch and structured result capture
  • capability and permission discovery
  • model discovery hooks
  • cancellation, wait, and exit status
  • process, worktree, and artifact ownership reporting
  • a normalized result that the orchestrator can verify

Keep the current AGY path as the reference adapter. Do not add vendor-specific instructions to grill-with-docs.

Acceptance criteria

  • The contract uses the repository terms orchestrator, worker, adapter, and execution scope check.
  • Vendor-specific command syntax, output parsing, and model catalog handling stay inside adapters.
  • The adapter receives static assignment constraints and cannot widen tools, permissions, path scope, worktree scope, or cleanup obligations.
  • The normalized result includes status, artifacts, resource identities, and model-selection metadata.
  • A fake adapter exercises success, failure, cancellation, malformed output, and an execution-scope violation.
  • grill-with-docs contains no AGY, Gemini, Codex, Claude, or vendor-model requirement.
  • The root SKILL.md remains below 500 lines; detailed contracts live in supporting documents.

Out of scope

  • Implementing every vendor adapter.
  • Choosing exact vendor models.
  • Replacing the existing verification gates.

Implementation pointers

  • SKILL.md
  • modes/execution.md
  • modes/repo-research.md
  • modes/web-research.md
  • scripts/run-agy-json.ps1
  • scripts/run-agy-json.sh
  • tests/

Verification

Use fake workers and disposable repositories. Verify that an adapter cannot publish an unverified artifact or clean a resource outside its ownership record.

Activity

  1. anthonyandrei commented on Sep 4, 2026

    @anthonyandrei
    OwnerAuthor

    Resolved by PR #39 (#39). The merged implementation covers this issue, and the targeted acceptance tests pass. Closing as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions