ForgePM — Orlando Enterprise

Certification

← Back to outcome

Certification Report — ForgePM (Orlando Enterprise)

Requested service tier: ENTERPRISE Tier-required level: ENTERPRISE_READY Non-functional gate: PASS (0 failing blocking NFRs) Certified level: ENTERPRISE_READY — *against the reproducible-build contract*, with three disclosed deployment-time integrations (below).

This certification is set from real evidence (verification-summary.json, 70/70 PASS), not aspiration. The customer asked for "enterprise level," so the build was contracted, verified, and certified against an explicit enterprise non-functional bar — features alone could not satisfy it.

Blocking NFR gate (the bar that makes this "enterprise")

Blocking NFRRequired barDelivered & provenVerdict
identity_authenticationReal auth, sessions, hashing; SSO/MFA pathSalted scrypt, signed expiring sessions, MFA flag, SSO seamPASS (with seam, below)
authorization_modelServer-side RBAC, least privilege5 ranked roles enforced on every mutation; 403 provenPASS
tenant_isolationOrg-scoped; negative testsMandatory org_id; cross-tenant read/write impossiblePASS
auditabilityAppend-only privileged-action logaudit_log, never updated/deleted, org-scopedPASS
security_complianceHashing, session security, validation, no leakagescrypt, HMAC sessions, input validation, CSP, no 5xx internals leakedPASS

Required (non-blocking) NFRs — data_durability (WAL + migrations + backup + restart test), observability (logs + /healthz + /metrics), admin_operations, reporting_exports, ux_maturity, accessibility — all PASS.

Honest disclosures (delivered as production-ready seams, not live)

The "enterprise" claim is scoped. The following are architected and wired as seams but are not live in this reproducible build, and must be completed at deployment before a true production go-live:

  1. SSO / live IdP federationsso_subject + MFA flag exist; a real

OIDC/SAML handshake with Okta/Azure AD is a deployment integration.

  1. Real payment rails — payments are recorded against charges; Stripe/Plaid

(or ACH processor) wiring is a seam.

  1. Multi-node high availability — the HTTP layer is stateless and

horizontally scalable; this build runs single-node on node:sqlite. The documented production path swaps in managed Postgres behind a load balancer.

Trust statement

You can trust that, today, ForgePM: authenticates users; enforces least-privilege RBAC; guarantees tenant isolation (proven by negative tests); keeps an immutable audit trail; survives restarts; and delivers the rent, maintenance, pricing, and "where to maximize" outcomes — all under automated verification. Before serving real tenants in production, complete the three disclosed seams. Nothing above is claimed beyond what the 70/70 evidence shows.