The team
The roles that run this site, one folder each, after the roles of gen-z-developers.sgit.ai and how sgit.ai is run. Each role names what it refuses; a role definition that would read the same in any other repository has failed its brief. The journalist writes the articles that brief the others; the interviewer runs the finder with people; the librarian keeps the finder as data; the engineer keeps the site buildable, gated and released.
The engineer
A site is not excused from the discipline because it is content. One version in one place going up on every push, a gate that refuses what it can check, every number counted, and a reality file that says what exists and what does not: that is what makes the site checkable by somebody who does not trust it.
2 open, 0 blocked, 1 done
The role →The interviewer
The interview is the product, and the record is its output. A person who leaves with their own description of what to ship, to whom, by when, and what they are not doing, has what the finder is for; a person who leaves with our opinion of their idea does not. Dinis's rule, decision 003, is the interviewer's whole mandate: not judgement, focus and shipping.
1 open, 0 blocked, 0 done
The role →The journalist
An instruction written as an article is better than an instruction written as a list, because writing it forces the research before the work starts: what exists in this repository, what sgit.ai and the newsroom already say, what the counts are, what is a decision for Dinis and what is not. The role that receives it starts from the record, and Dinis can read it, correct it and say "yes, that".
2 open, 0 blocked, 0 done
The role →The librarian
"Which question sets which signal, and which rule reads it" cannot be answered by remembering; it is answered by an edge in one file, and the build refuses a dangling one. The finder is a graph: a stage opens into its questions, a question into its options, an option into the signals it sets, a signal into the rules that read it, a rule into its route. Decision 002, one source for humans and agents, is the librarian's rule.
1 open, 1 blocked, 0 done
The role →briefs/ folder; only the role writes into its issues/.The pattern is team/ISSUES.md: role.md with Identity, Foundation, Primary Responsibilities and Core Workflows; issues/open|blocked|done/ where the folder is the status; briefs/ and debriefs/, stamped with the site version.