FrootAI.dev AgentSpace
On this page 4
Design & Extend Hybrid

Capability Hub & portable templates

Discover, review, and govern skills, extension manifests, connectors, and provider-agnostic workflow templates without silently widening authority.

Status: Available Architecture: O1 · Orchestration Read: 5 min Verified: 2026-11-16

Four capability types, one review boundary

Capability Hub consolidates discovery and governance across four distinct building blocks so operators never confuse documentation or manifest registration with live execution authority:

Capability type Role in AgentSpace Where execution authority lives
Skills Versioned instruction and checklist packages attached explicitly to selected agents. Bounded by the assigned agent’s existing connector and approval scope.
Extension manifests Declarative capability packages specifying requested permissions, version, and entrypoints. Manifest approval records governance consent; runtime execution still requires a bound adapter.
Connectors External system definitions specifying auth mode, data path, scopes, and action policies. Handed off to Connector Exchange for HTTPS allowlist and secret binding review.
Workflow blueprints Reusable human-and-agent process graphs with built-in evidence and Decision Gate nodes. Opened as non-destructive draft forks in Workflow Canvas.

Portable AgentSpace template contract

Reusable solutions combine these four primitives into a provider-agnostic AgentSpace Template. Keeping workflow structure, approvals, and evaluation criteria outside model-specific prompts allows teams to switch runtimes without rewriting governance.

{
  "id": "governed-knowledge-brief",
  "version": "1.0.0",
  "frootLayer": "O1",
  "outcome": "Produce a source-cited internal brief for human approval",
  "adapterContract": {
    "interface": "frootai.agent-runtime.v1",
    "supportedAdapters": ["openai-compatible", "mcp-http"]
  },
  "permissions": {
    "connectors": ["approved-knowledge-index"],
    "writePolicy": "ask-first",
    "destructivePolicy": "disabled"
  },
  "gates": ["source-citation-check", "owner-signoff"],
  "evaluation": {
    "minimumGroundedScore": 0.95,
    "maxCostCentsPerRun": 25
  }
}

Governed installation lifecycle

  1. Inspect before requesting

    Open Capability Hub, select Discover, and inspect package provenance, version, permission profile, and requested scopes.

  2. Submit an installation review request

    Requesting a package places it in proposed / review state with a server-governed request identity and audit entry.

  3. Approve, disable, or revoke with version checks

    Authorized owners or admins transition manifests through approved, disabled, or terminal revoked states using optimistic lifecycle versions.

  4. Complete specialist handoffs

    Connector templates route to Exchange for secret-reference binding; workflow blueprints fork into Canvas so existing active processes are never overwritten.

Authority and manifest invariants

  • Catalog item identifiers cannot spoof or overwrite governed installation-request identifiers.
  • Duplicate active installation requests for the same package are rejected cleanly.
  • Rejected or terminally revoked extension manifests cannot transition back to enabled state.
  • Connector writes default to ask first; destructive connector actions default to disabled.
  • Approving an extension manifest never reports a worker, model, or webhook adapter as running unless its runtime binding is verified.
Verified against repository suites
tests/backend/platform.test.tstests/backend/workspace-lifecycle.test.ts
Markdown specification

Capability Hub & portable templates