Appearance
Quality evidence
What a buyer can check for themselves, with where to look. Figures taken from the repository on 2026-10-09 (main at e95495b plus the launch docs). Re-run pnpm test and read the CI history on GitHub (FEAW-Serv/getmy-books, ADR 0046) to refresh them.
Size
| Measure | Value |
|---|---|
Production TypeScript (src/) | about 22,000 lines |
Test TypeScript (tests/) | about 32,000 lines |
| Test files | 156 |
| Tests | 1,989 (1,894 run without a database; the other 95 are Postgres tests that CI runs and requires) |
Spec scenarios named in test titles (SPEC-NNN Sn) | 148 distinct |
| Feature specs | 14 (docs/features/) |
| Architecture decisions | 36 (docs/decisions/) |
| Commits on main | about 700 |
What every change must pass
Every pull request, and every push to main, runs .github/workflows/ci.yml:
| Gate | Command or tool | Fails on |
|---|---|---|
| Lint | pnpm lint (eslint . --max-warnings 0, with eslint-plugin-security) | Any warning |
| Types | pnpm typecheck (strict, noUncheckedIndexedAccess, no any) | Any error |
| Migration rules | pnpm lint:migrations | A migration that breaks the append-only, expand-then-contract rules |
| Tests | pnpm test (vitest with coverage) against a real Postgres built as production builds it (pnpm db:setup) | Any failure; a skipped database test (REQUIRE_DATABASE_TESTS=true) |
| Coverage | Per-file floors in vitest.config.ts: 80% lines, branches, functions and statements on reconciliation, deadlines, receipts, money and presenters; 100% on src/platform/crypto.ts | Any measured file below its floor |
| Build | pnpm build | Any error |
| Docs | pnpm docs:build (VitePress, with a credential scan of every page) | A broken link, or credential-shaped text |
| Secrets | gitleaks over the full history (scripts/security/gitleaks.sh) | Any finding |
| Dependencies | pnpm audit with reviewed exceptions (security/audit-exceptions.json) | A new known vulnerability |
| Code rules | semgrep, 5 project rules in security/semgrep/, each with a fixture | A violation |
| Configuration | trivy config | A misconfiguration |
| Images | trivy image (report only until #75), CycloneDX SBOM uploaded per commit | Reported |
A red or flaky main stops feature work until the cause is fixed; retrigger commits are not allowed (ADR 0009, CLAUDE.md rule 7).
Project rules enforced in code
| Rule | Enforcement |
|---|---|
| The company comes only from the signed-in session | semgrep mcp-entity-from-session |
| No credentials in logs | semgrep no-logging-credentials |
| No statement text in logs | semgrep no-logging-statement-text |
| Money in integer pence, arithmetic only through the money helpers | semgrep pence-arithmetic; ADR 0025 |
src/rules/ and src/vat/ do no I/O | semgrep pure-modules-no-io; ESLint import bans |
| Owner-visible wording changes only on purpose | Golden snapshots of every presenter string (tests/present/golden.ts) and of every tool and prompt description |
Data isolation
- Row-level security on
entity_idon every table butprincipal(src/platform/policies.sql). tests/platform/rls.test.tsandtests/platform/policies.test.tsconnect as theapprole and prove one company cannot read or write another's rows;tests/platform/rls-indexes.test.tschecks the policy columns are indexed. CI fails if they skip.
Xero call budgets
tests/performance/budgets.ts fixes the exact number of Xero requests each of about 20 entry points makes for a stated amount of synthetic data (for example, a month of 2,000 bank records takes 22 requests). Xero allows 60 calls a minute per organisation; a budget that rises or falls fails until the number is changed with the reason in the commit. tests/performance/scale.test.ts and matcher-equivalence.test.ts cover large inputs.
Safety checklist
AUDIT.md records each standing rule (money, Xero, MCP, deadlines, code) with PASS, FIXED or N/A and the evidence: file, line, test and CI run. The approval path for writes (AUDIT C5) has its own injection tests.
Governance
Spec first, then a failing test, then the code (CLAUDE.md rule 2). Every commit carries a Spec: SPEC-NNN trailer or a logged SGE-Override, checked by .githooks/commit-msg. See the SGE governance guide.
Not yet evidenced
- No external penetration test.
- No load test against the production host; budgets bound Xero calls only.
- Retention periods (ADR 0026) are not yet enforced by scheduled jobs.