artifacts/standard-named

Continuity in Practice — Contributor Training (v1.1 Updated)

artifacts/standard-named/20260710__CONTINUITY-OFFICE__TRAINING__CONTINUITY-IN-PRACTICE__CONTRIBUTOR__v1__contributor-training.md

Rendered from markdown source. Open raw source on GitHub.

Continuity in Practice — Contributor Training (v1.1 Updated)

Purpose

Help teams stay in control of their work as systems become more complex — without adding friction, bureaucracy, or loss of autonomy.

Participants learn to:

  • Recognize when actions matter
  • Use simple signals (🝚 🝁 🜬 🜹) to guide decisions
  • Act freely while maintaining legibility
  • Prevent small issues from compounding into system drift

---

Format

  • 90–120 minute live workshop
  • Interactive and scenario-based
  • Practical, not technical

---

0. Opening (10 min)

Goal

Disarm expectations and establish relevance

Key Message

  • Not compliance
  • Not about slowing you down
  • About staying in control as things get more complex

Framing

Most problems don’t start big — they start small and compound:

  • Oversharing
  • Unclear access
  • Casual AI use
  • “Just for now” decisions

Nobody is trying to be careless — they just don’t see the system they’re operating in

---

1. How Work Actually Happens Now (15 min)

Goal

Shift mental model

Key Idea

Work is no longer separate domains:

  • Tools
  • People
  • AI
  • Policies

It is one interconnected system

Insight

Small actions don’t stay small — they propagate

---

2. Why Things Drift (15 min)

Goal

Make the problem felt

Patterns

  • Implicit decisions
  • Invisible actions
  • Missing context

Drift Loop

Action → no trace → confusion → workaround → drift

Key Line

“Nothing breaks immediately — it just gets harder to understand.”

---

3. Core Signals & Invariants (20 min)

Goal

Provide a simple, usable model

🝚 Boundary

Who can access this?

🝁 Consent

Should this be used this way?

🜬 Breach (Signal)

Does this feel like it crossed a line or shortcut?

A breach is not a failure

🜹 Witness (Invariant)

Will this be understandable later?

Witness is not a place — it’s whether context can be found

Framing

You don’t need to check everything — just notice when something matters

---

4. The Operating Pattern (15 min)

Goal

Translate model into behavior

The Pattern

  1. Act — do your work normally
  2. Notice 🜬 — when something feels slightly off
  3. Place 🜹 — leave a trace somewhere appropriate

Core Principle

Make decisions freely — make them understandable

---

5. Real Scenarios (40 min)

Goal

Make it practical and relatable

Scenario 1 — Using AI

  • What happens to the data?
  • Where does it go?

Scenario 2 — Sharing information

  • Who can actually see it?
  • What happens over time?

Scenario 3 — Granting access

  • Temporary vs permanent
  • Ownership and cleanup

Scenario 4 — Automation / shortcuts

  • Moving data across systems
  • Integrations

For Each Scenario

  • Where is 🝚 unclear?
  • Where is 🝁 assumed?
  • Was there a 🜬?
  • Is there 🜹?

---

6. Practical Rules (10 min)

  1. Don’t share by default — share intentionally
  2. If you don’t know who can see it, assume too many people can
  3. Don’t use AI on anything you wouldn’t forward externally
  4. Temporary access is rarely temporary
  5. If it matters, don’t let it disappear

---

7. Witness in Practice (10 min)

Goal

Remove friction around “where does this go?”

Key Insight

Witness is not a single place — it can exist anywhere

Examples

  • Slack message
  • Comment in a doc
  • Ticket note
  • Email
  • Metadata / structured note

Optional Pattern

Witness channel (email, Slack, etc.) as a fallback

If you don’t know where to put it, put it somewhere it can be found

---

8. Autonomy & Culture (10 min)

Goal

Prevent resistance

Key Message

This does not replace:

  • Trust
  • Autonomy
  • Ownership

It strengthens them

Reinforcement

You are still trusted to do your work

This just makes sure your work doesn’t create hidden problems later

---

9. Team Calibration (10–15 min)

Goal

Ground in their reality

Prompts

  • Where does work feel messy today?
  • Where do things get lost?
  • Where are people unsure what to do?

Optional:

  • Identify 2–3 high drift zones

---

10. Close (5 min)

Reinforce

You don’t need to change everything

Just be slightly more aware in the moments that matter

Final Lines

“A breach is a signal, not a failure.” “If it matters, don’t let it disappear.”

---

Outcome

Participants leave able to:

  • Make better decisions in real time
  • Recognize when something matters
  • Leave useful context without friction
  • Reduce system drift through everyday actions

---

Positioning

This is not traditional training

This is:

How to operate effectively in systems that are more complex than they appear