Skip to main content

Capabilities

jhf-reed Capabilities

This document is the canonical repo-owned capabilities spine for jhf-reed. It describes what Reed declares at repository truth level without overstating runtime admission beyond the bounded lanes already verified elsewhere.

Signed Skill owner-readback admission​

contracts/execution/reed_skill_owner_readback_admission_v1.json is the server-owned authority record for Fabric's signed Skill owner-readback contract. The producer refuses any key whose public half is not the pinned operator-held trust root and persists issued receipts in a durable SQLite receipt store; the readback path accepts only a stored envelope signed by that pinned root and rejects replay across restarts. The committed production receipt contracts/evidence/reed_skill_owner_readback_receipt_v1.json proves the pinned root has operated. It cannot admit a capability: every Fabric pin, candidate/release binding, registry/projection revision, policy/evidence reference and trust key is fixed by that record rather than by the client envelope, and the verifier hashes the actual Fabric blobs at the pinned commit before accepting them. The explicit verifier is python scripts/verify_reed_skill_owner_readback_admission.py --check.

Reed carries two lanes. Each capability below states which lane it belongs to.

Skill releases consume the existing capability truth through reed_skill_capability_admission_v1. Required capabilities must be present in the exact Fabric projection, optional gaps remain candidate-only, and denied capabilities always win. This binding admits no new capability or tool and is verified by python scripts/verify_reed_skill_capability_admission.py --check. See LANES.md (docs/LANES.md) for the canonical disambiguation.

Capability: Reed Context Delivery, Read-Only​

reed.context.delivery.readonly​

  • capability_id: reed.context.delivery.readonly
  • lane: Context Lane
  • summary: Serve governed, tenant-filtered, read-only context from the Bobbin Context-Graph to admitted agents through five MCP tools, fail closed on admission, freshness or upstream failure, and expose no graph write, no Cypher, no free vector search and no free model endpoint.
  • tools: reed_context_describe; reed_context_assemble; reed_context_explain; reed_context_expand; reed_context_report_missing_fact
  • primary_contracts: contracts/runtime/reed_context_runtime_manifest_v1.json; contracts/execution/reed_context_delivery_gateway_v1.json
  • primary_docs: docs/LANES.md; docs/ARCHITECTURE.md; docs/STACK_CONTAINER_CONTRACT.md

This lane is the only route by which an agent reaches the Bobbin Context-Graph v4.2 and is therefore blocking for that programme. Runtime materialization ownership stays with jhf-openclaw-env#2385.

Capability: HERP CRM Customer Read​

reed.business.herp.crm_customer.read​

  • capability_id: reed.business.herp.crm_customer.read
  • lane: Action Lane, read-only module adapter
  • status: planned / runtime-not-admitted
  • summary: Read exactly one already-known spindle_customer by canonical CCL-2026-xxxxx ID through Reed and the governed Bobbin Context-Graph projection. The response is limited to title and summary.
  • owner_repos: gateway jhf-reed; projection adapter jhf-bobbin; domain owner jhf-spindle
  • primary_surfaces: scripts/reed_herp_crm_customer_read.py (adapter) and scripts/reed_context_runtime.py (planned runtime gate); contracts/tests/reed_herp_crm_customer_read_vectors_v1.json; contracts/capabilities/jhf_reed_capability_manifest.template.json
  • fail_closed: principal, tenant, company, environment, runtime scope, adapter, policy, freshness, Bobbin availability, exact-ID and response-shape checks are distinct and deny before data is returned.
  • evidence: every attempt produces a redacted business-read receipt when the owner evidence sink is projected; the receipt carries the source revision, field allowlist, freshness marker and payload digest, never raw graph data.
  • runtime_gate: the MCP/runtime path is implemented but remains absent from the production manifest allow-list, so tools/list and calls remain not-admitted until the owner-projected adapter and jhf-bobbin#546 domain decision are live.

The concrete company/tenant pair and CRM isolation-domain admission remain owner-projected dependencies. The fixture vectors are not live evidence and do not authorize runtime activation; jhf-bobbin#546 must close with the governed domain and reprojected nodes before the capability can change from planned.

Capability: Reed Gateway Contract Boundary​

reed.gateway_contract_boundary​

  • capability_id: reed.gateway_contract_boundary
  • lane: Action Lane
  • summary: Publish the agent capability gateway contract boundary for action envelopes, evidence envelopes, MCP catalog posture, routing guards, and owner-adapter handoff contracts.
  • primary_docs: docs/CONTRACTS.md; docs/ARCHITECTURE.md; docs/MODULE_FEATURES.md

Capability: Fabric Capability Consumption​

reed.fabric_capability_consumption​

  • capability_id: reed.fabric_capability_consumption
  • lane: both lanes
  • summary: Consume Fabric capability truth read-only and fail closed when capability admission, projection freshness, or compatibility posture is missing.
  • primary_docs: docs/FABRIC_TOOL_PROFILE.md; docs/CONTRACTS.md; docs/MODULE_FEATURES.md

Capability: Policy-Aware Gateway Enforcement​

reed.policy_aware_gateway_enforcement​

  • capability_id: reed.policy_aware_gateway_enforcement
  • lane: both lanes
  • summary: Bind Reed execution posture to Warp policy, Heddle claims, Keystore-safe secret handling, and explicit routing scope before any Reed lane can proceed.
  • primary_docs: docs/SECURITY.md; docs/ARCHITECTURE.md; docs/OPERATOR_RUNBOOK.md

Capability: Runtime Binding Verification​

reed.runtime_binding_verification​

  • capability_id: reed.runtime_binding_verification
  • lane: Action Lane
  • summary: Provide repo-owned verification surfaces for the bounded Reed/OpenClaw runtime lane while keeping runtime materialization ownership with jhf-openclaw-env.
  • primary_docs: docs/STACK_CONTAINER_CONTRACT.md; docs/HOST_HANDOFF_EXTERNAL_BLOCKERS.md; docs/MODULE_FEATURES.md

Capability: Operator Lane Execution Consumption​

reed.operator_lane_execution_consumption​

  • capability_id: reed.operator_lane_execution_consumption
  • lane: Action Lane
  • summary: Consume the Fabric operator-lane recovery standard as an execution consumer by binding Reed gateway admission, exact-main, post-merge verify, and live-readback truth to the admitted Reed/OpenClaw runtime lane.
  • primary_docs: docs/FABRIC_OPERATOR_LANE_EXECUTION_CONSUMER.md; docs/STACK_CONTAINER_CONTRACT.md; docs/MODULE_FEATURES.md

License​

This document is part of an AGPLv3 repository. Helpifyr project information is available at https://helpifyr.com.