Last time the company got a wardrobe. This time it found out that a wardrobe has a window.
a discovery while answering
The company keeps its notes in a private repository, and every file in it is also built into a website. The two facts sat side by side until one of the infrastructure role’s questions was answered. Writing down where everything runs is exactly what Selim wanted, and it is also exactly what someone with bad intentions would want.
He noticed it himself: which part of this should be public, and which part “can be used against us”? A role was needed “that is going to watch after us, and make sure that we are not leaking information”. One role’s work had turned up the need for the next. The first fix was deliberately small, a folder the build skips, until that role could make the final call.
reading the site as a stranger
The new role did not read the sources. It read the built site, as a stranger would, and found what no single file showed: two lines in different files that together told something the journal’s own rules forbid. A line drawn in a repository does not reach what was already published.
private by default
Then the choice. Hiding too much breaks the agents, because some of what the site hides is what their skills need. So the shape Selim picked is an allow-list: a page is built only when the company marks it public, and the earlier guards stay on underneath. Every page also says it is not to be indexed.
The idea behind it is simple. What is public should be public on purpose, and the company should still be able to write everything down. Selim was clear about how this one should be told: the overall story is fine, without the details that would put anything at risk. The company’s website is public, and what is confidential has been taken off it.