Patterns translate Ethotechnics engagements into reusable approaches that help you share responsibility, rehearse care, and sustain the people doing the work.
Spot friction faster, redistribute upkeep, and keep pause points ready before harm spreads.
Each pattern pairs narrative context with facilitation steps so teams can practice accountability before crisis hits.
Choose a persona to get the most relevant Ethotechnics patterns, spotlights, and capability specs without having to scan the full library.
Design services with built-in safeguards, pause points, and reversals.
Audit readiness with visible refusal, contestation, and care signals.
Trace evidence behind each pattern and jump into deeper context.
Equip coalitions to share maintenance and protect collective capacity.
Adapt these to your own context or work with us to tailor the cadence, rituals, and safeguards. Each one emerged from real collaborations across care-critical systems.
Maintenance-as-strategy
“Redistributing upkeep was the only way to keep us from burning out. The pattern gave us scripts and checkpoints to make it stick.” — Systems engineer, public health lab
Consentful deployment
“This gave us language and leverage to say not yet—and the roadmap to get to yes without sacrificing care.” — Responsible AI steward
Care escalation
“We stopped waiting for emergencies. The pattern made care escalations normal and documented.” — Mutual aid coordinator
Pair a lightweight contribution portal with facilitation scripts that keep responsibility visible from the first suggestion through the safeguard taking effect. This pattern tunes the experience to each participant, surfaces dissent before it festers, and keeps the cadence grounded in real-world repair work.
Launch the forum with an entry survey that captures participant roles, stakes, and maintenance history. Responses auto-populate a shared role map so moderators can tailor prompts, highlight impacted communities, and match facilitators to the right rounds of review. Stakeholders receive personalized onboarding briefs that reflect their obligations, decision rights, and repair commitments.
Built-in mechanics surface dissent without retaliation: contributors can file minority reports, trigger pause votes, or escalate to a stewardship council when obligations are breached. Every adopted patch includes a maintenance rehearsal schedule, shared checklists, and quarterly reflection prompts so the forum keeps owning repair work after launch.
Dashboards show how responsibility and decision ownership shift over successive rounds. Track which roles authored proposals, who carried deliberation labor, where vetoes originated, and how deployment duties redistribute as the system matures. Export snapshots to feed governance reviews or public transparency reports.
Moderators can download facilitation guides for each stage as PDF or editable agendas, bundle them into onboarding packets, and trigger calendar invites for live repair sessions with Ethotechnics. Every invite includes prep questions, stakeholder roles, and follow-up commitments so the forum stays linked to embodied maintenance practice.
Create visibility into harm, pause when needed, share burdens fairly, and make repair accountable.
Systems always need upkeep. We make clear who is being asked to hold it together and redesign the load.
Move away from heroics by building practices and policies that let teams carry care together.
Ethotechnics patterns translate frontline experience into repeatable structures you can adapt across teams. Each pattern includes guidance for rehearsing maintenance, distributing responsibility, and measuring how care shows up in practice.
Browse the domains we cover and jump straight to the capability specs that match the work you're doing. These filters update the capability list below without a page refresh, and every capability link still works as an anchor if JavaScript is unavailable.
Showing all capability specs.
No capability specs match this combination yet. Select “All” or try another filter to see more guidance.
Select a capability to jump down the page and highlight matching specs. Layer on a domain to narrow the list to the contexts we explicitly cover. If scripting is blocked, every link still acts as an anchor so you can keep exploring manually.
Each capability anchors a cluster of patterns. Use these specs as checklists when designing, auditing, or iterating on services that must remain stoppable, reversible, fair, contestable, and explainable.
Ensure systems can be paused quickly before harm compounds.
Make it possible to undo decisions and repair records without friction.
Distribute maintenance and compliance work away from already burdened people.
Give people real channels to question, appeal, and renegotiate decisions.
Ensure decisions can be traced, justified, and audited by those impacted.
Use this blueprint to host practice sessions where teams learn to notice strain early, surface maintenance debt, and adjust shared agreements as conditions shift.
Start with situations that mirror the services you steward. Each scenario should include recent incidents, maintenance history, and frontline perspectives so the practice stays grounded in lived experience.
Try different ways of sharing load so the team can see how backup support, feedback cadence, and detection speed shift risk for the people relying on your service.
Ground every state transition in maintenance language so teams know when to pause, repair, or escalate.
Pair qualitative rituals with quantitative guardrails. These SLIs keep teams honest about whether the system still respects the people who depend on it.
Measure the elapsed time between a stop trigger and the actual halt of the system or feature.
Track the share of decisions or transactions that can be fully reversed without manual workarounds.
Understand whether contestation pathways meaningfully change outcomes for impacted people.
Track the average duration between appeal submission and initial human response.
Monitor who shoulders maintenance, escalation, and emotional labor across the service.
Subscribe for updates on frameworks, workshops, and tools that help you rehearse accountable systems.
