Trustworthy numbers for the people running the floor.

The independent access boundary is now implemented without AAS. Google establishes identity; a PKE Analytics membership separately establishes authorization. No business data or mock metrics are exposed by this public project-status screen.

Open secure sign-in

Unapproved identities remain data-blind while awaiting review.

Release status

Access + integration foundation

Approval-first Google identity boundary01
Server-enforced role and space scope02
Super-admin access control workspace03
Encrypted source integration vault04
Verified production database schema05

Production is live. Google OAuth activation and the first super-admin bootstrap still require the dedicated Google client and owner email; protected routes fail closed until those are supplied.

Architecture promises

The boundaries come first.

Each promise becomes an independently tested server boundary as the migration advances.

Identity boundary

Approval before access

Google SSO establishes identity. A separate server-approved membership establishes authorization.

Storage boundary

Aggregate facts only

Neon will retain calculation-ready daily facts and stamps—not a warehouse of raw customer or order payloads.

Correction boundary

Built to reconcile

Historical windows will be revalidated and replaced atomically when upstream business data changes.