Zum Hauptinhalt springen

External Helpifyr Boost Onboarding

Use this page when an external or adjacent partner needs the first admissible Helpifyr onboarding path without being handed a loose pile of generic docs links.

When to use this page​

  • You are onboarding a partner-operated boost or adjacent tool into the Helpifyr review path.
  • You need one exact packet of mandatory deliverables before Fabric can treat the request as reviewable.
  • You must explain the difference between orientation docs and the actual admission request.

What the partner must return​

  • one canonical fabric-manifest.json with stable identity, capability class, runtime kind, lifecycle stage, and release channel
  • repo-owned docs for tool profile, integrations, capabilities, API, and OSS inventory
  • explicit producer declarations for every Fabric-owned contract family the tool publishes
  • explicit consumer declarations for every Fabric-owned contract family the tool consumes
  • compatibility posture, lifecycle posture, and verify metadata
  • readiness and live-evidence targets that can be read back without guessing
  • one completed dry-run payload based on the Fabric-owned template

Review order​

  1. Send the canonical Fabric admission pack and dry-run template.
  2. Ask the partner to return the completed template plus linked repo artifacts and evidence.
  3. Validate the payload against the Fabric admission schema and governance surfaces.
  4. Execute the partner verify entrypoint and read back the declared readiness surfaces.
  5. Record the verdict in Fabric and open any downstream adoption work only after the evidence is complete.

Do not use these as substitutes​

  • API Surface Map is orientation help, not the admission contract.
  • Build an Integration is the journey page, not the review packet.
  • product API or compatibility pages can support evidence, but they do not replace the Fabric-owned dry-run request.

Fabric-owned source truth​

Verification​

This page is working when a partner can name the exact required artifacts, return the dry-run payload in the right shape, and understand that Fabric remains the admission verdict owner.

Next paths​