JaddaHelpifyr
DEENFR
Back to overview

Safety / Compliance

The lane that frames compliance

Technical name: Selvage

Compliance target layer in preparation.

Selvage keeps the target posture visible: Loom owns the canonical documents, OpenAleph is the target analysis platform, and OpenSearch remains an explicit target lane.

Make compliance decidable

Status Work in progress README sync 11 Jun 2026

Why start here?

Modern systems build AI features, automations, and business processes quickly. The real uncertainty starts when nobody can say with confidence whether all of that is actually allowed.

jhf-selvage is the emerging decision base for compliance across the Helpifyr system. Not as a screening-only tool, not as a document archive, and not as a finished product today. Canonical documents stay in jhf-loom on Alfresco CE while Selvage is meant to translate rules, requirements, and obligations into clear decisions for engineering and operations.

When do I need this?

Selvage becomes important when new regions, new data processing, or new AI features need to be assessed before they are built.

  • new AI features
  • new regions
  • new data processing
  • new business models
  • regulatory requirements

What role it plays here

This is the compliance decision layer.

Know before you build.

Compliance target layer in preparation.

What the module actually does

The target state is intentionally bigger than screening. Selvage is meant to become the compliance source and decision layer that product, engineering, and operations can rely on.

At the core

Connects laws to concrete requirements. Rules are not meant to stay abstract. They should arrive in the system as actionable requirements.

Defines when rules apply. Selvage is meant to show which obligations really matter in which context.

Translates obligations into technical controls. Compliance does not stop at text. It leads to clear controls and evidence paths.

Provides clear decision foundations. Teams should know before they build what is allowed, required, or risky.

Connects compliance with engineering and operations. The decision layer should not sit beside the product. It should influence delivery and runtime directly.

Makes compliance machine-readable. Rules, obligations, and gates should become structured enough for systems and teams to work with them consistently.

What role it plays in the stack

Loom keeps the canonical documents and metadata. Warp orchestrates agent execution. Spindle remains business truth. Lantern visualizes review and human approval without being pushed as a separate public brand in this wave. Harness reviews the case before execution. Selvage connects that document boundary to target analysis in OpenAleph and to an explicit OpenSearch target lane for later decisions.

  • future compliance decision layer
  • more than screening, but still under construction
  • affects engineering, release, and operations
  • meant to connect rules with controls and gates
  • stays clearly separate from finished legal advice

What this looks like in practice

Old: build, check, hope. New: check, understand, build. Today the public posture mainly describes the target lane: Loom as the document boundary, OpenAleph as the target analysis platform, and OpenSearch as an explicit target compatibility lane. The target state is a compliance source of truth plus decision layer for the entire system.

01

Connects laws to concrete requirements

Rules are not meant to stay abstract. They should arrive in the system as actionable requirements.

02

Defines when rules apply

Selvage is meant to show which obligations really matter in which context.

03

Translates obligations into technical controls

Compliance does not stop at text. It leads to clear controls and evidence paths.

04

Provides clear decision foundations

Teams should know before they build what is allowed, required, or risky.

How it fits into the system

Selvage does not stand alone. It connects to neighboring modules so a single capability becomes dependable follow-through.

Fabric The rules that always hold Beam The safety layer that stops risky change Wire The outward path that does not end in chaos Heddle The access layer that stays consistent everywhere Loom The place where no document gets lost

Important boundary

Selvage stays bounded to its role as Compliance target layer in preparation. It does not replace other modules; it makes its part of the system traceable, connectable, and reviewable.

What is intentionally out of scope

Selvage only makes sense when it is not mistaken for a finished screening or legal system.

  • not a screening-only tool
  • not a legal document archive
  • not a policy system on its own
  • not a replacement for lawyers

Open-source basis

These are the technologies carrying the module behind the scenes. They stay secondary, but they help technical readers orient themselves.

What keeps this page honest

This explanation stays anchored to the module’s current truth, including its real boundaries, responsibilities, and contracts.

Selvage is the emerging compliance decision layer for admission preparation, with jhf-loom as the document source of truth, OpenAleph as the target analysis platform, and OpenSearch as an explicit target compatibility lane.

JaddaHelpifyr/jhf-selvage

README.md

Source and repo truth

This page is rendered from the repo-owned projection truth and remains tied to the README, module boundaries, and status.

GitHub JaddaHelpifyr/jhf-selvage

Selvage

Loom keeps the canonical documents and metadata. Warp orchestrates agent execution. Spindle remains business truth. Lantern visualizes review and human approval without being pushed as a separate public brand in this wave. Harness reviews the case before execution. Selvage connects that document boundary to target analysis in OpenAleph and to an explicit OpenSearch target lane for later decisions.

Back to overview Contact