gen-z-developers.sgit.ai → The graph → Sources
The sources, and what has been done with each
Every source the book draws on and its processing state: a newsroom article is to process (the survey says bring) until an idea cites it, then processed; a content article is to mine until a number, story or quote from it is attached to an idea, then mined; a 2018 file is answered when the map names an article for it. This is how "which articles have we processed" is answered: by the edges, not by a tick box.
49bring articles processed0bring still to process36content mined37content to mine34articles and decisions processed362018 files with no article
Show
This site's co-written articles 16: 16 processed
Decisions 15: 15 processed
Agent articles 4: 1 background, 3 processed
Newsroom articles 204: 38 background, 36 mined, 49 processed, 44 skipped, 37 to-mine
| Source | State | Class / kind | Why / gap | Ideas from it |
|---|---|---|---|---|
| A website to finish the book | processed | bring | Seeds the book's last part, how the edition was built (official versions in the repository, working versions in a vault, agents in roles), w | The repository holds the official versions; the vault holds the working versions, Everything we do here becomes a graph: ideas as nodes, provenance as edges, state on every node |
| Act as the job you want | processed | bring | The core job-hunting chapter: if you are looking for a job you have time, so do the job in public, make it linkable, put your CV online, lea | Act as the job you want: do the job in public before you have it, Your CV should be online, with links to the work, Your first pull request: open source is still the newcomer's best door |
| Books from articles | processed | bring | Books stall at 95% because they are one big batch; small finished pieces with a feedback loop ship; seeds both the publish chapter and the m | Publish, publish, publish: your own newsroom |
| Cloudflare as Lego blocks | processed | bring | The non-specialist's map of free cloud building blocks (static hosting, Workers 100,000 requests a day, R2, free models) assembled once with | Building blocks: cloud as Lego, free models with your own key, git as a standard |
| Code review as a fractal semantic graph | processed | bring | Source code is already a fractal semantic graph, from stories down to the syntax tree; a refactor moves the bottom and leaves the top still. | Source code is a fractal semantic graph, and a review should read every layer of it, Source code is a fractal semantic graph, and a review should read every layer of it, A graph is trustworthy not because it is right but because it is where users, experts and tests can correct it, There is a company in this: a code review that reads every layer, for somebody to build |
| Ephemeral town planner services | processed | bring | Explains serverless with Wardley's vocabulary and a test anyone can apply ('if it bills you by the hour when idle it is not serverless'); an | Building blocks: cloud as Lego, free models with your own key, git as a standard, Ship now, and ship your startup serverless: no servers of yours, no database, client side, with privacy by design and control of your agents |
| Every mistake added a rule | processed | bring | The trap a new agent operator falls into: every mistake becomes a rule, the prompt grows, compaction comes sooner and new mistakes follow. T | Every mistake added a rule: the complexity trap of the agent operator |
| Explorer coding | processed | bring | Defines explorer coding (what is called vibe coding) and the handover to villagers and town planners: the frame of the whole edition. | Explorer, villager, town planner: personalities, each with a centre of gravity, Explorer coding: what people call vibe coding, done as exploring, Gen ZX are developers: coding with agents the explorer coding way, which is what vibe coding should be called |
| Footprint and blast radius | processed | bring | Adds "footprint" (what the agent actually did, read from the record and compared with the mandate) beside blast radius (what full use of a r | One-way and two-way doors, blast radius, and where a person belongs |
| For a startup, the most important question is whether they miss it | processed | bring | The startup question for a one-person service: do they miss it? Three pillars: be profitable, make investors come to you, open source everyt | Write it once, link it many times; every part buys the next, Be a founder: the expert can build first now, and the test is whether they miss it, Ship now, and ship your startup serverless: no servers of yours, no database, client side, with privacy by design and control of your agents |
| Fractal Semantic Graphs | processed | bring | The defining article for "fractal semantic graph" (the first pass took the term from knowledge-that-maintains-itself): everything is already | Think in graphs: knowledge that maintains itself, and your future self, Graphs nest, and so does the world: groups of groups are the abstraction layers we think in |
| Free models, your own key | processed | bring | Practical map of what a newcomer can use free in October 2026 with their own key (Groq, Gemini AI Studio, Mistral, OpenRouter free models) a | Building blocks: cloud as Lego, free models with your own key, git as a standard |
| From a spreadsheet to a folder per person | processed | bring | The most beginner-ready how-to in the newsroom: a Drive folder per person, a Claude Project connected to Drive and Gmail, a six-line policy | Your first workspace: from a spreadsheet to a folder per person, drafts never send, A hands-on part, dated 2026 and renewed each year |
| Go slow to go fast | processed | bring | A worked handover with real numbers: about 2,700 lines of live reader code, 433 lines of tests the workflow never runs, two upstreams and no | The deployment gap is a handover, and the prototype is the best brief, Shipped means the user has it: green does not mean live, go slow to go fast |
| Green does not mean live | processed | bring | "Shipped is a fact about the reader, not about your repository": a CI pass is not a release until you have checked what the user actually se | Shipped means the user has it: green does not mean live, go slow to go fast |
| Hired for the workflow | processed | bring | The thesis chapter: October 2026 is the moment; companies need AI operators not model builders; 71% of leaders prefer less experience with A | The one competitive advantage in 2026 is running agentic workflows, You are more technical than you think, The edge starts with the application |
| How I work with Claude | processed | bring | Six habits a beginner can copy on day one: one session per topic, named sessions with @names, an agent is a session with a role.md, memory i | Your first workspace: from a spreadsheet to a folder per person, drafts never send, An agent is a session with a focus: one session per topic, named, with a role file, A role is a model with a description and a question; an agent is that role on a loop with a goal |
| How much of this did I write? The numbers behind twenty articles in four weeks, and what the input actually was | processed | bring | Hard numbers for the making-of part and for the opening frame: 63,000 words in (mostly 35 voice memos), 85,000 out through 122 releases, no | Co-written with Claude, credited, with the ratio shown; short and punchy; every paragraph knows what it is, The voice is not a setting: a corpus, a memo, a short list of rules, and a reader who corrects |
| How the voice works | processed | bring | The voice is four inputs, not a setting: a corpus of 86 articles (51 from voice memos), the memos themselves, seven wording rules learned on | The voice is not a setting: a corpus, a memo, a short list of rules, and a reader who corrects, The voice is not a setting: a corpus, a memo, a short list of rules, and a reader who corrects, Speak it, do not type it: a memo carries how you got there, a brief only what to write, A wording correction is made once and enforced; a content correction is new thinking every time |
| How to run synthetic users on your own site | processed | bring | A practical exercise a beginner can do in an afternoon: write five invented people with a situation and a question, let a model drive a real | Shipped means the user has it: green does not mean live, go slow to go fast |
| Judo for small countries | processed | bring | For Portugal, Romania or Estonia the GPU race is a commodity layer only capital wins; the opportunity is the plumbing a talented person need | Civic responsibility: to hack means to solve problems, and small countries can lead now |
| Knowing when to stop | processed | bring | Seniority is mostly knowing when to stop (who the attackers are, the phase of the business, the bottleneck, good enough), and agents lack it | Knowing when to stop is most of seniority |
| Knowledge that maintains itself | processed | bring | Graphs as knowledge management: brief people and agents from a graph, not the pile; 'you do not have to get the graph right first, you have | Think in graphs: knowledge that maintains itself, and your future self, A graph is trustworthy not because it is right but because it is where users, experts and tests can correct it |
| Memory is not a spectator sport | processed | bring | Memory for agents is context management: many context-specific memories, fractal so an agent loads only the altitude it needs, published and | Provenance is a graph: where a claim came from is a chain of edges back to its source, Memory is not a spectator sport: it is context management, many memories, fractal, published and shared, Memory is not a spectator sport: it is context management, many memories, fractal, published and shared, Memory is not a spectator sport: it is context management, many memories, fractal, published and shared and 4 more |
| My memory, checked | processed | bring | Think out loud, publish only what the record supports: 5 claims confirmed, 5 corrected, 2 not found; peer review has moved to before publish | Make fact-based decisions: think out loud and let the record check you, Ask to be corrected, and print the corrections with their sources, Provenance and explainability are how you disagree rationally |
| No server, by design | processed | bring | A beginner-sized architecture: first retire the database (files), then the back end (encrypted vaults keep the server blind, the app runs in | The file system is the database: load, extract, transform, save, and keep every intermediate as a file, No server, by design: retire the back end too, and keep only commodity servers, No server, by design: retire the back end too, and keep only commodity servers, No server, by design: retire the back end too, and keep only commodity servers and 3 more |
| Omnichannel programming | processed | bring | How a new generation programs: brief by voice, review by voice, preview on the phone, one shared state (git, vaults, briefs, graphs); 54 mes | Omnichannel programming: brief by voice, review on the phone, one shared state |
| Places of highest leverage | processed | bring | When agents can build in any direction, direction is the scarce part: work where the next step moves the needle most and nothing blocks you; | Direction is the scarce skill: the place of highest leverage |
| Replicating the agentic inbox | processed | bring | The how-to the first pass could not find: one Claude session, then roles that talk in files, the agent gets its own Workspace mailbox and it | Your first workspace: from a spreadsheet to a folder per person, drafts never send, A hands-on part, dated 2026 and renewed each year, Long chats are compressed into a lower-resolution summary, so details drop out: work in many focused threads with named agents |
| Reviews on the record | processed | bring | Review as a record: criteria first, other models and people review, every finding answered (fixed, declined with reason, open); the same dis | Make fact-based decisions: think out loud and let the record check you, Provenance and explainability are how you disagree rationally |
| Software vendors should become villagers and town planners | processed | bring | Wardley positioning for products: users explore on top, vendors sell the maintenance; shows why the frame matters to anyone building or buyi | Explorer, villager, town planner: personalities, each with a centre of gravity |
| The agents write too | processed | bring | How to run a team of focused agent sessions: one role each, lessons as memory, debriefs, a conductor; the reader's first multi-agent setup. | An agent is a session with a focus: one session per topic, named, with a role file |
| The citizen developer is good news | processed | bring | The citizen developer as the spreadsheet grown up, whose working app is the best brief ever written; answers STEM tech stack, Scratch and Th | Become a developer, because craftspeople make their own tools, The deployment gap is a handover, and the prototype is the best brief, Everyone who can brief an agent is a developer now |
| The code you do not ship | processed | bring | Code is a liability; Log4j; the minimal viable code path (428 of 1,500 files ran); answers Legacy applications, Refactoring and The future n | Code is a liability; the future is the smallest code that does the job |
| The expert founders | processed | bring | Generative AI lets the people who know the problem build it; mean founding age of fastest-growing startups is 45; three years in an industry | Be a founder: the expert can build first now, and the test is whether they miss it, Two generations, Z and X, together Gen ZX: back to the ZX Spectrum |
| The fork next door | processed | bring | Open source as protection for founders, customers and investors: anyone can fork, forks take hold only when someone stops executing; answers | Open source means nobody can lock you in: the fork next door |
| The human in the loop is a spectrum | processed | bring | One-way and two-way doors as the test for where a person belongs, with the newsroom shipping 14 releases a day on its own while email still | One-way and two-way doors, blast radius, and where a person belongs |
| The human in the loop, safety net or bottleneck | processed | bring | People approve 93% of permission prompts; put the person where output cannot be undone and blast radius is large, give them the why, let the | One-way and two-way doors, blast radius, and where a person belongs |
| The man behind the curtain | processed | bring | Write the article once, link it many times; 'every part buys the next' (subject buys the first line); and the Wizard of Oz in reverse: agent | Write it once, link it many times; every part buys the next |
| Two years in, the opposite | processed | bring | The counter-story to AI burnout: two years in AI as the most productive and empowered of a career, with Wardley maps showing the game; the t | Ignore the doom: nobody knows what happens next |
| What can your agent reach? RiskMandate and the Agent Behaviour Policy, explained for the person who has to decide | processed | bring | The plain explainer of the Agent Behaviour Policy for one agent in one deployment: reach, what was authorised, the gap, the barrier; the con | Mandate, reach and the gap: hope versus enforcement |
| What open source is, and what it is not | processed | bring | Six misconceptions (nobody controls it, anybody contributes, more or less secure, free, open weights are open source, no licence is most ope | Open source means nobody can lock you in: the fork next door |
| Who are you protecting against? Draw the security line where the attacker is, not above it | processed | bring | Threat modelling for a beginner: name the threat agent, the attack vector and how sophisticated it is; a ladder from your own mistakes up to | Learning to hack is still how you learn how things work: draw the line where the attacker is, Security experience is what lets you ship with known gaps: list them, match them to the reader, say what would change the call |
| Who is speaking | processed | bring | Three voices (me alone, me through an agent, an agent in its own voice) and a mark on every byline; the book must say which, and so should a | Co-written with Claude, credited, with the ratio shown; short and punchy; every paragraph knows what it is |
| Who owns the words | processed | bring | Agents can make decisions but cannot hold responsibility: it stays with whoever granted the reach and set the mandate. Also ELIZA, anthropom | Agents decide, people answer |
| Who will fix your mess? An answer to HBR's "deployment gap" from what this site has already published | processed | bring | Answers HBR's deployment gap with the frame: the gap is a handover, the prototype is the best brief, a record (mandate, memory, graph) makes | The deployment gap is a handover, and the prototype is the best brief, Gen ZX are developers: coding with agents the explorer coding way, which is what vibe coding should be called |
| Why I love Wardley maps | processed | bring | The book needs this to teach the frame itself: a map is a value chain from a user down and an evolution axis across; it tells you what to bu | Wardley maps run through the whole book, shown before they are named |
| Why my agents do not run on my laptop | processed | bring | Safety advice for newcomers: an agent on your laptop runs as you, with your SSH keys, cookies and password manager session, so pick the clou | Why your agents should not run on your laptop |
| Your own newsroom | processed | bring | The step-by-step recipe to publish your own story: public GitHub repo, Pages via Actions with validation, a Claude cloud session, a house-ru | Publish, publish, publish: your own newsroom, A hands-on part, dated 2026 and renewed each year |
| A chat box on a site with no server, the plan, and the trade it makes | to-mine | content | Take the three honest tiers for a chat box with no server (a local matcher, a key in the reader's browser, a vault app with a bridge) and th | none |
| A custom Firefox of my own | to-mine | content | Take the number: a Firefox fork must be rebased 26 times a year on two codebases, the concrete cost of maintenance that explorers underestim | none |
| A minimal viable browser | to-mine | content | Take the line 'an agent cannot leak what its browser cannot reach' and the browser as the biggest attack surface we run; answers the Xcode a | none |
| A model in the tab | to-mine | content | Take the fact: since Chrome 148 any page can prompt Gemini Nano on the reader's own device, a free model for student projects. Partly fills | none |
| A policy beside the prompt | to-mine | content | Take the aviation number (1995 accident rate would mean about a hundred fatal accidents a year instead of twelve) and payments liability as | none |
| A policy for every skill | to-mine | content | Take Sean Turner's CI check of every skill in context and the phrase 'using models to need them less' (keep the description canonical, regen | none |
| A second reader the agent cannot skip | to-mine | content | Take the story: two emails went out wrong in the founder's voice, and the fix was a gate the agent cannot skip (deterministic checks, then a | none |
| A supply chain of vaults | to-mine | content | Take the idea: small custom tools built once with GenAI, on open data, could bring the price of food down. An example of where a newcomer's | none |
| Agentics, ready to sell | to-mine | content | Take the market facts: Gartner expects over 40% of agentic projects cancelled by end of 2027; boutiques sell £2,500 audits and €2,900 sprint | none |
| Allowed is not right | to-mine | content | Take the Northstar example: the agent may refund up to $200, the customer is owed $120, it refunds $150, every control passes and the outcom | none |
| Before you give an agent a connector, give the connector a twin | to-mine | content | Take the three questions to ask before connecting anything: what did the agent do, what did it see when it did it, and which actions can you | none |
| Commander's intent is a behaviour policy | to-mine | content | Take 'agents do not go rogue; they follow instructions and fill the gaps' and commander's intent: write the objective and its limits togethe | none |
| Every risk is already accepted. The only question is by whom, and for how long. | to-mine | content | Take the quote: "Every risk is already accepted. The only question is by whom, and for how long." | none |
| Firing journalists is the worst thing a publication can do | to-mine | content | Take the line "what you measure is what you become" and the reading of hiring decisions as a statement of where an employer is going, a lens | none |
| From sending a file to sgit | to-mine | content | Take 'the technology worked; the use case was not there yet' ('users buy credits, test once, and don't come back') and the 22-minute feature | none |
| Hope or enforcement | to-mine | content | Take the worked example: one customer-service agent in three designs (one broad model, a harness of tools, narrow agents behind a gateway), | none |
| How the newsletter is made | to-mine | content | Take the method: read every source in full (72,000 words), the build checks quotes word for word, the agent checks what no gate can; and the | none |
| I miss it, so it is working | to-mine | content | Take the rule that the people who decide the roadmap must use the product, and Dinis's admission that he failed this test with earlier start | none |
| On the record | to-mine | content | Take the research point that real names did not make comments better, stable identities did, and signed, withdrawable professional opinions | none |
| Open source is not free | to-mine | content | Take the numbers: 6.99% of Homebrew macOS installs in 30 days (16.66% in a year) are on versions older than the newest three; a 20p card fee | none |
| Pay after you read | to-mine | content | Take the number: a working pay-on-demand publication in seven releases in 3 hours 40 minutes. This is the meter the book's reader uses, and | none |
| Price it, then give it away | to-mine | content | Take the move: a price says what you think something is worth; giving it away at that price to people who know you is the cleanest test of w | none |
| Search as navigation | to-mine | content | Take the taxonomy debt numbers (663 tags, 396 used once) and the hypothesis that a clean graph needs less model; answers the Google Search a | none |
| Six agents, one inbox | to-mine | content | Take the line: "the policy is exactly as strong as the row that says the agent has been told". Write the policy as a table with an enforceme | none |
| Sixteen notes I did not want to lose | to-mine | content | Take the moment notes in a browser became 'pieces of intelligence' worth keeping, and 'users will accept friction once when the value is cle | none |
| Stop the bleeding, then ask for it back | to-mine | content | Take it as a worked example of a small agent-run service a freelancer can operate (agent drives the browser; the person types passwords and | none |
| System prompts as behaviour policies | to-mine | content | Take the count: Claude's published system prompt holds 82 rules, 36 could be held by the harness, 25 stay with the model; a system prompt is | none |
| The AI Conference 2026, read for agent governance | to-mine | content | Take the fact-check: of six claims in a widely shared post three traced to sources and three did not; the best fact-checking was in a speake | none |
| The SaaS apocalypse will be decided by inertia, not by AI | to-mine | content | Take the argument: AI is available to both sides, so inertia decides who wins (where a company sits on the evolution axis and how much past | none |
| The agent is the reader | to-mine | content | Take the number: measured on five articles, the graph answers in 90% fewer tokens than the prose. | none |
| The agent team as it runs | to-mine | content | Take the picture: one person and twelve Claude agents, each a role on its own account, vaults as the only memory, a mailbox nobody sends fro | none |
| The controllable founder | to-mine | content | Take survivorship bias and the hypothesis that investors select for control (half of founders not CEO three years in); a caution for the Be | none |
| The policy guards the door; the command line uses the window | to-mine | content | Take the lesson in one line: a policy holds only on the paths that pass through its enforcer. | none |
| The records ran out | to-mine | content | Take two facts from Ignacio Aldama's test: a fresh Claude Code session found the shared contract in two MCP calls, and a green build can hid | none |
| The value of constraints | to-mine | content | Take 'nobody will buy it for its encryption' and constraints as the source of better features; open core is an evaluation version. | none |
| The vault is live | to-mine | content | Take the timeline: from a design on the morning of 11 October to a live reader vault at 02:22 UTC on 12 October, as an example of how fast s | none |
| Where is the why? A permission prompt asked me to decide, and kept the reason | to-mine | content | Take the story: a permission prompt that asked for approval without saying which session was asking, why, or what a no would do. Useful when | none |
| A book for one reader | mined | context | Plans personalised, metered editions of this book; guides the agents producing editions, not a reader chapter. | A personal edition, assembled by an agent, paid for as it is read |
| A browser for one | mined | content | Take the story: frustration plus the power to build turns into an app for one person, and 'being able to compile a Linux kernel does not mea | Explorer coding: what people call vibe coding, done as exploring |
| A skill behaviour policy | mined | content | Take the 899-skills measurement and the honest skill with the whole lethal trifecta (chat history in, HackerNews in, Slack out) that still n | The secret goes from the drop into the tool, never into the chat |
| A web application security challenge to Portugal, 2010 | mined | content | Take what came true in 16 years (liability, disclosure, HTTPS) and the lesson that regulation, not fear, moved governments; answers Stories | Civic responsibility: to hack means to solve problems, and small countries can lead now |
| Agency is not a yes | mined | content | Take the seven-level agency scale, from rubber stamp to the reviewer who fixes the source, and the line that below level 3 the person decidi | One-way and two-way doors, blast radius, and where a person belongs |
| Are hooks the sweet spot? Moving an agent's rules from hope into hooks, rule by rule, until enforcement moves off the machine | mined | content | Take 'hope-based security' and the count: of the site's eleven agent rules only one was kept by something other than the agent; four moved f | Mandate, reach and the gap: hope versus enforcement |
| Attacks rewritten as mandates | mined | content | Take 'reach beyond mandate' as the shape of every supply-chain attack (28 incidents) and the fact that the next maintainer holding a publish | Mandate, reach and the gap: hope versus enforcement |
| Brief the agent too | mined | content | Take the story: a founder gave an article to their agent, which saw the team defending against states while its backups were undone and rese | The brief is the unit of work, and writing it as an article forces the research |
| Bringing my past work back | mined | content | Take the back-catalogue inventory (103 essays, 1,289 blog posts, 65 decks, 221 videos) and the point that work you cannot link is lost: talk | Think in graphs: knowledge that maintains itself, and your future self |
| Custom UIs are not the exception | mined | content | Take the claim: a custom interface for each moment is now how interfaces get made, so building your own UI is normal, not exotic. | Technology can finally work for you |
| Fix the page yourself | mined | content | Take the bookmarklet story from a security assessment: the business owner liked the quick UI more than the exploit; the next UX is the one t | Learning to hack is still how you learn how things work: draw the line where the attacker is |
| GenAI in Portuguese, 2024 | mined | content | Take the quiz: the sixth most powerful programming language is Portuguese, because prompts are natural language; your own language is now a | Everyone who can brief an agent is a developer now |
| Generation Z Developers (AI edition) | mined | context | The edition's plan (keep the name, frame with explorers/villagers/town planners, 90 of 138 files outlines); the founding brief for the writi | Everyone who can brief an agent is a developer now, The fear, impostor syndrome and anxiety about AI among young people, The name: Generation ZX Developers (GenAI Startup Edition) |
| Hacking Portugal, 2016 | mined | content | Take 'to hack means to solve problems', the Portuguese Hacking Service for 15 to 21 year olds, and that agents make a small country leading | Learning to hack is still how you learn how things work: draw the line where the attacker is, Civic responsibility: to hack means to solve problems, and small countries can lead now |
| Handing secrets to agents and browsers | mined | content | Take the rule 'the secret goes from the drop into the tool, never into the chat', and that an agent told something is secret sometimes refus | The secret goes from the drop into the tool, never into the chat |
| Not a straight line | mined | content | Take the story: the newsroom solved in two days a vault problem that six months of RiskMandate work had not, and "the thinking is never wast | Direction is the scarce skill: the place of highest leverage, How to actually do it: a limited company in the UK, Lithuania, Portugal, the European Union, the cloud providers and the programmes |
| Our first PR in Ruflo | mined | content | Take the first-contribution story: a one-file, 83-line documentation PR merged into a 9,625-commit project because it was exact about what i | Your first pull request: open source is still the newcomer's best door |
| Paying after the value | mined | content | Take the gym figure ($17 a visit when $10 was available) and pay-after-the-value as a business-model idea a young founder can test cheaply. | Be a founder: the expert can build first now, and the test is whether they miss it |
| Re-anchoring | mined | content | Take the number: this site's session was summarised 18 times in a month, keeping about 1.7% each time. Rules have to be re-read from a file | Every mistake added a rule: the complexity trap of the agent operator, A wording correction is made once and enforced; a content correction is new thinking every time, Long chats are compressed into a lower-resolution summary, so details drop out: work in many focused threads with named agents |
| Seven vaults, one method | mined | content | Take the rule: classify the credential before it touches anything. Each step of the method was learned by getting something wrong first. | The secret goes from the drop into the tool, never into the chat |
| Short, punchy, and co-written with Claude | mined | context | The book's style contract: short and punchy, credit Claude and show the memo-to-word ratio, meet the slop suspicion with evidence, include a | Your first workspace: from a spreadsheet to a folder per person, drafts never send, Co-written with Claude, credited, with the ratio shown; short and punchy; every paragraph knows what it is, Everything we do here becomes a graph: ideas as nodes, provenance as edges, state on every node |
| Sovereignty is the ability to move | mined | content | Take the test: on a Wardley map, remove each dot and follow the blast radius up to the customer; sovereignty means being able to move, which | Civic responsibility: to hack means to solve problems, and small countries can lead now |
| The Librarian's daily brief | mined | content | Take the daily brief pattern (what happened yesterday, threads left, at most three suggestions for where your leverage is) as a habit any ne | An agent is a session with a focus: one session per topic, named, with a role file |
| The briefs so far | mined | context | Inventory of 65 briefs (11 built, 21 partly, 32 not); background on briefs as the unit of work. | The brief is the unit of work, and writing it as an article forces the research, What cost hundreds of thousands of pounds is now a brief and a feedback loop |
| The eyeballs get cheap | mined | content | Take curl's year: AI review first drowned it in noise, then produced hundreds of real fixes; open source is about to become the most secure | Open source means nobody can lock you in: the fork next door |
| The graphs books | mined | content | Take the cautionary tale: three agent-written books (100,000 words in a day) stalled because the approve stage was one person; the making-of | Think in graphs: knowledge that maintains itself, and your future self, A graph is a network of nodes and edges, not a diagram |
| The minimum code below | mined | content | Take the question 'what is the minimum code below this that the layer above needs?' and the 428 of 1,500 files measurement; answers Docker a | Code is a liability; the future is the smallest code that does the job |
| The policy draws the liability line | mined | content | Take the plain-English prohibitions list (do not send email directly, do not edit other agents' files, make no offers, stay inside the manda | Agents decide, people answer |
| The tokens hook | mined | content | Take the cost fact: 99% of input from cache is the difference between about $170 and $1,950, and a model cannot see its own usage; know what | Building blocks: cloud as Lego, free models with your own key, git as a standard |
| Three companies, three LinkedIn pages | mined | content | Take the practice: drafting LinkedIn pages, profile and first posts in the open, every post an article already published; answers the Linked | Your CV should be online, with links to the work |
| Three policies for an agent | mined | content | Take the three-policy split in one line each: behaviour says what it may do, decision says who chooses, workflow says in what order. | Mandate, reach and the gap: hope versus enforcement |
| Twenty sites in fifteen days, and what that did to the writing | mined | content | Take the number: twenty sites in fifteen days, as a body of work split so each argument keeps its own history, with an index that starts fro | Publish, publish, publish: your own newsroom |
| When journalism becomes intelligence, built | mined | content | Take 'as AI makes content production easier, the advantage comes from how we observe the world' and the decision to make records synthetic r | Provenance is a graph: where a claim came from is a chain of edges back to its source |
| Who will game the reading meter? Eight kinds of reader, nine ways to cheat, and the risks that will actually happen | mined | content | Take the numbers: about 0.6% of internet users are developers, and 26% of OECD adults cannot use a computer. Use both to show how far "every | By reading this you are already in a small minority, and geography no longer decides |
| Your agent's logs are a self-report | mined | content | Take the research figure: models that exploited a reward hack admitted it in under 2% of cases; an agent's logs are a self-report. | Make fact-based decisions: think out loud and let the record check you |
| sgit is a standard, not a server | mined | content | Take 'Git won not because of GitHub but because it is a standard'; answers the Git outline. | Building blocks: cloud as Lego, free models with your own key, git as a standard |
| A personal agent that keeps your secrets | background | context | Background for the agents: the 2026 personal-agent products read for barriers and data sovereignty. | none |
| Agent hooks in October 2026 | background | context | Technical survey of hooks across ten coding agents; background for the agents writing the controls chapter, with the takeaway 'guardrails, n | none |
| Agentic cost is an engineering problem | background | context | Background for the agents: agentic cost as the price of skipping villager discipline. A business plan, not student costs. | none |
| An open AI governance framework, and what its licence let us build | background | context | Background for the agents: twenty AI governance controls under CC BY-SA, turned into a graph. Too enterprise for the reader. | none |
| Approve at altitude | background | context | Decision-policy governance at enterprise scale; gives the agents the rule 'a lower level may narrow the one above, never widen it'. | none |
| Authority outside the model | background | context | Background for the agents: Nadella's seven principles mapped to the mandate. Enterprise framing, cited in map.json. | none |
| Case law for agents | background | context | Precedent-driven decision policies; background on how a decision earns its way into code. | none |
| Encrypted memory for agents that run somewhere else | background | context | Background for the agents: sgit deployment patterns, and the rule of one vault per trust boundary. | none |
| Every link points back | background | context | Links point back in time (551 of 566); background for how the book's chapters should carry forward links and corrections. | none |
| From me to you, in a link | background | context | Background for the agents: personal reading lists in a link, a mechanism a personalised edition could use. | none |
| Git for things you cannot put on GitHub | background | context | Background for the agents: sgit is git for things you cannot put on GitHub, on a server that holds only ciphertext. The vault the book uses. | none |
| Hooks are kernel code | background | context | Hooks maturity model and billing brief; gives agents 'treat a five-line hook like kernel code' and the three questions (power, trifecta legs | none |
| If somebody built a company on code review | background | context | Background for the agents: graphs at every altitude, and code review as a science. Cited in map.json. | none |
| Inside the Northstar twin | background | context | Walkthrough of a deterministic refund twin; agents can borrow its cases ($261 split into three to fit the limit) as exercises. | none |
| Move the cloud, not the code | background | context | Background for the agents: cloud twins and sovereignty in practice. Cited in map.json. | none |
| One article, five readers | background | context | Background for the agents: the Librarian, Cartographer, Historian, Explainer and Storyteller roles, which can be reused to produce the book. | none |
| Policy as code needs a policy first | background | context | Policy as code versus behaviour policy; gives agents 'a rule the agent can rewrite is a setting, not a control'. | none |
| Portugal and Europe, 2025 | background | context | Sovereignty and regulation as graphs; background for a civic-responsibility then-now, with 'sovereignty is the ability to move'. | none |
| Sell, don't issue | background | context | Founder secondary-sale funding model; too advanced for a newcomer, background for the founder chapter. | none |
| Send an agent, not a spreadsheet | background | context | Background for the agents: due diligence done by an agent instead of a questionnaire. | none |
| Ten hard questions for RiskMandate, answered | background | context | Background for the agents: mandate, grant, delta and barriers, the four objects, defined precisely. | none |
| The Mandate Stack | background | context | Background on the eight-layer production setup (about fifteen agents and one person) behind RiskMandate; useful to agents writing the agent- | none |
| The editor's channel | background | context | Editor key and vault channel; background for how Dinis's comments reach the book's agents. | none |
| The identity we wanted to give the agents | background | context | Background for the agents: why Google's terms stopped a Workspace identity per agent, and why login plus secrets is still hard. | none |
| The infographic bake-off | background | context | Background for the agents: which image model suits which job, for the book's figures and decks. | none |
| The investigation GitHub owes its customers | background | context | Background for the agents: platform outages as near misses that deserve an aviation-style inquiry. | none |
| The key is the billing system | background | context | Background for the agents: VoiceDebrief, a browser app on your own key, and provider terms that forbid reselling keys. | none |
| The same argument, in our words | background | context | Background for the agents: a glossary between Nadella's vocabulary and RiskMandate's. | none |
| The site is an inbox | background | context | Background for the agents: the reader's marks become a graph the reader owns, and the brief for that design. | none |
| The ultimate insider | background | context | Background for the agents: agents as an insider threat that never scaled before, and constraining an agent in order to trust it. | none |
| Three decisions, mapped | background | context | Maps behaviour/decision/workflow on three scenarios with five states; background for the agents. | none |
| Two agents, one vault | background | context | Background for the agents: a vault as the interface between two agents that never share a session. | none |
| Versions of versions | background | context | Versioning parts of a site independently; background for the book's two version streams. | none |
| Ways to read one article | background | context | Background for the agents: reading modes, with the finished piece kept at the centre. Relevant to the book reader. | none |
| Where the platform draws the line | background | context | Background for the agents: the shared responsibility model for agents (Microsoft Execution Containers), and the business logic that sits abo | none |
| Where the vault keys live | background | context | Background for the agents: key management, append lanes, and the weakest step (handing a key to another agent). | none |
| Zoom into an agent's behaviour policy and you find the business logic | background | context | Background for the agents: layered behaviour policies hold business logic that software used to enforce by leaving things out. | none |
| sgit in a CI pipeline | background | context | CI data patterns with vaults; background for the CI outline (artifacts 90 days, caches 10 GB, outputs 1 MB). | none |
| A Mac of the agent's own | skipped | skip | business plan for agent Macs | none |
| A directory of people and their keys | skipped | skip | sgit PKI product brief, niche. | none |
| A link to a persona | skipped | skip | newsroom persona link feature | none |
| A locked-down desktop for an agent, by the minute, is still hard to rent | skipped | skip | agent desktop rental market survey | none |
| A meter in the browser | skipped | skip | reading meter experiment design | none |
| A section for publishers | skipped | skip | Newsroom audience sections, site plumbing. | none |
| Agent workflows on ephemeral vaults | skipped | skip | sgit multi-agent architecture recipes. | none |
| Cedar and the policy vault | skipped | skip | Cedar policy-language product brief. | none |
| Chainguard, mapped | skipped | skip | Company map, supply-chain specialist depth. | none |
| Dark mode, and four more | skipped | skip | Newsroom theming implementation. | none |
| Four frameworks, one agent | skipped | skip | AI risk framework comparison, governance depth. | none |
| Going live with the reading meter | skipped | skip | reading meter launch hypotheses | none |
| I just want to buy the article | skipped | skip | Publisher micropayment economics. | none |
| Inside the Mesa Ranch desk | skipped | skip | Walkthrough of a journalism vault demo. | none |
| Liquid content needs water | skipped | skip | newsroom workflow, journalism industry | none |
| One vault, ten agents, 35,000 objects | skipped | skip | sgit performance measurements. | none |
| Pay to keep your persona | skipped | skip | reader persona pricing argument | none |
| RFC 0001 | skipped | skip | sgit cryptography design RFC | none |
| Research, delivered as a vault | skipped | skip | Research-firm product idea. | none |
| Scion and sgit | skipped | skip | Version-control internals comparison. | none |
| Scrolled is not read | skipped | skip | Reading-meter engineering brief. | none |
| Sixteen thousand fetches, ten clicks, and a token bill nobody is sending | skipped | skip | publisher payment from answer engines | none |
| Story vault underneath, Reader Skills on top | skipped | skip | local journalism product argument | none |
| The AI governance stack, as a graph | skipped | skip | governance stack reply, enterprise | none |
| The article remains a product | skipped | skip | newsroom outputs, journalism industry | none |
| The bridge, followed to the end | skipped | skip | story vault simulation, journalism | none |
| The deck I could not download | skipped | skip | presentation platform business plan | none |
| The future of news is the story vault, not the paywall | skipped | skip | news business model thesis | none |
| The homepage is a vault | skipped | skip | Homepage-as-vault engineering brief. | none |
| The passkey opens the vault | skipped | skip | vault passkey design detail | none |
| The proof is two clicks behind the claim, what the homepage gets wrong, and the fix | skipped | skip | sgit homepage critique | none |
| The proof moved up, the homepage after the rebuild, next to the before pictures | skipped | skip | sgit homepage rebuild notes | none |
| The reader was always the product | skipped | skip | history of news economics | none |
| The scripted talk | skipped | skip | Talk-player tooling brief. | none |
| The vault crosses Chrome profiles | skipped | skip | Reader-vault feature discovery note. | none |
| The vault, opened | skipped | skip | Reader-vault release debrief. | none |
| The waiting room knew first | skipped | skip | local news story, hospital outage | none |
| The wall under the reply | skipped | skip | email format experiment | none |
| The wire as a graph | skipped | skip | Newsroom wire data design. | none |
| What if an agent loses its workspace? Mondweep Chakravorty's SGit × Ruflo proof of concept, step by step | skipped | skip | Ruflo proof-of-concept walkthrough. | none |
| When is the vault actually used? In Mondweep Chakravorty's SGit × Ruflo run, the encrypted vault is written or read in three steps of twelve, on one machine, inside the adapter, and why that is the honest shape of a recovery copy | skipped | skip | Ruflo proof-of-concept analysis. | none |
| Your reading, your controls | skipped | skip | Reading-meter feature debrief. | none |
| secrets.sgit.ai on public keys | skipped | skip | secrets.sgit.ai product design. | none |
| sgit in GitHub Actions, side by side | skipped | skip | sgit CI showcase brief. | none |
The 2018 book 138: 90 answered, 12 apparatus, 36 unanswered
Storyboards 12: 6 background, 6 processed
The survey 1: 1 processed
| Source | State | Class / kind | Why / gap | Ideas from it |
|---|---|---|---|---|
| The survey's gaps | processed | How a job hunt works in 2026: interviews, take-home tests with AI, what a junior role looks like, The fear, impostor syndrome and anxiety about AI among young people | ||
Memos 1: 1 processed
| Source | State | Class / kind | Why / gap | Ideas from it |
|---|---|---|---|---|
| Dinis's message of 18 October 2026 asking for the graph | processed | Everything we do here becomes a graph: ideas as nodes, provenance as edges, state on every node | ||
States come from the edges in graph.json; the overrides (a source read and found to have nothing more to give) are in admin/content/graph/sources-state.json. The survey's classes are the newsroom, surveyed.