Topic 17
Current Product Boundaries
A clear boundary helps your organization judge whether Jena4 fits today without relying on capabilities that are not currently part of the service.
Before you depend on Jena4
A product boundary is part of the answer—not a footnote.
Jena4 maintains whether governed conclusions remain justified as their recorded conditions change. It does not replace the people who define those conclusions, supply trustworthy information, review what changed, and decide what their organization should do next.
How Jena4 is delivered
Use the hosted service and its supported connections.
Jena4 is currently offered as a hosted service. A self-hosted edition, a customer-cloud edition, and a customer-installed collection agent are not current capabilities. Organizations connect through the supported product and integration interfaces; implementation details belong in the maintained developer documentation.
Identity and organization fit
Confirm that the current access model fits your rollout.
Enterprise single sign-on is not currently established as part of the service.
A person who needs access to multiple customer organizations cannot switch among them with one account today.
Requests that need Pathion
Some customer lifecycle actions are assisted rather than self-service.
Jena4 does not currently provide self-service organization export or deletion. Contact hello@jena4.com to discuss an organization privacy request. Public verification pages, portable certificates, offline verification, and an open verification standard are also not current product commitments.
Service commitments
Technical capability is not the same as a contractual guarantee.
Do not infer a public uptime promise, throughput guarantee, backup or restoration objective, or disaster-recovery commitment from a product demonstration or technical description. If your adoption depends on a specific service commitment, confirm it in the maintained service documentation or your written agreement with Pathion.
How to use this boundary
Plan against what is available and documented now.
Product boundaries can change as capabilities are released and documented. Until then, treat an unlisted capability as unconfirmed and ask Pathion before making it part of an operating plan, procurement requirement, or customer promise.