Crew teams the owner can dial: design, data science, security, platform - with a scorecard per crew member #2677

Owner (trevato), 2026-10-19: "we should have a design team on this thing 24/7 ... teams. like a security team, data science team, design team, etc. all of these are trajectories that i could increase or decrease in magnitude based upon how i feel but also right now they just arent being hit. crew members that are incentivized to work as a team ... the data science team could work with the design team to make some exceptional visualizations ... more diversity in the crew members would be great. diversity in models and in prompts. then we could also start tracking which crew members are better to start tuning even more."

Done: (1) a team is a named group of crew members with a charter (what it owns, what it reviews), and a dial the owner sets (share of builder slots and budget, 0-100%), shown and set on one settings page; first teams: design, data science, security, platform; (2) the planner fills each team's queue from the direction and the charter, so every dial above zero gets work every day; (3) cross-team work: an issue can name two teams (e.g. data science + design for a visualization), and both review the pull; (4) diversity: each crew member records its model and prompt version, and a team can hold members on different models/prompts; (5) a scorecard per member on a board: pulls landed, landed per $, review rounds, red-check rate, reverts, time to land - so the owner can tune who does what; (6) the design team reviews every pull that changes a page against one design system. Test: setting design to 30% gives design issues ~30% of builder starts over a day; the scorecard counts a landed pull for its author.