# The weight of the documents, and the past projects as the team's memory > The weight of the documents, and the past projects as the team's memory: one of the editor's briefs of 2026-11-04__in-session, published in full as given. *Source: · site v0.1.692 · generated from the same content as the page, so the two cannot drift.* --- The editor, Dinis Cruz, in the conductor's session (conductor@book.the-ultimate-insider), about 02:38 UTC on 4 November 2026, with a screenshot of pages 17 and 18 of the full book (chapter 4: the brief, the reality file and the corrections; the banners taken from the newsroom). A voice transcription, kept as given ("Eskit" is sgit). Never edited; where it turns out to be wrong, the finding goes in `BRIEF-CORRECTIONS.md`. > I think on cases like this, it'd be good to show sometimes the meat size of it, the kind of the size and weight of these documents, maybe some key screenshots or key elements of it that might be worth doing. That's worth quoting, right? Some of these big documents that we create, and also the size of it. And then I think this is where it goes, where you can take a screenshot of it and then put it maybe two or three pages or a collage of it, right? But I think it's important to show for these documents that we create. And again, sometimes the planning that we do and the articles that we write, sometimes you get a team to write articles. And also take into account that also you should do the same thing when there's an article from the news, the Eskit newsroom. In fact, we should be showing cases where the newsroom.eskit articles were used here, because there was a lot of cases where that happened, right? So maybe get the team to research when I've made references and when they read from it, right, if you can, because it's very important that A, we link back to it, but B, we show, where is it and the type of article is it, and maybe some collage or some infographics of it or some screenshot of that newsroom.eskit.ai, or even articles from other websites. In fact, I believe that in the beginning the brief contained reference to coding.eskit.ai and nfrs.eskit.ai. So it's important to again show that that's been used as memory. That's what provides the guidance. At the moment, I have a lot of power in this because I'm benefiting from all those past projects. So we need to show that weight here. ## How the conductor reads it (not his words) - **The weight of the documents**: the brief, the reality file, the plans, the articles the team wrote, shown with their size and a few pages, quoted or in a collage, where they first appear. - **The past projects as memory**: every place the newsroom's articles (newsroom.sgit.ai) and other sgit.ai sites were referenced by him or read by the agents, linked, with where and what kind of article, shown in screenshots, a collage or an infographic. A first count of the talk's repository at the day's end finds newsroom.sgit.ai on about 2,666 lines and a dozen other sgit.ai sites (raw, to be registered before print). - The talk's brief (BRIEF.md at cb5b996) names newsroom.sgit.ai, ruv.sgit.ai and *.sgit.ai; coding.sgit.ai and nfrs.sgit.ai, which he recalls, appear elsewhere in the record (the historian finds where). - Routed: historian 038, researcher 058, librarian 029, storyteller 065, designer 069, writer 026. --- *[Site index for agents](../llms.txt) · [HTML version](https://the-ultimate-insider.book.sgit.ai/brief/19-the-weight-of-the-documents-and-the-memory.html)*