Support Center

Support for Jadda, builders and the Helpifyr community

This page separates the right entry points: questions about Jadda and early access, questions about Helpifyr solutions, and community or partner contact. That keeps follow-up faster and cleaner.

Clarify the Jadda entry first Use this when the main question is whether Jadda fits your daily work, routines or coordination needs.
Bundle solution questions deliberately Use this when the main topic is operational guidance, memory, automation, finance or local AI support.
Public channels for lighter touchpoints Discord, GitHub and Facebook remain good entry points for community and first orientation.

Who should use which support path?

The support page is no longer just a contact list, but a decision surface for end users, technical partners and the community.

Jadda entry

For people interested in Jadda

For people who want to understand whether Jadda fits their daily life, work style and early access direction.

  • clarify the right Jadda path first
  • match use cases and early access direction
  • avoid technical side paths too early
Go to early access
Solution support

Helpifyr solutions & operations

For teams that need solution-level conversations around operational guidance, memory, finance, local AI or controlled change.

  • discuss the right Helpifyr solution path
  • bundle operator and systems questions more clearly
  • move from vague technical talk to a business-readable solution picture
See solutions
Partners & projects

For collaborations and initiatives

When the topic is collaboration, solution demand, research or shared rollouts.

  • Suitable for partners, evaluations and strategic conversations
  • Most helpful when you already have a clear problem or project outline
  • Central entry point via email or the contact page
Contact us

Community and channel overview

Alongside direct support, public channels remain important so interested people, developers and the community have suitable touchpoints.

Email & direct contact

The structured path for project requests, solution interest, support and billing questions with more context.

  • Central address for prioritization and follow-up questions
  • Suitable for proposals, longer problem cases and collaboration
  • Direct entry point for Jadda early access as well as billing and refund topics
Contact us

Discord & community

For quicker questions, exchange and low-friction conversations around Helpifyr, Jadda and new ideas.

  • More direct exchange instead of long email ping-pong
  • Good for follow-ups, quick questions and community dynamics
  • An easy touchpoint for interested people
Open Discord

GitHub

The public technical channel for repos, traceability and visible systems work.

  • Useful for developers, builders and evaluations
  • Shows the technical substance behind the Helpifyr systems layer
  • A fit for anyone who wants to look deeper into implementation
View GitHub

Facebook

A public touchpoint for updates, visibility and low-friction first contact.

  • Good for reach and referrals
  • Supports public presence next to the blog and website
  • Useful for people who prefer social channels
Open Facebook

Operator-Lagebild und Fallsicht

Diese Oberfläche bleibt lesend. Sie zeigt, wo Master-Case, Work-, Run-, Action- und Evidence-Truth liegen, ohne daraus eine lokale Steuerzentrale zu machen.

Master Case

Case- und Handoff-Truth

Fallstatus, Ownership und Eskalationslogik bleiben upstream. Diese Seite zeigt nur die führenden Stellen und macht fehlende oder widersprüchliche Zustände sichtbar.

Master case program Case projection
Action / Run

Aktionen und Review-Pfade

Agentenaktionen, Denials und Review-Schritte bleiben in den führenden Projektionen. Die Readout-Surface macht sie lesbar, ohne lokale Erfolgssignale zu erfinden.

Action projection Run projection
Fail-Closed

Konflikte und visible gaps

Wenn Upstream-Truth fehlt, stale ist oder widersprüchlich wird, bleibt das als sichtbarer Gap stehen. Diese Seite glättet keinen Konflikt in ein falsches Grün.

Readout JSON Status JSON

Kombinationen und reservierte Views

Bundle-Profile und reservierte Operator-Views bleiben an Fabric gebunden. `jhf-web` zeigt die konsumierte Truth, beansprucht aber keine eigene Bundle- oder WebUI-Steuerwahrheit.

Reserved view boundary

Kein lokaler Shadow für künftige WebUI-Views

Diese Support-Fläche bleibt die lesende Web-Surface für Human-View, Operator-Zusammenfassung und Approval-Kontext. Eine künftige dedizierte WebUI kann diese reservierten Views später übernehmen, aber nicht parallel als zweite Truth starten.

Readout JSON Fabric deep dive

Wenn Upstream-View-Namen, Approval-State oder Bundle-Profile stale oder unvollständig sind, bleibt das hier sichtbar und fail-closed.

Not sure which path is right?

If you are not sure whether the right next step is Jadda, a Helpifyr solution, a partner conversation or a community route, we can point you to the right path quickly.

Get in touch See solutions