Lesson 2: Policy pack (scope creep, closure, privacy)

These are written as short policy cards you can paste into Notion and Mighty.

Policy 1: No Scope Creep

Name: Policy – No Scope Creep Purpose: Protect helpers from getting trapped and protect requesters from unclear expectations. Policy:

• A match is a timeboxed container with a defined scope.
• New needs require a new request.
• Helpers are allowed to say: “That’s a separate request.”

Steward enforcement: If scope grows mid-match, steward closes the original match cleanly and creates a new request for the additional work.

Policy 2: Clean Closure Required

Name: Policy – Close the Loop Purpose: Prevent invisible labor, social fog, and resentment. Policy:

• Every match ends as one of: Completed, Cancelled, Rescheduled, Closed.
• Completed matches must be marked complete and logged.
• Stale requests must be closed cleanly (not left hanging).

Minimum closure behavior:

• Mark status
• One sentence note (optional)
• CompletionLogged checked when ledger is done

Policy 3: Privacy and Pattern Safety

Name: Policy – Privacy Boundaries Purpose: Keep capacity honesty alive and prevent gossip dynamics. Policy:

• PulseChecks are private.
• ContributionLedger is private.
• Pattern conversations happen privately with care.
• No public scoreboards, callouts, or “you should help more” culture.
• If someone is overloaded, we reduce commitments first.

Steward enforcement: Any public comparison, shaming, or gossip about private signals is redirected and stopped immediately.