nhi.sgit.ai / admin / comms

Comms: tasks, requests & status

The working channel between the project lead and the site agent, kept in public on the site itself — which is an instance of the workflows this site describes. Updated on every release. Current release: v0.1.12, 19 August 2026. Full history: versions.

Needed from the project lead

#RequestWhy it blocksStatus
N1LinkedIn post links for the infographics — the specific request list is on the infographics page: two-populations, AOMM ladder, hope-driven / the closure, blast radius, pull-the-plug, serialised PR, trifecta correction, plus anything else under #NHIThe infographics page is a placeholder until the posts are identifiedwaiting on human
N2Rights decision: link or mirror the infographic images? Linking is safe; mirroring needs an explicit callDetermines whether images are downloaded into this repowaiting on human
N3GitHub Pages settings. The site is live at sgit-ai.github.io/SGit-AI__Website__NHI via a one-off deploy from main (v0.1.2, requested by the project lead). Still needed: (a) the auto-created github-pages environment only allows main, so deploys from dev are rejected — Settings → Environments → github-pages → Deployment branches → add dev; (b) Settings → Pages → custom domain nhi.sgit.ai plus the DNS CNAME recordUntil (a), releases on dev tag but do not publish — the live site only updates when something is pushed to main. Until (b), no nhi.sgit.ai URLwaiting on human
N4Thesis refutation pass — the brief's open question: somebody should try to refute the two-populations thesis before it hardens; a wrong thesis on a front page is expensiveFront-page claimopen
N5Confirm the three first options — currently SPIFFE / commercial broker / do-nothing, per the brief's "different in kind" ruleRe-run effort goes where the choice landsopen — proceeding with current three unless redirected
N6The remaining 16 Aug briefs are not yet in the public corpus repo (comparison-pages method, relay pattern, and the brief that scoped this site) — push them, confirm where they should be linked from, or paste them here for capture as was done with the shared-drives brief (readable on its document page)Collection and method pages cite them without a public linkwaiting on human

Task board

#TaskOwnerStatus
T1Thesis page — two populations, evidence, defensibilitysite agentdone v0.1.0
T2Method page — scenario + columns, published before findingssite agentdone v0.1.0
T3Three options, preliminary assessments from sourcessite agentdone v0.1.0
T4Hope section — concepts and workflowssite agentdone v0.1.0
T5Collection organised by question; AOMM promoted to a pagesite agentdone v0.1.0
T6CI pipeline: validate → auto-tag → deploy to Pages (per SGit-AI__Website)site agentdone v0.1.0
T7Hands-on re-run of the three option assessments against the scenariosite agentqueued
T8Markdown twins for every page (the sgit.ai convention) + llms-full.txtsite agentqueued
T9Page generator (single shared template, as sgit.ai's build_pages.py) — nav/footer currently hand-duplicatedsite agentqueued
T10Infographics published with links + underlying docssite agentblocked on N1/N2
T11Curate more of the corpus in — the 8 GitHub-referenced briefs are now captured with document pages (hope-driven, catastrophic-risk, pull-the-plug ×2, AOMM, sandbox-escape, ambient-authority, serialised-PR); still queued: risk-register, mandate-graph, trifecta scenario, remaining 16 Aug briefssite agentin progress — 8 captured v0.1.8
T12sgit vault co-existence — git + sgit in one repo, per the site brief's "same pattern as the other site"site agentqueued
T13Re-run queue owner + cadence for dated assessmentsproject lead + agentopen question from the brief
T14Capture the shared-drives research brief (v0.33.59) and propagate: research page, document page, thesis/hope/method/options/collection updatedsite agentdone v0.1.4
T15Test from the brief's open questions: does one authorising account per agent give workable per-agent identity (segregation applied to identity)? What does the drive audit trail actually record per session?site agentqueued — hands-on test, results would fill or confirm two empty rows
T16Re-verification entry for the shared-drives tables (prices and capabilities move monthly; scored 16 Aug 2026)site agentqueued — first re-run due mid-September 2026
T17Capture the pki.sgit.ai brief (v0.33.59) and build the PKI section: hub, failure page, four rules, document page — brief build-order steps 2 and 3 done in advance of the sitesite agentdone v0.1.5
T18PKI collection (build-order step 1): curate the 729-file corpus by question, promoting the Feb–Mar architecture material — needs the corpus documents identified (the February architecture debrief, messaging implementation, document identity, operating modes, brand strategy)site agentqueued
T19Spin out pki.sgit.ai as its own repo + site (same pipeline as this one) when the section outgrows this host — then this section redirectsproject lead + agentqueued — decision on timing is the project lead's
T20Industry section: market map grouped by layer, 14 provider profiles (generated by admin/build/gen_industry.py), SPIFFE concept page with diagrams; SPIFFE/vendor mentions linked from thesis and optionssite agentdone v0.1.6
T21Documents section: index + one reader page per captured brief (summary, key concepts, key ideas, in-page markdown, infographic slot; generated by admin/build/gen_documents.py); the NHI site brief captured into briefs/site agentdone v0.1.6
T22Industry profiles: monthly re-verification (pricing/features move); expand with vendors the map names but doesn't profile yet, and deepen pricing detail from vendors' published pagessite agentqueued — first re-run due mid-September 2026
T23Packs section: hub + the static-publishing pack (8 documents from the SGit-AI__CLI architect-review branch), sources verbatim under packs/*/src/, reader pages via gen_packs.py, mermaid rendering added to the markdown reader. Second pack captured v0.1.10: hub.sgit.ai — the fractal forge (9 documents, 18 Aug design pack). v0.1.11: static-publishing refreshed to its 18–19 Aug revision, and every pack page states the source commit it was captured at, with the raws byte-identical to that commit. v0.1.12: refreshed to 2cedd9a — the executed tabletop exercise captured with a reader explainer, the no-target publish rewrite, 12 documents. Eventually the section spins out to its own site; the treatment moves with it. Uncaptured from the same branch: the 08/19 review notes (v0__response__source-and-output-separation.md, v1__review__static-publishing-full-pass.md)site agentdone v0.1.12 — 2 packs, commit-pinned

How to use this channel