# Public Safety Map

This map defines what Episode 2 can use from past Salbotics experience.

## Source Basis

Public-safe lesson sources:

- harness engineering talk materials
- existing prompt templates, context-pack templates, and checkpoint rules
- public demo/runbook style from local testing tutorials
- ebook production privacy rules
- general lessons from building local-first tools and learning labs

These sources are used for patterns, not disclosure.

## Allowed Lesson Themes

- AI work needs a goal, context, path, checkpoints, and done criteria.
- Long projects need handoff notes so a future session does not start cold.
- Public examples should use fake data and generic names.
- Testing can be simple: start the thing, observe it, compare expected vs actual, record evidence.
- A tutorial should teach a behavior, not expose a project.

## Forbidden Detail Categories

Do not publish:

- real client or partner names
- local machine paths
- private repo names or private branch names
- emails, phone numbers, buyer data, account IDs, keys, tokens, or passwords
- exact factory, sales, payment, or operational numbers from real work
- internal architecture or product strategy that gives away a Salbotics advantage
- screenshots from private tools unless separately reviewed and approved
- private notes, health notes, career notes, or personal planning material

## Safe Replacement Patterns

| Risky detail | Safe replacement |
|---|---|
| Real client name | "a small business", "a workshop", "a team" |
| Real repo path | "your project folder" |
| Real customer data | fake table with sample rows |
| Real dashboard screenshot | plain text checklist or generic diagram |
| Real strategy | general principle or review question |
| Real number | rounded fictional number marked as fake |

## Public Review Checklist

Before publishing a tutorial:

- [ ] No real client, partner, account, or personal identity appears.
- [ ] No local path appears.
- [ ] No email address, phone number, key, token, password, or buyer detail appears.
- [ ] No private repo or internal product name appears.
- [ ] All examples use fake data.
- [ ] Any external tool claim is either verified or removed.
- [ ] The lesson still helps if all project specifics are hidden.

## Stop Rule

If a lesson only works because it reveals a private detail, do not publish it.

Rewrite it as a general pattern, or leave it out.
