Privacy and record design

Not every workshop record belongs in the same place

The design separates project sources, controlled contributions, restricted operational information and any later release artifact. The portal should not become the default store for every workshop need.

Allowed

Public-safe project record

Examples
Plans, source code, blank templates and synthetic fixtures
Intended location
Git repository

Not enabled

Controlled workshop record

Examples
Private drafts, shared snapshots, synthesis provenance and review responses
Intended location
Separate workshop D1

Route not established

Restricted operational record

Examples
Contact, attendance, access needs, compensation, consent and safeguarding records
Intended location
Approved restricted system outside Git

Route not established

Release artifact

Examples
De-identified, reviewed account for a defined audience
Intended location
Separately approved release location