Talent Marketplace Legal and Security Review
A release decision, candidate-data and GDPR model, employment and AI-law analysis, code-grounded security findings, launch blockers, and a 30/60/90-day plan.
Product research, technical discovery, implementation plans, and readiness reviews for active SolidProfessor initiatives.
Each collection keeps its conclusion, supporting evidence, scope boundaries, and next actions together without mixing unrelated initiatives.
GDPR, employment-law, AI-governance, and security requirements for releasing Talent Marketplace as a separate B2B product, with a strict real-candidate beta gate and light SOC 2 preparation.
A release decision, candidate-data and GDPR model, employment and AI-law analysis, code-grounded security findings, launch blockers, and a 30/60/90-day plan.
Printable version for leadership review, product planning, employment and privacy counsel, and security or model-risk review.
Legal and security requirements for offering the LCMS as a separate B2B SaaS product, with a narrow GDPR-first beta gate and light SOC 2 preparation.
A release decision, GDPR operating model, required customer documents, code-grounded security findings, launch blockers, and a 30/60/90-day plan.
Printable version for leadership review, product planning, and legal or security counsel.
Core Platform's input to SPPLT-19123: bucket inventory across both AWS accounts, S3 vs R2 recommendation, migration sequencing, and SOC 2 posture. Measured from live AWS 2026-08-26/27.
Discovery and implementation material for supporting instructors who enter SolidProfessor through an existing LMS integration.
Explains identity versus role, just-in-time access, returning users, anonymous launches, NRPS, SSO, rostering, and the current backend gap.
The trio-facing companion: integrates the knowledge base and the backend plan against a fresh code review; recommends a scope, sizes the work, names where the research diverges, and covers the known and anonymous (LAUSD/Schoology) cases.
The engineering companion: the proposed file-by-file backend changes — role mapping, deployment boundaries, identity handling, security contract, tests, and definition of done. A reference for the implementing team.