Identity and access
Company access is invitation-based. Authenticated users operate through assigned roles, and manager-only actions are enforced server-side.
Security & trust
Built to keep maintenance evidence inside the right company workspace.
FaultCite uses company-scoped records, role-controlled actions, authenticated access and private evidence storage as the foundation of its pilot architecture.
Tenant isolation
Machines, cases, manuals, evidence and exports are scoped to the active company. Cross-company isolation is explicitly tested during release acceptance.
Private evidence
Evidence and manuals are stored privately and delivered through authenticated, tenant-scoped application routes rather than public object links.
Operational controls
Trust is a release gate, not a marketing claim.
FaultCite does not claim independent certification that has not been completed. Automated release checks cover build, lint, tests, packaged assets and tenant guards. Dependency review, secret review, backup recovery, mobile accessibility and two-company field acceptance are verified separately before broader rollout.
- Dependency-aware health checks for application, database and file storage.
- Release gates for build, lint, tests and packaged assets, with separate dependency and secret reviews.
- Audit history for invitations, uploads, exports and repair workflow actions.
- Controlled production deployment and rollback procedures.
Safety boundary
FaultCite supports qualified maintenance work. It does not authorize unsafe work.
OEM procedures, employer safety programs, lockout/tagout requirements and qualified human judgment remain authoritative.