A high-level status report of the current Solynth development thread, prepared as an orientation for a new collaborator: what was built, what now works end-to-end, how public and member content connect, where Patreon fits, and what remains DEV work.
The platform has moved beyond a collection of static content sites. The DEV build now has a coherent public front door, Auth0-backed sign-in, a Solynth-owned user shadow table, account status control, canonical entitlements, database-owned content classification and a server-side content gate.
The major milestone in this thread was SOL-005E. Three dedicated Auth0 database users were created and mirrored into platform.sln_users. One was given an active SOLYNTH_MEMBER entitlement, one deliberately had no entitlement, and one was disabled. The final regression script verified all three paths through the real login flow.
sln_session; disabled users do not.platform.sln_users.platform.entitlements is the canonical Solynth authorization grant store.Runtime secrets were separated from source-controlled code. runtime/secrets/codespaces.env became the DEV environment source, and the final 005E runner now loads it automatically.
Three Auth0 users were created for predictable authorization testing: entitled, unentitled and disabled.
The Auth0 subjects were inserted into platform.sln_users; passwords remained entirely in Auth0.
The entitled user received an active SOLYNTH_MEMBER grant; the unentitled user deliberately received none.
The original regression client produced a valid Auth0 token for the wrong audience. The live Solynth site expected the SolynthSSO client audience. Production authentication was sound; the test path was wrong.
The replacement harness drives /login, Auth0 Universal Login, Authorization Code + PKCE, the callback, session issuance and the protected-content gate.
The 12/12-passing script was packaged, validated, committed from A-Shell, pushed, pulled fresh into Codespaces and rerun successfully.
| Fixture | State | Result |
|---|---|---|
test-entitled | enabled + active SOLYNTH_MEMBER | Session issued; protected content = HTTP 200 |
test-unentitled | enabled + no active entitlement | Session issued; redirect with access=entitlement |
test-disabled | disabled | No Solynth session; callback gate=removed; protected route denied |
The architecture separates external membership evidence from Solynth authorization. Patreon is intended to become an external source that influences canonical Solynth entitlements rather than being queried directly for every protected-content request.
Still evolving: the Patreon integration foundation exists, but automatic Patreon-to-entitlement mutation/synchronization should not yet be presented as a finished production pipeline.
| Work item | Status | Meaning |
|---|---|---|
| SOL-005E | Complete | Authentication and authorization certification passed 12/12 through the real login path. |
| SOL-005F | Candidate next platform work | Planning/registry work remains available, but immediate demonstration/content onboarding can take priority. |
| SOL-006A candidate | Parked concept | Broader Solynth business/workflow ontology: plans, workgroups, workflows, tasks, threads, actors, automations, integrations and business operations. |
The scope expanded because the system kept exposing real architectural questions. Testing revealed an Auth0 audience mismatch in the original harness; debugging clarified the true session contract; operational friction exposed the need for automatic environment loading; repeated delivery failures hardened Flight Control; and planning discussions exposed a future need for a richer workflow/business-operations model.
In practical terms, the thread did not merely finish a login test. It converted several loosely connected platform ideas into a system that can now be demonstrated as a coherent whole.