# The team, startups.sgit.ai

> The roles that run this site: journalist, interviewer, librarian, engineer.

*Source: <https://startups.sgit.ai/team/index.html> · site v0.1.3 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.*

---

# The team

The roles that run this site, one folder each, after [the roles of gen-z-developers.sgit.ai](https://gen-z-developers.sgit.ai/team/index.html) and [how sgit.ai is run](https://sgit.ai/team/index.html). 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.

*role*

### [The engineer](engineer/index.md)

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 →](engineer/index.md)

*role*

### [The interviewer](interviewer/index.md)

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 →](interviewer/index.md)

*role*

### [The journalist](journalist/index.md)

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 →](journalist/index.md)

*role*

### [The librarian](librarian/index.md)

"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 →](librarian/index.md)

No session has yet run as a role: the first release was built by one session acting as all four, and the engineer's agent article says which decisions were whose. The issues are the first board. Work for a role arrives as a brief in its `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.


---

*[Site index for agents](https://startups.sgit.ai/llms.txt) · [HTML version](https://startups.sgit.ai/team/index.html)*
