pki.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 discipline this site argues for. Updated on every release. Current release: v0.1.2, 19 August 2026. Full history: versions.
Needed from the project lead
| # | Request | Why it blocks | Status |
|---|---|---|---|
| N1 | GitHub Pages: the custom domain. The site is live at sgit-ai.github.io/SGit-AI__Website__PKI — the Pages source, the github-pages environment and deploys from dev all work, verified end to end on the v0.1.1 release. Still needed: Settings → Pages → custom domain pki.sgit.ai, plus the DNS CNAME record pointing at sgit-ai.github.io — pki.sgit.ai does not resolve yet | Until then there is no pki.sgit.ai URL, and every canonical on the site names a host that does not answer | waiting on human |
| N2 | The corpus documents for the collection. Build-order step 1 needs the February–March PKI material identified: the architecture debrief, the messaging implementation, the model-integration research, the document identity brief, the operating modes, the provenance treatment and the brand strategy. 729 files mention the subject; the site needs the handful worth promoting | The collection cannot be curated by question until the documents are named | waiting on human |
| N3 | The attestation decision. Does the registry accept third-party attestations? It is the site's central open question and it is a call for the project lead, not the site agent — a documented failure on one side, no social trust at all on the other | The private-registry build (step 4) can start without it; mandates (step 5) cannot be finished without it | open — published unresolved, deliberately |
| N4 | Presentation material to recycle. The scoping brief notes 31 files referencing presentation material the project lead wanted reused — worth an infographics section if the posts are identified, as on nhi.sgit.ai | No infographics section until the material is identified | open |
Task board
| # | Task | Owner | Status |
|---|---|---|---|
| T1 | CI pipeline: validate → auto-tag → deploy to Pages, adapted from the NHI site; validation extended to pull requests; canonical-host check added | site agent | done v0.1.0 |
| T2 | Theme carried over from sgit.ai / nhi.sgit.ai, with this site's additions (rules ladder, timeline, claim block, safe/fatal split columns) | site agent | done v0.1.0 |
| T3 | Shared page generator (single template for nav/footer/head) — currently hand-duplicated per page, as on the other two sites | site agent | queued |
| T4 | Refactor the PKI section across from nhi.sgit.ai and promote it to a site: the failure, the rules, mandate (new page), build order (new page), documents, disclosure | site agent | done v0.1.1 |
| T9 | Release-pipeline fix: the tag job anchors on the newest release commit reachable from HEAD instead of on HEAD itself, so a pull request landing as a merge commit no longer stops the release. Found by the pipeline's own first run on dev | site agent | done v0.1.2 |
| T5 | Markdown twins for every page + llms-full.txt (the sgit.ai convention) — only the front page has one | site agent | queued |
| T6 | The collection (build-order step 1): curate the 729-file corpus by question, promoting the Feb–Mar architecture material | site agent | blocked on N2 |
| T7 | Redirect the nhi.sgit.ai PKI section here once this site is live on its domain — that section was always staging, and the NHI site queues the spin-out as its T19 | site agent | queued — after N1(c) |
| T8 | The private registry (build-order step 4) — the first thing built rather than published | project lead + agent | queued — the next build |
How to use this channel
- Human → agent: reply in the working session, or edit this page / open an issue in the repo. Anything added under "Needed from the project lead" with an answer gets actioned next session.
- Agent → human: every release updates this page and versions; requests appear in the N-table above, most-blocking first.
- Decisions log: the site ships the pipeline before the content, so every release goes through a gate that already works; the PKI section was refactored across from nhi.sgit.ai rather than rewritten, so the two sites stay diffable; source briefs are captured verbatim under
briefs/with a curated page alongside, so the raw document and the presentation coexist; and the open questions are published unresolved rather than settled quietly.