# Crew Chart

> Design the standing organizing team of a recurring technical event - the structure that persists between editions -
> then write the standing-team design or the role cards for its charter. Enter the event's scale and legal shape, every
> role with its lead, backup, hours and written scope, and every organizer's pleasantness answer, return and interests.
> Built on the SkillSafe skill @samber/event-team-structure (samber/dev-event-organizer-skills, MIT).

https://crew-chart.skillsafe.ai/

## What is free
- The bus-factor map, lead first: every role without a backup, roles that exist only as "whoever picks it up", roles with no written scope, the missing standard roles and the span of one coordinating layer.
- Load per person: stacked roles (three or more led), hours over the workload budget (volunteer teams), one person as everyone's backup.
- The yearly "is organizing still pleasant?" check, each organizer's named return, the conflict-of-interest register and undisclosed interests, departing organizers without a successor or with a handover outside 6-12 months.
- The entity menu (deleted for a company-run event), decision-rights shape with where each role decides, succession mechanisms (planned rotation deleted without a continuity layer) and the paid-hire gate (paid rungs deleted with no money; the first hire an event coordinator).
- Six standing-team checks, all self-set; map CSV, Markdown and JSON exports.

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (design or cards), `team`, `roles` and `facts`.
- `design` replies with `summary`, `diagnosis`, `busfactor`, `entity`, `shape`, `succession`, `burnout`, `coi`, `hire`, `checks`, `signals` and `caveats`; the page holds every role's lead, backup and bus factor, the four picks, every organizer's answer, the undisclosed interests and the checks to its own.
- `cards` replies with `cards`, `coi_clause` and `note`; the page holds every card's lead, backup (or "to be named") and decision layer to its own and requires a scope, a boundary and a clause that covers disclosure and abstention.

## Links
- API tutorial: https://crew-chart.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-team-structure