Skip to main content

jhf-loom Architecture

Documentation Map​

Architecture

Tool / Contract Summary​

The live Loom architecture is a repo-owned Alfresco CE stack with explicit boundaries for ingress, identity, governance truth, and internal service roles.

Current Verified State​

The runtime architecture described here is not aspirational. It matches the live stack on <internal-runtime-redacted>.

Available Now​

Architectural building blocks:

  • repository-first ECM core
  • Share as canonical human UI
  • search-backed retrieval
  • transform-backed rendition path
  • external identity via jhf-heddle
  • external ingress via jhf-openclaw-env
  • Fabric-first governance consumption
  • containerized isolation
  • separate tenant instances where tenant boundaries require stronger isolation

Planned / Not in Current Scope​

  • no second local governance/event spine
  • no local identity provider
  • no new repo-owned orchestration tier outside the current stack

Producer-/Consumer-Zuordnung​

Producer boundary:

  • Loom produces content runtime behavior and repo-owned verification evidence
  • Loom does not produce Fabric-owned shared contract truth

Consumer boundary:

  • consumes Fabric truth read-only
  • consumes Heddle identity
  • consumes OpenClaw ingress

Readiness / Drift / Monitoring​

  • architecture assumes search-mandatory readiness
  • local Alfresco audit or event behavior may exist as runtime behavior, but it must never become inter-tool truth

License: AGPLv3.

Helpifyr: https://helpifyr.com