gen-z-developers.sgit.ai → The graph → Tasks

The tasks: what the articles ask for, and what has been done

Every numbered item in a co-written article's brief is a task, read from the article by the build, with the role the brief names. Its state is what the repository shows (the evidence column names the file or page), checked by the librarian; a task nobody has touched is open. 7 done, 18 in progress, 4 blocked, 60 open, of 89.

9journalist2dinis12publisher62editor3librarian1reviewer

Show

Write it as an article 2 of 5 done

#	Role	Task	State	Evidence
1	journalist	Publish this article and the four that follow at `/articles/`, each with a markdown twin. Done when the site's gate passes with all five.	done	articles/ has nine articles with markdown twins; the gate passes (site v0.2.1 to v0.2.6)
2	journalist	Put a brief in `team/publisher/briefs/` for article 2, and in `team/editor/briefs/` for articles 3, 4 and 5. Done when each role's page lists its brief.	done	team/publisher/briefs/book__v1.0.0__release-the-book-we-already-released.md; team/editor/briefs/ has the three
3	journalist	When a role's debrief comes back, read it against the article, and correct the article if the work found it wrong.	open	no debrief has come back yet (team/*/debriefs/ are empty)
1	dinis	Read the five articles and correct what is wrong.	in-progress	the seven decisions of 18 October (decisions/) came from reading the first five
2	dinis	Open a session as the publisher and point it at article 2; open one as the editor and point it at article 3.	open	no publisher or editor debrief yet

Release the book we already released 0 of 10 done

#	Role	Task	State	Evidence
1	publisher	Copy the bookkit from graphs.sgit.ai (`admin/build/bookkit/`, and what `gen_book.py` needs) into `admin/build/`, with its origin and commit. Done when `build.py` imports it and nothing in it was rewritten for style.	open	admin/build/ has no bookkit
2	publisher	Build the print PDF of v1.0.0 into `v1/publish/`, with the CC BY 4.0 copyright page. Done when it renders with every font embedded.	open	no v1/publish/
3	publisher	Match it to 2018: page count against 139, chapter order against `print-toc.json`, each chapter's first page against the 2018 one, and a page-by-page side by side as images. Done when the debrief shows the comparison and the differences left are explained.	open	no v1/publish/
4	publisher	Diff the text: the 2018 GitHub issue 3 says fixes were made in the Leanpub build repository and not brought back to the source. Compare the 2018 PDF's text layer with the frozen markdown, chapter by chapter. Done when every difference is listed; each one is a …	open	no debrief
5	publisher	Find out what each store accepts today: Leanpub (PDF, EPUB, MOBI?) and Amazon KDP (the paperback interior; the Kindle ebook format). Done when the debrief quotes each store's current guidance with its date.	open	no debrief
6	publisher	Build the screen PDF, the EPUB, the Kindle format and the sample from the same source. Done when each opens, and the EPUB passes a validator.	open	no v1/publish/
7	publisher	Write `v1/publish/manifest.json` from the build, and teach `validate.js` to check its text hash. Done when the gate fails on a manifest that names the wrong text.	open	validate.js has no manifest check for v1/publish/
8	publisher	Write the metadata sheet and the upload checklist: Leanpub on uploaded files first, then the paperback interior update. Done when the checklist is in `team/publisher/debriefs/book__v1.0.0__upload-checklist.md` and I can follow it without asking.	open	no upload checklist in team/publisher/debriefs/
9	publisher	Create `admin/content/book/publications.json` and show its rows on the versions page. Done when, after I upload, one row says what went where.	open	no admin/content/book/publications.json
10	publisher	Write an agent article when the release is done: what you built, how it compares with 2018, what you learned about the stores.	open	no publisher agent article

One board for the book 0 of 7 done

#	Role	Task	State	Evidence
1	editor	Create `board/issues/open\|blocked\|done/` in the vault, with the write key I give you, and add the content issue format to `team/ISSUES.md`. Done when the guide describes both kinds and an example content issue is in the vault.	open	the vault has board/issues/ folders from v0.1.0 but no content-issue format in team/ISSUES.md
2	editor	Teach the build to write the site's board: `board/index.html` from every role's work issues, with the three columns, the filter, the counts and the "waits on Dinis" strip. Done when moving an issue with `git mv` and rebuilding moves its card, with nothing else…	open	no board/index.html on the site
3	editor	Write the vault board script: in `admin/build/`, run against a vault checkout, it writes `board/BOARD.md` from the content issues and refuses one with a missing field or a quote not in its file. Done when the vault's board is its output, and each check has a f…	open	no vault board script in admin/build/
4	editor	Teach the gate the work-issue checks above. Done when each has a failing example that it refuses.	open	validate.js has no work-issue checks
5	editor	Bring in the 43 GitHub issues of the 2018 repository from `admin/content/github/` as content issues in the vault, generated rather than typed, open ones in `open/` and closed ones in `done/`. Done when every issue has a file, and the vault board's count matche…	open	the 43 GitHub issues are captured (admin/content/github/) but not in the vault as content issues
6	editor	Move the seven open questions from the vault's board into blocked issues that wait on me, each in the role that needs the answer. Done when the "waits on Dinis" strip shows them and the hand-written board is gone.	open	the vault's BOARD.md still lists the questions by hand
7	editor	Add the site's board to the navigation and to `llms.txt`.	open	no board in the navigation

Everything unfinished in one place 0 of 6 done

#	Role	Task	State	Evidence
1	editor	Teach the build to write the inventory: `inventory/index.html` and `inventory.json`, one row per item, the fields above, grouped by part, filterable by kind and by "no decision yet". Done when every file of v1.0.0 has a row and the counts on the page match the…	open	no inventory/
2	editor	Mark the overlaps. A draft file that is also an outline is one row, with both kinds. Done when the inventory's count of rows is the number of distinct items, and the page says how it was counted.	open	no inventory/
3	editor	Add the content issues from the vault board's snapshot, once it exists, including the 2018 GitHub issues. Done when each issue is a row with its link.	blocked	waits on the vault board (one board for the book, task 1)
4	editor	Create `admin/content/notes/` with a README saying how a page of handwritten notes becomes a file, and ask me whether I have found the printed copy. Done when the answer is recorded, either way.	open	no admin/content/notes/
5	editor	Mark the candidates for "article first": the outlines with no newsroom article, as a filter, so I can read them together. Done when the filter shows the 31.	in-progress	the graph's sources page lists the 2018 files with no idea and no article (the 'article first' candidates); the inventory filter itself is not built
6	editor	Add the inventory to the navigation and `llms.txt`.	open	no inventory in the navigation

Read, comment, decide 0 of 7 done

#	Role	Task	State	Evidence
1	editor	Create `board/decisions/` in the vault, with the write key I give you, and add the decision format to `team/ISSUES.md`. Done when an example decision is in the vault and the guide describes it.	open	no board/decisions/ in the vault
2	editor	Add the decision to the desk: a verb per chapter, next to its state, kept in the browser like everything else on the desk and carried in both exports; nothing sent. Read `CLAUDE.md`'s rule on the reader first. Done when a decision survives a reload and appears…	open	assets/reader.js has states and comments, no decision verb
3	editor	Show decisions on the item pages and in the inventory: the chapter page shows its recorded decisions under the map's reading; the inventory's decision column links each. Done when recording a decision file and rebuilding fills both, with nothing edited by hand…	open	chapter pages show the map's reading only
4	editor	Teach the vault board script (from [one board for the book](/articles/one-board-for-the-book.html)) to refuse a decision without Item., Version read., Comment. and Decision., and one whose verb is not on the list.	blocked	waits on the vault board script (one board for the book, task 3)
5	editor	Prepare the first batch: the four Introduction chapters marked "to review" on the desk's filter, and the five `show-in-book` issues on one page with what I need to decide. Done when I can answer all nine in one sitting.	open	no first-batch page
6	editor	Run the first batch with me, record the nine decisions, act on them in the vault, and write a debrief stamped `book__v1.0.0__decisions-01.md` with the counts by verb and what did not work about the loop. Done when the debrief is in `team/editor/debriefs/`.	blocked	waits on task 5 and on Dinis's sitting
7	editor	Hand the journalist any "article first" as a brief in `team/journalist/briefs/`.	open	team/journalist/briefs/ is empty

Start from the storyline 1 of 6 done

#	Role	Task	State	Evidence
1	editor	Map the storyline. From the 18 topics and the first storyline, one row per proposed chapter of the second edition: its punchline in a sentence, the concept it introduces, the evidence it uses, the character it is for, and the newsroom articles it draws on. Don…	in-progress	admin/content/graph/chapters.json is the librarian's proposed chapter map, one row per chapter with punchline, topics, gravity, character and the 2018 files it answers; rendered at graph/chapters.html; the editor's map decides
2	editor	A storyboard per part. When the chapter map has parts, one storyboard each, in `admin/content/storyboards/`, from the cast. Done when I can flick through the whole second edition, part by part.	in-progress	storyboards exist for the opening, where do you land and connect the dots (the first part); none yet for the other parts
3	editor	Take my comments on the storyboards through the read, comment, decide loop; a panel I reject is changed or cut in its file, and the decision recorded. Done when the first part's storyboard has had one round.	open	no decision recorded on a storyboard
4	editor	Add the four missing bring articles to the map: places of highest leverage, from a spreadsheet to a folder per person, why my agents do not run on my laptop, who owns the words. Done when `gen_map.py` names them and the map shows them.	done	gen_map.py names places-of-highest-leverage, from-a-spreadsheet-to-a-folder-per-person, why-my-agents-do-not-run-on-my-laptop and who-owns-the-words (site v0.2.12)
5	editor	Review the survey's classes with me, a part at a time, the bring and content ones first. Done when each has my decision, recorded in the vault with the text decisions.	open	no class decisions in the vault
6	journalist	Write the gap articles, one at a time, starting with the fear and the job hunt in 2026, from a memo of mine on each.	open	no gap article yet; the gaps are nodes on the ideas register (fear-of-ai, job-hunt-in-2026) marked article first

You are lucky to be here 0 of 5 done

#	Role	Task	State	Evidence
1	editor	Record the decision in the vault: the book opens with wonder and privilege, not with fear and not with technologies. Done when it is a decision on the text, with my words, in the vault's `board/decisions/`.	open	no board/decisions/ in the vault; the idea wonder-not-fear is 'accepted' on the register pending that record
2	editor	Revise the first storyline (`02__a-first-storyline.json`): its cold open is the fear; replace it with the opening above, keeping the fear as what the reader hears, not where the book starts. Done when the storyboard opens with "you are lucky to be here".	open	02__a-first-storyline.json still opens with the fear
3	editor	Prepare interview questions on this opening, to make me justify it: why optimism is honest and not a sales pitch; which jobs that never scaled I mean, with three examples; what the European opportunity is, concretely; and the stories behind each transformation…	open	no second interview script in team/editor/briefs/
4	editor	Place the 2018 material this answers: the outlines The Zone, BBS and modems and the draft Dopamine, and the Introduction's "Overwhelming curiosity". Done when the chapter map says where each goes.	in-progress	chapters.json places The Zone, BBS and modems, Dopamine under lucky-to-be-here; the editor's map decides
5	journalist	Write the articles this opening needs evidence for: the history of the seven transformations, dated and sourced; the attention economy and what is known about its effects; the jobs that never scaled. One memo of mine each.	open	no history, attention-economy or jobs-that-never-scaled article

Where do you land? Wardley maps run through the whole book, shown before they are named, and the first thing a reader should work out is their centre of gravity 0 of 5 done

#	Role	Task	State	Evidence
1	editor	Record the decisions in the vault: Wardley maps run through the whole book and are shown before they are named; the reader's centre of gravity is introduced early. Done when both are decisions on the text, with my words, in the vault.	open	no board/decisions/ in the vault
2	editor	Give every chapter in the chapter map a centre of gravity: explorer, villager, town planner or all three. Done when the chapter map has the column, and the counts show whether the book leans one way.	in-progress	chapters.json gives every proposed chapter a gravity; counts on graph/chapters.html
3	editor	Draft three learning paths, one per centre of gravity, through the chapters. Done when a reader who knows where they land can see what to read first.	open	no learning paths
4	editor	Put a map in every part's storyboard, using the storyboard `map` kind. Done when each part shows at least one map, named or not.	open	only the where-do-you-land storyboard has a map panel
5	editor	Prepare interview questions that make me justify this: the claim that Wardley's three describe personalities better than the business tests; what my own centre of gravity is and how it has moved; an example of each from teams I have built. Done when the script…	open	no interview script on this

Connect the dots backwards 0 of 4 done

#	Role	Task	State	Evidence
1	editor	Place the chapters this answers: the 2018 Learning, Books and Pen and Paper chapters, and the outlines Love maths, The Zone and Thinking as a programmer. Done when the chapter map says where each goes.	in-progress	chapters.json places Learning, Books, Pen and Paper, Love maths, The Zone and Thinking as a programmer; the editor's map decides
2	editor	Add "read it on paper" to the opening, as advice on how to read the book, before the first chapter. Done when the opening's storyboard has the panel.	open	03__the-opening.json has no read-it-on-paper panel
3	editor	Prepare interview questions on this: what multidisciplinary looks like for an explorer, a villager and a town planner; my own path, connected backwards, with its dots; why paper, when the book will also be sold as a PDF. Done when the script is in your `briefs…	open	no interview script on this
4	journalist	Find what the creativity study actually measured before the book uses it; and the evidence on reading on paper and on screens. Done when each is an article, or a note saying what was found and what was not.	open	no article on the creativity study or reading on paper

Where the thinking came from 0 of 6 done

#	Role	Task	State	Evidence
1	editor	Add an influence column to the chapter map: the influences behind each chapter, from the table above. Done when every chapter that draws on one names it.	open	chapters.json has no influence column yet; the ideas from the register name the influences in their statements
2	editor	Plan a box per chapter, "where this comes from", naming its influence and linking the register entry; and an appendix, Where the thinking came from, as the reading list. Done when the chapter map marks the boxes and the appendix has an outline.	open	no boxes planned
3	editor	Real people appear as quote cards, not as cast members. Done when the storyboard guidance says so.	open	no storyboard guidance on real people
4	editor	Interview me on the stubs: Neil Peart, playing in a band, diverse and distributed teams, and what David Rice's keynote changed for me. Done when the script is in your `briefs/` and the transcripts are in the vault.	open	no interview script on the stubs
5	editor	Put the reader's exercise in the book, at the end of the learning part. Done when the chapter map places it.	in-progress	the idea know-where-your-ideas-come-from is placed under connect-the-dots-backwards (the learning chapter); the editor's map decides
6	journalist	Write the brief for the register: the six findings above, each with its 2018 file, for the influences site to take in. Done when I have approved it and it is delivered to that repository.	open	no brief delivered to the influences repository

Generative AI, not AI 0 of 4 done

#	Role	Task	State	Evidence
1	editor	Plan a short section, early, on what generative AI is: the bucket (AI, machine learning, deep learning, generative AI), how a language model works in plain words, why a better prompt helps, where hallucinations come from, and the corrections above. Done when t…	in-progress	chapters.json proposes the chapter what-generative-ai-is, first in the frame, with two ideas; no storyboard yet
2	editor	Use "generative AI" across the book, and "AI" only where the wider field is meant. Done when the style notes for the drafts say so.	open	no style notes for the drafts exist
3	editor	Add the name to the title interview (`002__the-title-the-subtitle-and-the-language.md`): Gen AI edition, or not; and whether Gen Alpha is a future reader. Done when the question is in the script.	in-progress	Dinis decided the title on 19 October 2026: Gen Z Developers (GenAI Edition) (decision 010); the editor's issue 002 (title, subtitle, language) has the title to record and the subtitle still to settle
4	editor	Ask for the image, or remake it. The slide is Lee Brimelow's post; the book can only reproduce it with his permission. The painting itself is in the public domain, so the alternative is to extend The Starry Night ourselves, with a named tool, and show that. …	blocked	the image is found (site v0.2.10: slide 70 of Deterministic GenAI Output With Provenance, Lisbon 2024, Lee Brimelow's Starry Night extended with Generative Fill); the task is now to ask for it or remake it, which waits on Dinis's decision

Follow the rabbit holes 0 of 4 done

#	Role	Task	State	Evidence
1	editor	Place this as the chapter the 2018 outline Facts promised, next to Popper and the questioning in [where the thinking came from](/articles/where-the-thinking-came-from.html). Done when the chapter map has it.	in-progress	chapters.json has facts-and-the-record under Direction and judgement, with the five ideas from the article placed in it (site v0.2.12); the editor's map decides
2	editor	Propose the hands-on part: its workflows (an agentic workflow from zero, images, infographics and storyboards, presentations, meeting briefs and follow-ups, publishing), each with the newsroom article it starts from, and a note that this part is dated 2026 and…	in-progress	chapters.json proposes the part hands-on-2026 with one chapter per workflow, each naming the newsroom article it starts from, marked dated 2026; whether it is in the book or a companion is Dinis's open question
3	editor	Prepare interview questions on this: a story of a rabbit hole that changed a decision of mine; how I prepare for a meeting today, step by step; where a generation that is told not to post anything should draw the line. Done when the script is in your `briefs/`…	open	no interview script on this in team/editor/briefs/
4	journalist	Write the hands-on workflows as articles first, one memo of mine each, starting with meeting briefs and follow-ups, which no newsroom article covers yet.	open	no hands-on workflow article yet; meeting briefs and follow-ups first

Everything is connected 1 of 5 done

#	Role	Task	State	Evidence
1	editor	Place the graphs chapter early, before or with Wardley maps, since a map is a graph with positions. Done when the chapter map orders the two and says why.	in-progress	chapters.json places everything-is-connected just before where-do-you-land in Before you start, with the reason in its note (site v0.2.15); the order is Dinis's question and the editor's map decides
2	editor	Choose the figures from the list above, and the worked example: one newsroom article's graph, shown and read. Done when the chapter map names them.	open	no figures or worked example named in chapters.json yet; the candidates are the table in the article
3	editor	Place the 2018 material: the outline Graphs, and the chapters Dot Language and AST as examples inside this one. Done when the chapter map says where.	in-progress	the chapter's answers_2018 names 5.concepts/graphs.md, dot-language.md and AST.md, and the idea the-2018-graph-chapters says they are examples inside it; the editor's map decides
4	editor	Put Your first graph in the hands-on part. Done when the part lists it.	done	chapters.json lists your-first-graph in the hands-on 2026 part (site v0.2.15)
5	editor	Prepare interview questions on this: where graphs first entered my thinking (the influences register asks the same); a graph I drew that changed a decision; how to explain "start anywhere" to someone who feels lost. Done when the script is in your `briefs/`.	open	no interview script on graphs in team/editor/briefs/

Lenses, roles and loops 1 of 4 done

#	Role	Task	State	Evidence
1	editor	Place this chapter right after what generative AI is, as the second half of the same explanation: lenses, roles, the loop, tools, the context window, compression, and why to work in focused threads. Done when the chapter map has it.	in-progress	chapters.json places lenses-roles-and-loops right after what-generative-ai-is in The frame (site v0.2.15); the editor's map decides
2	editor	Plan the lenses exercise for the hands-on part: one idea explained through five lenses (a teenager, a musician, a doctor, a football fan, another language), the reader's own choice of idea. Done when the part lists it.	done	chapters.json lists five-lenses in the hands-on 2026 part (site v0.2.15)
3	editor	Plan a tiny agent loop for the hands-on part: a page of code or a no-code version that shows the loop and one tool call, so the reader sees it is not magic. Done when the part lists it, with the newsroom article it builds on.	in-progress	chapters.json lists a-tiny-agent-loop in the hands-on 2026 part; the newsroom article it builds on is not named yet
4	editor	Prepare interview questions on this: the first time I saw a model ask for a tool; a time a long chat lost something important; how I name and split my agents. Done when the script is in your `briefs/`.	open	no interview script on this in team/editor/briefs/

The book in release mode 1 of 7 done

#	Role	Task	State	Evidence
1	editor	Assemble rc1 in the vault from the proposed chapter map and the register's ideas for this edition: every chapter written from its co-written article, and every chapter without one present as its title, its ideas and what is missing. Done when rc1 reads from th…	done	rc1 exists: v2/content/ (30 chapters, every one written from its ideas, the gaps as For Dinis notes collected at v2/book/for-dinis.html and in the back matter) and the working copy in the vault's book/rc1/ (site v0.2.19); the librarian assembled it at Dinis's request, the editor's coherence read is next
2	editor	Run the coherence read of rc1, with the synthetic readers: does it hold as a book, where does the storyline break, what is repeated? Done when the findings are in the vault, answered.	open	no coherence read of rc1 in the vault yet
3	editor	Clerk the board: keep the hearings and the precedents in the vault, one file each, and apply the precedents before calling a hearing. Done when the first round's hearings are recorded, each with its verdict.	open	no board/hearings/ or board/precedents/ in the vault yet
4	librarian	Make the batch for each round from the register: the ideas and sources not represented in the current release candidate, with the round's pile. Done when round 1's batch is a page on the graph.	in-progress	v2/book/for-dinis.html lists the ideas with no chapter and every gap rc1 names; the round-1 batch as a page on the graph (ideas and sources not represented in rc1) is not built yet
5	librarian	Record every verdict on the idea (state, destination, and the hearing that decided it), and count each round's changes by size. Done when the graph shows the rounds converging, or not.	open	no verdicts yet; the ideas' decided_by fields are ready to name a hearing
6	reviewer	Bring round 2: the 2018 chapters the review says to keep or rewrite that rc1 does not cover, each as a proposal with its evidence. Done when every such chapter has a hearing or a precedent.	open	no round-2 proposals yet
7	publisher	Say what a release candidate needs to become official: the checks, the formats, and who signs. Done when it is written in your `briefs/`.	open	team/publisher/briefs/ has the brief; no answer yet

Gen ZX Developers 1 of 4 done

#	Role	Task	State	Evidence
1	editor	Put this to the board as the first change set, from rc1 to rc2, so rc2 is written under the frame I choose: the audience, the title, the objective, the new part and the remapping above, each as its own proposal. Done when each has a hearing and a recommendatio…	done	Dinis adopted the proposal himself on 19 October 2026 and told the librarian to rewrite the book under it (decision 015); the change set did not need a hearing. The board hears what comes after rc2.
2	librarian	Map the proposal on the graph as a variant of the chapter map, so the two can be compared, and process the newsroom articles above into ideas. Done when the variant has a page, and each article above is cited by an idea or marked with why not.	in-progress	chapters.json is the rc2 map and chapters-rc1.json the rc1 map, compared on graph/rounds.html; the newsroom articles of the proposal's table are processed into ideas (batch rc2) in the same release
3	journalist	Write the gap articles, one memo each: the UK company, Lithuania, Portugal, the EU, the first customers, the community and the measure. Done when each is an article, processed into ideas.	open	team/journalist/issues/open/002 lists the six gap articles; none written yet; the chapters that wait on them stand in rc2 as their titles, ideas and what is missing
4	publisher	Say what a new title means for Leanpub, the print edition and its ISBN, Amazon and this site's address, if I choose it. Done when it is written in your `briefs/`.	open	no answer in team/publisher/briefs/ yet

The roles' own issues

The work issues each role keeps (the folder is the status). A role opens its issues from the briefs above; these are the ones open today.

Role	Issue	State
editor	Run the first interview with Dinis	open
editor	The title, the subtitle and the language	open
editor	The chapter map of the second edition	blocked
journalist	The gap articles for the startup edition	open
journalist	Brief the influences register with the 2018 findings	blocked
librarian	The 2018 files with neither an article nor an idea	open
librarian	Mine the content articles as the chapters are drafted	open
librarian	Process the four bring articles left	done
publisher	The Leanpub iteration plan	open
publisher	The 6x9 PDF and KDP	open
publisher	A launch in Lisbon at Web Summit	blocked
reviewer	Review the 2018 text, one record per chapter	open
reviewer	Check the map, row by row	open
reviewer	The three missing STEM figures	open
reviewer	Settle the licence of the 2018 text	blocked

States: admin/content/graph/tasks-state.json. The build refuses a state for a task the articles do not have.