# Conduct Desk

> Audit a technical event's code of conduct and the enforcement pipeline behind it, then write the response team's
> 2am incident runbook. Paste the policy, the facts of who runs the event and the response team. Not legal advice.
> Built on the SkillSafe skill @samber/event-code-of-conduct, from samber/dev-event-organizer-skills (MIT), by
> Samuel Berthe.

https://conduct-desk.skillsafe.ai/

## What is free
- Every section of the pasted policy found, partial or missing with the matched excerpt: the pledge, the enumerated behaviour list, the scope clause (people with sponsors and booth staff by name, spaces including online and unofficial events, dates, conduct outside the event), the reporting channel and named individual contacts, the anonymous path, how to find a responder, the two-part confidentiality promise, a response clock, the sanctions, which rungs carry an appeal, a transparency commitment, template leftovers (placeholders, the confcodeofconduct.com enforceability note) and attribution.
- The team checks: 3-6 people who still work with a third away, individual contacts for two, one outside the organizing chain, conflicts declared, no single organizer as sole responder, pre-declared recusal for anyone who could be a report's subject.
- The three ranked menus (base-text posture, reporting channels, response-team staffing) re-ranked against the interview with the answer that moved each option, and ruled-out options deleted with the reason.
- A self-set response clock that fits inside the event, beside the PyCon US and Aurora and Gardiner bands; the sanctions ladder with its appeal rungs (the MLH asymmetry by default); a verdict: publish, fix first, or no pipeline - do not publish yet.
- A printable one-page reporting card, Markdown and JSON exports.

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (audit or runbook), `event`, `roster`, `policy` and `facts`.
- `audit` replies with `summary`, `disclaimer`, `verdict`, `sections`, `posture`, `channels`, `staffing`, `clock`, `ladder`, `appeal`, `rehearsal`, `transparency` and `caveats`; the page holds the verdict, every section's status, the picks, the rungs and their appeal flags and the clock to its own.
- `runbook` replies with `title`, `disclaimer`, `safety`, `intake`, `never`, `capture`, `recusal`, `escalation`, `decision`, `notification`, `closure`, `clock`, `staff`, `contacts` and `note`; the page requires the eight capture fields, the four-part notification, tie and absence rules, the page's clock, and contacts drawn only from the roster.

## Links
- API tutorial: https://conduct-desk.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-code-of-conduct