Skip to main content

Security

jhf-lantern Security

Lantern is a human interface layer. It must not become a policy, identity, secret, runtime, or domain-system authority.

Boundaries​

  • Fabric owns policy, gate, projection, and closeout truth.
  • Heddle owns identity and session truth.
  • Keystore owns secret brokering and evidence posture.
  • Domain repositories own business-object truth.
  • Lantern renders admitted readbacks and fail-closed status only.

Phase-0 Posture​

  • no write-capable user actions
  • no committed secrets or credentials
  • no local shadow approval or closeout logic
  • no direct external submissions
  • no domain mutation from UI state

Evidence Handling​

Sensitive evidence must remain in the owner system and be linked only through admitted readback surfaces. Do not copy secrets, tokens, passwords, raw personal data, or private runtime evidence into Lantern docs, logs, or UI fixtures.

Verify​

python scripts/verify_module_features.py
python scripts/verify_route_aware_runtime.py

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