Demo template project: copy-to-workspace + locked project flag

[paynejd]

The demo project itself and the mechanism that puts it in a user's workspace.

ACs

• An OCL-owned template project, pre-configured, with the AI Assistant already run on all but ~2 rows
• "Try the demo" copies it into the signed-in user's workspace once; re-triggering does not create duplicates
• The copy is exempt from all four preview caps (projects, rows per project, match operations, AI calls)
• A project-level locked flag — data, not preview-specific code — blocks delete, row changes and config changes, enforced in both the API and the UI
• Content per the parent issue (Jussara's SIGTAP→LOINC project, pending permission)

Note: this is stricter than the "score config and algorithms stay editable" idea from the 2026-09-15 call — the demo is fully locked.

Parent: demo project + guided walkthrough · enforcement: see the Mapper enforcement wiring ticket

[ocl-automation]

Automated Triage — 2026-09-16

Dimension	Score
Complexity	4
Scope	4
Clarity	4
Dependency	2
Risk	3

Decision: decision/planning-needed
Type: type/feature
Signals: signal/large-scope, signal/well-specified

Multiple interacting components needed: template project creation, workspace copying logic, preview cap exemptions, and locked project enforcement across both API and UI. Well-defined requirements with clear acceptance criteria, though some details like the exact locking mechanism are unspecified. Moderate risk since incorrect locking could break user workflows or allow unintended modifications.

---

Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-4 (openrouter).