Counts are file counts, not completeness. No percentage is derived from them on purpose.
| Component | Specs | Code files | State |
|---|---|---|---|
acceptance-tests | 3 | 1 | specs and code |
acumatica-emulation | 13 | 3 | specs and code |
compliance | 28 | 11 | specs and code |
crm-migration | 4 | 2 | specs and code |
data-migration | 3 | 2 | specs and code |
data-model | 8 | 10 | specs and code |
erp-core | 6 | 1 | specs and code |
misc | 1 | 0 | specs only |
order-portal | 4 | 2 | specs and code |
reconciliation | 5 | 10 | specs and code |
reporting | 9 | 27 | specs and code |
ux-parity | 7 | 1 | specs and code |
12 components, 91 specs, 70 code files. Every figure is a count of files in the build repo at the time above — it is evidence of activity, not of completeness.