Status: built and deployed, private (pre-launch). A working multi-tenant system runs behind Cloudflare Access — org auth + seat provisioning, an Ed25519-signed, externally verifiable audit chain over every decision, client-data ingestion with a Robust-PCA corruption mask, prospect dedup, and a continuous-improvement loop. The source is private and there’s no public demo, so it isn’t open for outside inspection yet. Tests pass on local runs (there’s no CI yet); the improvement metrics to date are measured on synthetic data; there is no paying customer yet.
For inquiries, contact us via the SUMequities contact page.
What’s Built vs. What’s Next
Built and running behind auth: Cloudflare Access multi-tenant auth with org/seat provisioning; an Ed25519-signed, hash-linked audit chain with an offline verifier; client CSV/JSON ingestion with an automatic Robust-PCA corruption mask; prospect research and dedup; and a continuous-improvement (AR) loop. The system is deployed — but behind Cloudflare Access, so the whole surface (including any “public” route) currently requires auth.
What would make this entry externally substantiable — at least one of:
- A public (unauthenticated) demo URL reflecting the intended product behavior, and/or
- A public or read-access source repository so the implementation can be inspected directly, and/or
- CI wired up so the test suite’s pass/fail status is independently verifiable (today the tests pass only on local runs).
Verification
Full proof report → All claims, all projects →- In progress
Deployed behind Cloudflare Access; worker test suite (31 K-matrix + 4 A-matrix files) and engine math/improvement tests pass on local runs — no CI yet, so not independently verifiable
README / PROOF_BOUNDARY.md; workers/api/test; engine/test_*.py (local-only, no .github/workflows)
- In progress
Public (unauthenticated) demo URL, or read-access source, so the implementation can be inspected directly
Body — 'What's Built vs. What's Next'