Skip to main content

Helpifyr Beam Compatibility

This compatibility page is generated from canonical repo-owned source material in JaddaHelpifyr/jhf-beam.

Documentation Map​

Compatibility Sources​

  • docs/OSS_INVENTORY.md
  • docs/PUBLIC_SURFACES.md

Derived from OSS Inventory and Version Truth​

OSS Inventory and Version Truth

Tool / Contract Summary​

jhf-beam publishes repo-owned OSS inventory and version-truth lanes for stack-wide upgrade readiness and owner routing. The normal path consumes Fabric directory status from: GET /api/v1/platform/tool-oss-inventory-directory.

Machine-readable sources:

  • maintenance/stack-oss-scan-scope.json (maintenance/stack-oss-scan-scope.json)
  • monitoring/sources/stack-oss-catalog.json (monitoring/sources/stack-oss-catalog.json)
  • maintenance/oss-inventory-scope.json (maintenance/oss-inventory-scope.json)

Execution and verification surfaces:

  • maintenance/pull_stack_oss_inventory.py (maintenance/pull_stack_oss_inventory.py)
  • maintenance/verify-fabric-tool-oss-directory-status.py (maintenance/verify-fabric-tool-oss-directory-status.py)
  • maintenance/generate_stack_upgrade_plan.py (maintenance/generate_stack_upgrade_plan.py)
  • maintenance/verify-stack-oss-inventory.py (maintenance/verify-stack-oss-inventory.py)
  • scripts/testing/run_beam_stack_oss_inventory_wave.sh (scripts/testing/run_beam_stack_oss_inventory_wave.sh)

Business Value​

Upgrade readiness must not depend on scattered version snippets. Beam keeps one explicit OSS inventory lane, one explicit version/readback lane, and explicit owner routing for drift and blockers. Fabric directory summary status and blocked-tool count are fail-closed inputs in the wave path.

Current Verified State​

  • stack-wide OSS inventory and upgrade planning are implemented and validated through repo verifiers
  • Fabric directory fields summary_status and blocked_tool_count are included in inventory evidence and validated fail-closed
  • owner-routing stays explicit and does not create local shadow truth in Beam
  • AGENTS guidance for Gitea API token runtime usage is documented in: AGENTS.md (AGENTS.md) (C:/CodexTest/.env as GITEA_TOKEN, no token value in repo artifacts)

Verify Path​

Repo:

python maintenance/verify-stack-oss-inventory.py
python maintenance/verify-maintenance-contracts.py
bash scripts/testing/run_beam_stack_oss_inventory_wave.sh

Optional live host readback:

python maintenance/pull_stack_oss_inventory.py --host <internal-runtime-redacted> --output test-results/stack-oss-inventory.live.json
python maintenance/verify-fabric-tool-oss-directory-status.py --inventory test-results/stack-oss-inventory.live.json

Planned / Not in current scope​

  • no local workaround for external owner repo drift
  • no shadow-truth fallback for Fabric directory in normal mode
  • no token materialization in docs, issues, logs, or evidence
  • no replacement of owner repo version truth with Beam-authored shadow data
  • JaddaHelpifyr/jhf-beam#154

License​

AGPLv3. See ../LICENSE (LICENSE).

Learn more at helpifyr.com.