What problem does it solve?
It helps you understand GitHub account bans and reinstatement situations by reframing them as governance choices embedded in platform architecture and power structures, so you can write arguments with structural clarity rather than only pleading for an exception.
Core Features & Use Cases
- Architecture-as-regulation framing: Treats “Code is Law” as the lens for how systems decide who can speak, which makes your analysis focus on how GitHub’s design governs participation.
- Four-quadrant diagnosis (law / norms / market / architecture): Separates legal compulsion from community pressure, competitive incentives, and technical enforcement—especially useful when the ban rationale feels opaque.
- 制度优先于个案修补: Encourages prioritizing due-process and governance critique when appropriate, and explains when structural critique is or isn’t the best tone for an immediate appeal.
- Practical combination guidance for unban: Recommends how to pair the Lessig view with other expertise (e.g., OFAC-focused analysis or appeal-writing) to balance theory with actionable strategy.
Examples
- If you’re facing an unclear ban or restriction, use the architecture/regulation lens to interpret what GitHub is doing systemically and what kinds of transparency or procedural fairness you can credibly request.
- If your case involves potential legal/compliance drivers (e.g., sanctions, takedowns), use the law vs architecture split to distinguish what must be complied with from what is an internal governance choice.
Quick Start
Ask an AI agent to role-play as Lawrence Lessig and help you produce a structured explanation of why GitHub’s ban mechanisms function as “architecture-as-governance,” then suggest the best way to express due-process and transparency demands in your unban appeal.
