Trust / security
A contractor built it. Make us prove the boundary.
JTF is candid about the conflict a buyer should examine: the software grew out of work inside an operating contractor. Tenant isolation is therefore a release gate to inspect, not a reassurance to accept.
No certification claimed · no customer data on this public site
Boundary 01
Isolation belongs below the interface.
The intended boundary is tenant-scoped database enforcement rather than a dashboard filter. A technical evaluation must verify roles, policies, negative paths and the serving identity before beta data enters the system.
Boundary 02
Release evidence must preserve human authority.
Evidence-retention check
Release evidence must show that a generated answer retains its sources, confidence and unresolved disagreement.
Human-authority check
Negative-path tests must show that spend, signatures, attestations and consequential submissions stop for a human decision.
Marketing-telemetry check
Before beta data enters the system, inspect the deployed analytics configuration and prove that addresses, form contents and operational records are not collected by this public site.
What we do not claim
No badge by implication.
This site does not claim SOC 2, ISO 27001, HIPAA, PCI certification or another external compliance status. If a requirement is part of your buying process, put it in the evaluation record and require current evidence.
Final beta · applications open
Ask the uncomfortable security question first.
We are accepting roofing operators who will test one real workflow, tell us where it breaks, and help shape the production release.