ACT Fibernet · Field Workforce Management Platform

Four repositories.
One platform.No documentation.

So the source was read instead — 690,343 lines of it, across a Java monolith, a Spring Boot service, an Angular console and an Android app. These four suites were reconstructed by static analysis, and every statement in them carries its evidence: verified cites a file and line you can open, inferred flags a reconstruction of intent that still needs business confirmation.

lines read
690,343
source files
3,101
repositories
4
documents
136

Clients

What the workforce touches

Services

What answers them

In every suite

Same shape, four systems
  1. 01Business RequirementsWhat business problem the system solves, and for whom.
  2. 02Product RequirementsEvery feature, with acceptance criteria.
  3. 03Architecture & DesignBlock diagrams, call flows, integrations, crons, deployment.
  4. 04Data ModelTables, collections, stored procedures, ERDs, and the sensitive-data map.
  5. 05API ReferenceEvery endpoint, grouped by module, with request and response shapes.
  6. 06User JourneysWhat a person actually does, step by step — including exception paths.
  7. 07Roles & EntitlementsWho can do what, and where each check is enforced.
  8. 08ConfigurationEvery setting, where it lives, and how to change it safely.
  9. 09Risks & ExceptionsThe risk register and failure-mode catalogue.
  10. 10LibrariesDependencies, their currency, and the upgrade path.
  11. 11Audit ReportWhat the extraction covered, what it missed, and how far to trust it.
Static analysis only. No running instance was observed, no database was accessed, and no penetration testing was performed. Credential keys are named by file and line; no credential value is reproduced anywhere in these suites.