Skip to content

Immutable Evidence, Real Certification: Internal OCI Artifacts and CRM Gateways Compose a Safer Stack

Today, Helpifyr and JaddaHelpifyr converge on a new internal contract: every critical runtime now emits immutable OCI evidence artifacts, and CRM certification gates are enforced with real, verifiable evidence. This closes the loop between what we claim, what we publish, and what we can actually prove at runtime.

Jadda Helpifyr3 min read
Immutable Evidence, Real Certification: Internal OCI Artifacts and CRM Gateways Compose a Safer Stack

At a glance

141

merged changes

20

code projects involved

Most changes in

  • jhf-spindle41
  • jhf-weaver27
  • jhf-openclaw-env16

Underlined terms are explained: just hover or tap.

Imagine deploying a customer-critical CRM integration, only to discover-after the fact-that the certification evidence was missing or unverifiable, leaving operators in the dark and developers scrambling to reconstruct what went wrong. Until now, evidence of runtime compatibility and certification status was scattered, mutable, and often ephemeral. This gap between intent and proof made it impossible to guarantee, at any moment, whether a deployment truly met the platform’s contractual requirements. Today, that uncertainty ends.

Why This Day Mattered

For operators and developers integrating with the Helpifyr/JaddaHelpifyr stack, the new internal OCI evidence artifacts mean that every critical runtime-Loom, Warp, Shuttle, Heddle, and more-now leaves behind an immutable, independently verifiable record of its build and certification state. This enables downstream systems to programmatically enforce CRM compatibility gates, automate compliance checks, and diagnose failures without guesswork. For users, this translates to higher confidence that only certified, proven integrations are admitted, while failed or ambiguous states are fail-closed and immediately actionable.

The closed UTC day 2026-07-11 resolved into 141 merged PRs across 20 repos, led by jhf-spindle (41), jhf-weaver (27), jhf-openclaw-env (16).

What Actually Changed

Every major runtime in the stack now emits a metadata-only OCI evidence artifact during its build and admission phase, retained as an immutable Gitea Actions artifact. CRM certification gates (notably for ERPNext and Frappe/Host73) have been updated to require and consume these real evidence artifacts, rather than relying on indirect or mutable signals. This evidence is now the single source for both human and automated gatekeeping, and is canonicalized through Caddy/AdGuard hostnames to prevent drift. The stack’s contract is now enforced not just by policy, but by cryptographically signed, queryable evidence that can be independently audited at any time.

Why It Holds Better Now

This approach eliminates the ambiguity and race conditions of prior certification signals, where mutable or missing artifacts could leave a system in an unknown state. By emitting and retaining immutable OCI evidence for every runtime, the platform guarantees that certification and compatibility claims are always backed by concrete, tamper-evident data. Certification gates now operate on these artifacts, closing the loop between build, admission, and runtime, and ensuring that only verifiable, certified integrations progress through the stack. This reduces operational risk and unlocks automation that was previously impossible without a trustworthy source of runtime truth.

Want to Know More?

How might downstream automation and compliance tooling leverage these OCI evidence artifacts to provide real-time, self-service certification dashboards or trigger targeted remediation without manual intervention?

Terms in this post

Heddle
Module for identity, sign-in and SSO.
Warp
Controls which task runs when and where.
Shuttle
Runs workflows.
Loom
Controlled storage for documents and content.
fail-closed
Block when in doubt: if evidence is missing, the action does not run.
drift
Target and actual state silently moving apart.
runtime
The environment in which the system actually runs.
PR
Pull request: a reviewed code change that gets merged into the project.
repo
Repository: a code project under version control.
CRM
Customer relationship management: contacts, requests and sales opportunities.
operator
The person or team running the system.

What would this look like in your company?

A pilot shows it with a real process.

Request a pilot

More on Evidence and verification

See all
Offline Admission Verifiers: Locking Down First-Owner and Time Guarantees in Autonomous DeploymentEvidence and verification

4 min

Offline Admission Verifiers: Locking Down First-Owner and Time Guarantees in Autonomous Deployment

Today's engineering work closes a critical trust gap in Helpifyr / JaddaHelpifyr's deployment pipeline by introducing offline verifiers for first-owner claims and time-based admissions. These new mechanisms enforce contract-level evidence and one-use challenge protocols, making the system provably strict even in isolated or adversarial environments. This elevates the platform's operating model from best-effort checks to cryptographically anchored, auditable invariants at every stage of the bootstrap and admission lifecycle.

Read
Domain Separation for Zimbra Admission: A New Line of Defense in UC Contract IntegrityEvidence and verification

4 min

Domain Separation for Zimbra Admission: A New Line of Defense in UC Contract Integrity

Today’s engineering work delivers domain-level isolation for Zimbra-based admissions, unlocking a stronger, more auditable contract boundary for user communication (UC) flows. By introducing a concrete domain separator into the Zimbra Admission process, we’ve enabled precise compartmentalization of authentication and lifecycle events, ensuring that cross-domain ambiguity is structurally impossible. This architectural hardening not only closes subtle attack surfaces but also empowers platform operators and integrators with new guarantees about the provenance and scope of each admission event.

Read
Offline Core Issue Auditing: Closing the Loop on Historical Data IntegrityEvidence and verification

4 min

Offline Core Issue Auditing: Closing the Loop on Historical Data Integrity

Today, the Helpifyr and JaddaHelpifyr stack gains a foundational guarantee for the long-term integrity of critical core issue data, with new mechanisms for offline audit, closure logic, and plan-basis reconciliation. This work arms operators with tools to detect and resolve discrepancies in historical records, unlocks safer data migrations, and gives developers a deterministic contract for the lifecycle of sensitive issues and plans.

Read