Skip to content

calibration: wire probeFunctionalSurface into the live provider/entry gate for openapi/subnet-api/sse kinds #8909

Description

@JSONbored

Problem

src/review/content-lane/registry-logic.ts:636's probeFunctionalSurface is a "best-effort, truncation-tolerant check that a fetched body actually serves the surface its kind claims" (openapi schema, JSON API, SSE stream) -- fully implemented and tested (11+ cases in test/unit/content-lane-registry-logic.test.ts). Like computeGrounding (see the sibling issue), it has zero callers outside its test file; assessSurfaceEntry never fetches the surface url's content before merging.

Proposal

Same shape as the sibling grounding-check issue -- fetch the surface url's content-type/body for FUNCTIONAL_KINDS (openapi, subnet-api, sse) entries and feed it through probeFunctionalSurface, holding/closing on served: false. Likely should be scoped/designed together with the grounding-check issue since both need the same "fetch source content before merge" plumbing.

Deliverables

  • A maintainer decision on whether/when to wire live functional-surface probing into the merge gate
  • If approved: a design spec covering fetch plumbing shared with the grounding-check issue, and what served: false does to the gate decision

Links & Resources

  • src/review/content-lane/registry-logic.ts:636
  • test/unit/content-lane-registry-logic.test.ts

Boundaries

This changes what's verified before a subnet-registry surface auto-merges -- gate-authority change requiring design review. Do not unlock for contributors without an explicit maintainer decision. Should be scoped together with the sibling grounding-check issue given shared fetch-plumbing needs.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.roadmapOn the Wave-2 agent-layer roadmap board (project 9)

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions