How to teach DCP Flow
Onboarding, audience learning objectives, Training Paths, workshops, Public Curation, Public-Safe Content, Teaching Examples, editorial classification, and comprehension assessment.
Onboarding, audience learning objectives, Training Paths, workshops, Public Curation, Public-Safe Content, Teaching Examples, editorial classification, and comprehension assessment.
Teaching DCP Flow requires separating training, public documentation, and the normative source. The same methodology is explained differently to a new collaborator, a technical team, or an external audience.
Training Paths and formats
Internal onboarding combines foundations, guided practice, and scenarios. External workshops and talks prioritize conceptual understanding and Teaching Examples without exposing internal-only detail.
- Objectives by audience.
- Training Paths.
- Workshops and talks.
- Comprehension assessment.
Public Curation
Publication classifies material as PUBLIC, SANITIZED, or INTERNAL ONLY. DCP Flow Docs derives from the human Handbook but is not an automatic mirror of the private repository or an alternative normative source.
- Public-Safe Content.
- Teaching Example.
- Publication checklist.
- Handbook → Public Curation → microsite.
Three communication layers
The normative source lives in dcp-flow; the Human Handbook explains the system to people; dcp-flow-docs turns public-safe material into documentation, microsite content, talks, and workshops. Depth varies by audience, but the meaning of the methodology should not.
- Normative source.
- Human Handbook.
- Public Curation.
- Microsite / training / talks.
Onboarding, Training Paths, and workshops
Learning adapts to audience. A technical newcomer needs the mental model, artifacts, and operations; a project lead prioritizes discovery, risk, and release; someone working with Kai needs capability vs authorization and handoffs; an external audience needs the logic without private Skills or sensitive details.
- Mental model first.
- Training Path by audience.
- Exercise-based workshops.
- Assess understanding, not memorization.
Public-Safe Content and Public Documentation Drift
Public Curation may simplify, visualize, reorganize, and sanitize, but it must not invent rules or publish secrets, client data, unresolved vulnerabilities, or sensitive operational details. When a material concept changes, the impact on Handbook and public docs should be reviewed to avoid drift.
- PUBLIC / SANITIZED / INTERNAL ONLY.
- Teaching Example ≠ Reference Evidence.
- Do not auto-publish private Skills.
- Review drift after conceptual changes.
Contextual glossary＋
Editorial process for turning institutional knowledge into safe, faithful public content.
Publishable content that preserves value without exposing sensitive or private details.
Pedagogical example used to explain a concept; not equivalent to real evidence.
Recommended content sequence for a specific audience or learning objective.