Skip to main content

Integrations

Documentation Map​

Contracts And Integrations

Tool / Contract Summary​

jhf-dobby is mostly valuable because of how it consumes and respects external truth. This page documents what Dobby reads, what it writes, what it materializes locally, and what it must never recalculate as a competing truth source.

Business Value​

  • prevents Dobby from drifting into a second governance system
  • makes ownership boundaries clear for Fabric, Warp, Shuttle, Bobbin, and Spool
  • gives maintainers a single page for integration-side failure semantics

Current Verified State​

Available now:

  • Fabric read-only contract and admission consumption
  • Warp approval-lane consumption
  • Shuttle optional read-only evidence consumption
  • Bobbin-marked provenance publication
  • Spool scope classification as optional read-only evidence only

Planned / not in current scope:

  • Dobby-owned policy rules
  • Dobby-owned contract registry
  • Dobby-owned approval truth

Fabric​

Tool / Contract Summary​

Fabric is the governance source of truth for Dobby capability class, contract-family landscape, and admission posture.

Public Surfaces Consumed​

  • GET /api/v1/contracts/jarvis
  • GET /api/v1/contracts/jarvis/readiness
  • GET /api/v1/contracts/registry
  • GET /api/v1/contracts/families
  • GET /api/v1/contracts/schemas
  • GET /api/v1/contracts/matrix
  • POST /api/v1/tools/admission/dry-run

Contract Families​

Dobby consumes its producer/consumer family list from Fabric matrix truth. The derived runtime views expose the resulting set, but Dobby must not publish a competing family registry.

Producer-/Consumer-Zuordnung​

Materialized locally:

  • alignment status
  • derived contract families
  • admission dry-run request payload
  • degraded effective service mode

Explicitly not local truth:

  • JARVIS repo classification
  • registry ownership
  • family catalog
  • schema catalog
  • admission ownership

Compatibility Window​

  • compatibility mode: additive-minor-compatible
  • deprecation window: one published minor line
  • values come from fabric-manifest.json (fabric-manifest.json) and are verified against Fabric admission

Readiness / Drift / Monitoring​

  • drift signals are raised when repo entry, capability class, mode impact, matrix mapping, registry catalog, schema catalog, or admission readiness do not align
  • Dobby lowers its effective service mode when drift exists

Warp​

Tool / Contract Summary​

Warp owns the approval-lane truth used by Dobby promotion checks.

Public Surface Consumed​

  • GET /api/v1/security/approval/dobby/current

Available now​

  • Dobby sends approval_id, candidate_hash, and provenance_hash
  • Warp returns approval binding and fail-closed semantics
  • Dobby stores the returned approval snapshot in proposal payload

Fail-Closed Behavior​

  • missing base URL -> fail closed
  • HTTP failure -> fail closed
  • unreadable response -> fail closed
  • stale, mismatched, or rejected approvals -> fail closed

Explicit non-ownership​

Dobby must not accept request-local approval booleans as authoritative policy truth. The request model still contains legacy fields, but the runtime behavior uses Warp.

Shuttle​

Tool / Contract Summary​

Shuttle provides optional A2A/handoff evidence that can raise the priority of a run and can materialize a Dobby learning signal when the read-only evidence shows a negative handoff outcome.

Public Surface Consumed​

  • GET /api/v1/evidence/a2a-handoffs/latest

Available now​

  • Dobby filters Shuttle evidence by tenant and correlation/root-correlation
  • matched records are attached to stored run payload
  • evidence can increase priority score
  • negative matched outcomes such as blocked, rejected, expired, conflict, or circular are normalized into a Dobby-owned handoff_outcome_learning view

Optional / Extended​

  • Shuttle can be absent or 404
  • Dobby continues with degraded semantics

Known Limits​

  • Shuttle evidence does not become a hard intake dependency
  • Dobby does not sync or own Shuttle records
  • Dobby does not rewrite or re-publish Shuttle truth; handoff_outcome_learning is only a derived read-only materialization inside the run payload

Bobbin​

Tool / Contract Summary​

Bobbin is used as a marked provenance sink, not as a proposal or policy owner.

Artifact Written​

  • JSONL artifact of kind dobby.provenance.memory-enrichment.v1

Available now​

  • Dobby builds a marked artifact after successful approval processing
  • artifact validation forbids ownership fields such as policy or approval authority
  • when configured, artifacts are appended to JHF_DOBBY_BOBBIN_ARTIFACT_SINK

Optional / Extended​

  • when no sink is configured, Dobby returns degraded Bobbin status but does not fail the proposal lifecycle

Spool​

Tool / Contract Summary​

Spool is currently treated as optional read-only evidence scope only.

Current Verified State​

  • Dobby exposes Spool classification through its contract view
  • there is no Spool write or control dependency in the runtime

Known Limits​

  • no local cache of Fabric truth beyond in-process derived reads
  • no Bobbin or Shuttle retry queue
  • no multi-system reconciliation job
  • jhf-dobby#1
  • jhf-dobby#30
  • jhf-dobby#31
  • jhf-dobby#32

License: AGPLv3. See ../LICENSE (LICENSE).
Learn more at helpifyr.com.