Skip to main content

Overview

jhf-lantern Overview

jhf-lantern is the human interface layer for the Helpifyr stack. It renders operator-facing views over Fabric, Pattern, Warp, and owner-repo truth without becoming the source of truth for policy, runtime state, identity, or domain objects.

When To Use It​

Use Lantern when an operator or evaluator needs a single read-only interface to:

  • inspect stack posture without opening multiple owner tools
  • compare workflow, quality, evidence, and operations surfaces side by side
  • verify whether an upstream owner surface is available, stale, restricted, or intentionally fail-closed

Do not use Lantern as the authority for business policy, runtime ownership, identity truth, deployment control, or final closeout decisions.

What It Owns​

  • the human-facing shell and navigation posture for admitted stack surfaces
  • route-level UI contracts for read-only operator views
  • explicit fail-closed rendering when upstream owner readbacks are unavailable

What It Does Not Own​

  • Fabric contracts or event truth
  • Pattern work-state authority
  • Warp execution authority
  • Heddle or Keystore identity and secrets authority
  • deployment, cutover, or host runtime ownership

Scope​

  • route-aware mixed operator shell over admitted, restricted, preview, and future-contract surfaces
  • route, navigation, and interaction contracts for stack surfaces
  • explicit fail-closed states when an upstream owner surface is unavailable
  • UI composition that keeps Fabric and domain-owner truth visible

Bootstrap Boundary​

For the spindle bootstrap program, Lantern may own:

  • wizard and admin UX for company profile input and review
  • explicit W1 readback for company, country, industry, size class, accounting, organization, access-agent, and residency profile families
  • quickstart, full bootstrap, add-company, and reconcile-company mode visibility
  • readiness, risk, simulation, and drift readback presentation
  • bounded BFF adapters that render admitted owner truth without mutation

For W1 specifically, Lantern may render only the admitted bootstrap input and readback families for:

  • company
  • country
  • industry
  • size class
  • accounting mode
  • organization
  • access/agent
  • residency/sovereignty

Lantern must keep small_company_quickstart versus full_company_bootstrap selection explicit in the operator UX and readback. It must not infer those postures locally.

Lantern must not own:

  • bootstrap program truth, milestone truth, or closeout verdicts
  • company, identity, document, or runtime business objects
  • local progress state that duplicates Fabric, Pattern, Spindle, Heddle, Loom, or OpenClaw truth
  • W2 identity provisioning or W3 domain-bundle materialization behavior

Non-Goals​

  • business policy ownership
  • final closeout decisions
  • runtime orchestration ownership
  • write-capable domain actions
  • local shadow truth for Fabric, Heddle, Spindle, Pattern, Warp, or Keystore

Verify​

Use the repo-owned fast checks for docs and contract integrity:

python scripts/verify_fabric_oss_upgrade_consumer.py
python scripts/verify_module_features.py
python scripts/verify_scan_and_fix_automation.py
python -m pytest -q

For host or runtime questions, verify the real Lantern owner state on the owner-supplied runtime host first instead of treating the local UI preview as runtime truth.

Release Eligibility Posture​

  • Public release-surface admission is bounded by contracts/admission/release_surface_inventory_v1.json.
  • Current repository history posture is tracked in contracts/admission/repository_publication_history_posture_v1.json.
  • Active owner blocker: JaddaHelpifyr/jhf-lantern#382.
  • jhf-lantern remains pending_history_scan; this slice prepares and tests public release surfaces only and does not authorize publication.
  • Repo-owned history evidence now runs through python scripts/verify_repository_history_posture.py and currently proves filtered_publication_required.
  • Canonical Gitea history remains private or internal; a future public candidate uses filtered publication from exact main and never rewrites canonical history.
  • The owner decision is recorded in docs/FILTERED_PUBLICATION_DECISION.md.

License: AGPLv3 Project: https://helpifyr.com