graphs.sgit.ai → admin → Comms
Comms: tasks and requests
A public working channel, in the network's house style. Asks (N) are things this site needs from someone else. Tasks (T) are things this site owes. Both are published unresolved, because a board that only shows finished work is a press release.
Asks
| # | Ask | Why it matters | State |
|---|---|---|---|
| N1 | Add the library/concepts/ cross-reference to .claude/CLAUDE.md in the source repository. |
This is the actual cure for the problem that produced this site. Phase 2 of an import memo specified on 11 June 2026 and never executed — which is why an agent reading forwards from that file never meets the philosophy. One edit. The diagnosis → | Open |
| N2 | A reciprocal /graphs/ bridge page on each sibling site, pointing here. |
What finally gives the philosophy a linkable home. A document nothing links to is, for a reader who follows links, a document that does not exist. The bridges → | Open |
| N3 | The founder's LinkedIn “graphs of graphs / meaning through connectivity” series. | Requested as prerequisite reading on 10 June 2026 and still absent from the corpus. It is the canonical statement of the thesis in his own voice, and its absence is why gap G1 exists. Until it arrives, the thesis on this site is assembled from thirty-five fragments. | Waiting since 10 Jun |
| N4 | The corpus glossary cited as the authority on edge-grammar discipline. | Cited by name in a July brief; no such file exists in the repository. This site has taken the other option and become it — but several inverse names are ours rather than the corpus's, and they need review. The edge set → | Partly answered here |
| N5 | Resolve licence and attribution on the three foundational concept documents. | Was the only hard blocker in the brief pack. Closed by the decision of 21 August 2026: CC BY 4.0 by default across the corpus and every *.sgit.ai site. The decision → |
Done · 21 Aug |
| N7 | Use the front page's framing to open the book. | Founder, 21 August 2026, reading the front door via sgit.ai/network/graphs.html: the way it frames the ideas, the examples it gives and how it explains what happens next should open the book too, even before the book defines what it means by a graph. Done at v0.3.4: the Introduction, projected from the front page, ahead of chapter 1 in all four editions. |
Done · 21 Aug |
| N6 | A legal read on the case study that names a real third-party product. | Sources are public and the tone is fair, but it is the one item an external party could reasonably object to. Not published until this comes back. Stated on the examples page → | Open |
Tasks
| # | Task | Why | State |
|---|---|---|---|
| T1 | Mirror the 2FA instance graph JSON and its ontology brief here, as a download. | The single highest-value thing this site could add. It is the only artefact that is both a complete narrative and a machine-readable file, it declares its own modelling principles inside the data, and it carries "license": "CC BY 4.0". The page describing it → |
Open |
| T2 | Ship the live node-types.json and link-types.json as a downloadable example schema. |
Cheapest credibility on the site: 12 node types, 10 verb/inverse pairs with domain and range constraints, and 71 live nodes / 141 edges behind it. It also ships the banned edge, which is the better half of the lesson. | Open |
| T3 | Build the personal risk question graph — six questions, browser storage only, no backend, no account, no LLM. | The best interactive demo available: answer six questions and watch your own risk graph build itself. Answers typed as fact / opinion / hypothesis / evidence. Nothing leaves the browser, and a visitor can verify that in the network panel. | Open |
| T4 | Render the air-gap Wardley map and the four unrendered permissions maps. | The air-gap map is the sharpest single map in the material and it has no image. Four more are one render command away. Why it works → | Open |
| T5 | Split /start/, /grammar/ and /depth/ into per-page URLs. |
The architecture document specifies eighteen separate pages; v0.1.0 ships them as five rich pages with anchors. Sections are addressable today, but a per-concept URL is what an agent citing one rule actually wants. The specified IA → | Queued |
| T6 | Make the rendered pages' prose fetchable in one request, not just the source documents. | Answered by the book: /book/single.html is all sixteen content pages in one HTML file, generated from the pages themselves. llms-full.txt still carries the source documents; the front page's prose is in index.md. Between the three, one-fetch coverage is complete. |
Done · v0.2.0 |
| T7 | /infographics/ — build the graph prompt library first. |
The infographics page reads “awaiting resources” across this estate. The unlock is a graph-specific prompt library, in the slide-NN-name/{_page.json, brief.md, infographic.png} shape — prompt beside output, so every image is regenerable and auditable. |
Queued |
| T8 | Write /depth/time/. |
Time as a first-class dimension is asserted across the corpus and never developed — gap G10. The vault commit DAG is a working answer to “how does a graph change over time” and should be the proof. | Queued |
| T10 | Build /book/ — the site as a book, in three reading modes. |
Founder request, 21 August 2026: a book-like reading sequence over the existing content. Built as a generated projection of the site's pages — chapter pages with a left table of contents, a single page, and a PDF — with a CI check that fails the build if a source page changes without the book regenerating. The v0.2.0 row has the details. | Done · v0.2.0 |
| T17 | The Introduction — the front page, projected into the book. | Closes ask N7 at v0.3.4. gen_book.py extracts the front page's hero and bands (minus the purely navigational ones), rewrites the site wording to book wording at the projection, and places the result before chapter 1 in the reader, single-page and both PDF editions. The gate hashes the front page's hero region the same way it hashes every chapter source: the front page is now a book source, and the two cannot drift. |
Done · v0.3.4 |
| T16 | Grow the chapter grammar: directives for the remaining components, and JS graph rendering. | Founder direction, 21 August 2026: extend the markdown grammar rather than fall back to HTML. Still embedded HTML in the markdown: the cards grid, the origins timeline, the edge-palette legend. And in-chapter graph visualisation: ```mermaid renders today; cytoscape, d3, viz.js / vis.js are the candidates for interactive graphs — which would also let the worked examples render their own node/edge data live, on the page that describes it. |
Queued |
| T15 | Move the chapter text to markdown — the editorial layer. | Done at v0.3.0: all sixteen chapters authored in content/*.md, rendered to the pages by gen_pages.py, gate-checked in both directions. Editors edit markdown and git tracks their changes cleanly; the migration was verified text-identical on every chapter before shipping. Each chapter's markdown is public at /content/<chapter>.md. |
Done · v0.3.0 |
| T14 | Ship both PDF editions from one source, versioned. | Done at v0.2.2: the screen edition (site design, US Letter, tablet-friendly) and the print interior (6″×9″) are emitted by one gen_book.py run from the same extracted chapters; each cover carries the site version, the manifest records both, and the gate refuses a release if either is missing or stale. Founder request, 21 August 2026. |
Done · v0.2.2 |
| T13 | Kindle edition — a reflowable EPUB from the same chapters. | Deliberately deferred, not forgotten: KDP does not want a PDF for ebooks — a fixed-layout conversion reads badly on every device. The right artefact is a reflowable EPUB, and the pipeline can generate one from the same extracted chapters with the same no-drift hash check. Founder decision, 21 August 2026: "let's not do kindle for now". | Queued |
| T12 | The print cover. | Done at v0.3.1, as code: gen_cover.py generates the front cover as SVG (web-reusable) and the full KDP wrap as a vector PDF — back, spine and front with bleed, the spine computed from the interior's page count and gate-checked against it, a 2″×1.2″ barcode zone at KDP's position. The cover graph is a true subgraph in the book's own edge vocabulary. Remaining at upload time only: confirm paper stock (spine assumes b/w on white, 0.002252″/page). |
Done · v0.3.1 |
| T11 | Retypeset the book PDF as a print interior in the standard technical-book format. | Done at v0.2.1: 6″×9″ trim, mirrored gutter margins, folios, running heads, recto chapter openings, a typesetter-computed contents — KDP-ready, no bleed, fonts embedded, 117 pages. The format review that produced these numbers is on the book's about page. | Done · v0.2.1 |
| T9 | Get indexed. | The measured finding behind the agent surface: an agent could fetch the parent site's index and then could not follow its links, because fetch tools refuse URLs a search has not already returned. Static HTML on GitHub Pages fixes the crawlability half; being indexed is the other half. | In progress |
Questions published unresolved
- Do the proposed inverse edge names belong in the set at all? Nine of the fifteen inverses on the edge set are this site's, not the corpus's. Publishing them makes them citable, which makes a guess durable. The alternative — publishing only the six that are sourced — leaves the vocabulary unusable. We chose usable-and-labelled; it may be the wrong call.
- Should
/start/mention that its examples come from another project? The five Reviews and the port example were written for Issues-FS, about issue tracking. The provenance is on /origins/ and in the source documents but not on the page itself, where it would cost a newcomer their first thirty seconds. - How much of the honesty framing survives contact with a first-time reader? Six pages carry a “written fresh” or “designed, not shipped” box. That is either the site's best feature or a wall of hedging, and we cannot tell from the inside.