Files
protocol-droid/seeds/appreciative-apology.yaml
Protocolbot 02794e565e feat: initial release of Protocol Droid v0.2.0
A tool for authoring, sharing, and curating social protocols.

Features:
- Protocol library with search, tag filtering, and sort by date/relevance
- Protocol authoring with structured fields (title, description, steps, outcome, practice, source, tags)
- Protocol forking with provenance tracking
- Collection creation with searchable protocol picker and ordering
- User accounts with roles (admin, member, viewer)
- YAML import/export for portability
- Self-hostable on LAMP/Cloudron, works in subdirectories
- Responsive design with hamburger menu on mobile
- About page

Security:
- CSRF protection via Origin/Referer validation
- Session regeneration on login/register
- Secure session cookie params (HttpOnly, SameSite, Secure)
- Visibility enforcement on private/unlisted items
- YAML object injection hardening
- Login rate limiting
- Path traversal protection
- Input validation and length clamping
- Vote value constraining

Stack: PHP 8.x + MySQL/MariaDB, vanilla JS frontend, no external dependencies.

Hippocratic License (HL3-CORE).
2026-07-06 13:18:08 -06:00

33 lines
1.2 KiB
YAML
Executable File

id: appreciative-apology
title: Appreciative Apology
description: >-
A protocol for repairing harm through structured acknowledgment, moving
beyond reflexive apologies toward genuine accountability.
source: Restorative Justice Project
source_url: https://restorativejustice.org/
tags: [conflict]
forked_from: null
image: null
steps:
- headline: Name the harm
description: >-
The person apologizing specifically describes what they did, without
minimization or justification.
- headline: Acknowledge the impact
description: >-
They describe the impact they understand their action had on the
other person or group.
- headline: Express commitment
description: >-
They state what they will do differently, concretely. No future
promises without specific actions.
- headline: Invite response
description: >-
They ask the other person if there is anything they have missed, and
listen without defending.
outcome: >-
The harmed party feels heard and acknowledged. The relationship has a
path forward with concrete commitments.
practice: >-
Avoid the word "but" — it negates everything before it. "I'm sorry, but..."
is not an apology. Practice pausing after each step.