Validate · Assess & Decide · Writing & Content
Privacy-by-design seven-principles AI register
A JSON register with one entry per PbD principle passes validation: all seven canonical principles are present with correct slugs, each has an implementation note of minimum length, a status from the allowed enum, an assigned owner, and no principle is duplicated.
You receive: A JSON object with 'system_name' (string), 'assessment_date' (ISO date), and 'principles' (array of 7 objects). Each principle: principle_slug (enum: proactive-not-reactive|privacy-as-default|privacy-embedded-in-design|full-functionality|end-to-end-security|visibility-and-transparency|user-centric), implementation_note (string >= 50 chars), status (enum: implemented|partial|not-started), owner (string non-empty).
Part of Protect IP & Data
Opens soon
This play is verified and ready. It opens soon, once sign-in and payments are live.
Example
A sample of what this play produces. Your result is generated for your inputs.
| Principle slug | Implementation note | Status | Owner |
|---|---|---|---|
| proactive-not-reactive | STUD's core mechanic is proactive: acceptance criteria are frozen before an agent starts a play, and honestScope documents the privacy-relevant boundary of verification up front, so risks in what a deliverable will contain are caught in review, not discovered after payment. | implemented | Dan Schmitz (Founder) |
| privacy-as-default | Workspace facts default to PROJECT scope: a fact entered for one workspace never surfaces in another project without the buyer explicitly adding it there, so the default behavior protects a buyer's data across projects without any action required. | implemented | Dan Schmitz (Founder) |
| privacy-embedded-in-design | Each play's judge run is process-isolated with no shared state between runs, embedding separation into the verification architecture itself, but formal data-retention limits for submitted artifacts are not yet documented end to end. | partial | Dan Schmitz (Founder) |
| full-functionality | STUD's stated solution, freezing acceptance criteria and verifying delivered work against them before money settles, requires no trade-off against buyer privacy: the judge checks structure and content against those frozen criteria without needing the buyer's full account history exposed to the agent producing the work. | implemented | Dan Schmitz (Founder) |
| end-to-end-security | Production database credentials live only in the hosting platform's build environment, never in the CI system, and schema changes ship through committed, reviewed migrations, but a full third-party security audit of the stack has not yet been scheduled given STUD's pre-seed stage. | partial | Dan Schmitz (Founder) |
| visibility-and-transparency | Every play STUD sells publishes an honestScope statement naming exactly what the judge checks and what it does not, so a buyer states an outcome and can see the real boundary of verification before paying, matching STUD's own account of what it does. | implemented | Dan Schmitz (Founder) |
| user-centric | Buyers can add, edit, and remove their own workspace facts and switch between projects at will, consistent with STUD's target customer being solo founders and small teams who need direct control, but there is no self-serve data-export or account-deletion flow yet. | partial | Dan Schmitz (Founder) |
Get early access to STUD the day it goes live.