Skip to content

Capabilities — admit one typed non-model service #42

Closed as not planned
Closed as not planned

Description

@zenithruneblade

Planning representation replaced — 6 November 2026. The accepted Typed services and extension authoring outcome is retained in #62. Reopen one bounded task when selected. This closure does not mean the capability is complete or cancelled. The original scope and evidence below remain preserved; current selected work starts at #52.


Make one service discoverable and callable without pretending it is a chat model.

Starting point: Current delivery: general interface/profile declarations and call/job/session grants remain designed.

First working slice

  • Define one exact interface/profile, typed demand and Rune contribution; preserve the existing model path as explicit compatibility.
  • Register one bounded CallGrant driver with fresh capability observations, admission checks and lease cleanup; expose only its typed operation.
  • Verify incompatible demand, unknown/stale readiness, unauthorized use and cancellation fail cleanly; record one controlled end-to-end service call.

Connections: Extends #1/#7/#21 and shares readiness with #6. #22 owns durable job attempts; domain providers still authorize their own effects.

Later: #51 owns the first crawl provider's JobGrant registration/driver extension, backed by #22's durable attempts. SessionGrant, additional domains and broader placement remain separate follow-ups.

References: ADR 22 · ADR 14.

First modality consumers: #48 Echo and #49 Vision; #50 verifies their shared runtime handoffs before #16/#17 resource and ranking policies.

Contribution entry: Contribute one exact service interface and controlled CallGrant driver.
Open decision: Use #48's bounded local transcription path as the candidate first non-model service consumer. Agree its exact interface/profile, typed input/output, cancellation and Rune contribution with #21/#48 before implementing the driver. Reuse the agreed profile in #50. Runtime/version and media limits remain explicit decisions; broader grant families remain follow-ups.
Verification: Demand/admission/cancellation fixtures and one bounded service call. Shared contribution and touched-docs rules: #52.

Activity

  1. added
    area:runtimeAgents, Graph, dispatch, orchestration, capabilities and workers.
    needs-designAn issue-specific implementation choice remains open; see Open decision.
    on Sep 18, 2026
  2. added
    help wantedActive contribution call for the named scope or host evidence; may require deep experience.
    and removed
    help wantedActive contribution call for the named scope or host evidence; may require deep experience.
    on Sep 18, 2026
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

    area:runtimeAgents, Graph, dispatch, orchestration, capabilities and workers.needs-designAn issue-specific implementation choice remains open; see Open decision.

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions