Skip to main content

Overview

jhf-reed Overview

jhf-reed is the Helpifyr Agent Capability Gateway bootstrap repository. It already publishes the contract-boundary and verification surfaces for stack-safe MCP and action-routing lanes, while the broader live gateway runtime remains only partially materialized.

Reed keeps execution separate from truth ownership:

  • jhf-fabric remains the source of contracts, projections, events, and verdicts.
  • jhf-warp remains the source of agent policy, risk posture, and approvals.
  • jhf-heddle remains the source of identity and delegated claims.
  • jhf-keystore remains the source of secret brokering and acceptance evidence.
  • Module repositories remain the owners of their domain-specific adapters and actions.

What Reed Is​

Reed is two runtimes under one name, and every statement below applies to exactly one of them. LANES.md (docs/LANES.md) is the canonical disambiguation and should be read first.

  • Action Lane (reed.action.capability_plane) — the agent-facing access layer for Helpifyr module actions. It is the place where admitted capabilities, policy, identity, routing scope, and evidence requirements meet before an agent-visible action can proceed. Write-capable, staged behind ACP waves.
  • Context Lane (reed.context.delivery.readonly) — the read-only context delivery gateway carrying reed_context_describe, reed_context_assemble, reed_context_explain, reed_context_expand and reed_context_report_missing_fact. It is the only route by which an agent reaches the Bobbin Context-Graph v4.2, and therefore blocking for that programme.

Non-blocking is a property of the Action Lane, not of Reed. The same claim applied to the Context Lane is false. Never make it, or the related claims about contract-only status and missing runtime, without naming the lane — see LANES.md (docs/LANES.md).

When To Use Reed​

Use the Action Lane when an OpenClaw-driven agent needs a Helpifyr action surface that must stay aligned to Fabric truth, Warp policy, Heddle claims, and Keystore-safe evidence posture.

Use the Context Lane when an agent needs governed, tenant-filtered context from the Bobbin Context-Graph with provenance, citations and an explanation trace.

What Reed Owns​

  • MCP and action-gateway access posture for admitted Helpifyr agent actions (Action Lane).
  • The read-only context delivery boundary and its fail-closed runtime route surface (Context Lane).
  • Routing guard contracts for tenant, environment, runtime scope, and adapter instance boundaries.
  • Reed-owned evidence and handoff propagation contract surfaces.
  • Public-safe documentation about the gateway boundary and operator verification posture.

What Reed Does Not Own​

  • Business object truth, module domain logic, or domain write semantics.
  • Policy, approval, or risk truth.
  • Identity, delegated-claims, or session truth.
  • Secret storage, brokering, or acceptance evidence truth.
  • Final closeout or stack-verdict ownership.

How To Verify The Current Repo-Owned State​

  • python scripts/docs/validate_docs_inventory.py
  • python scripts/validate_docs_platform_v1_6.py
  • python scripts/verify_reed_oss_inventory.py
  • python scripts/verify_reed_templates.py

These checks validate the current public-safe source docs, imported docs-platform contracts, and Reed-owned template/ownership boundaries. They do not claim that a live Reed runtime already exists.

Scope​

The repository is in bootstrap/contract-boundary state. Its current scope already includes MCP gateway, action routing, policy enforcement, evidence emission, and OpenClaw runtime integration contracts for Helpifyr agents, while live admitted execution remains a bounded follow-up owned jointly with runtime repositories.

The stack-wide repository inclusion matrix is maintained in REPOSITORY_SCOPE.md (docs/REPOSITORY_SCOPE.md). Repositories may participate as truth owners, adapter owners, runtime owners, consumers, operations surfaces, or reference/legacy systems; inclusion does not imply that Reed owns their business logic.

The concrete Agent Capability Plane Gitea issue orchestration is recorded in ACP_WAVE_ISSUES.md (docs/ACP_WAVE_ISSUES.md).

License​

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

Docs Platform v1.6 Base Family​

  • README.md
  • docs/OVERVIEW.md
  • docs/INSTALL.md
  • docs/CONFIGURATION.md
  • docs/OPERATIONS.md
  • docs/TROUBLESHOOTING.md
  • docs/RELEASE_NOTES.md
  • docs/docs.manifest.yaml