sg-sentinel.sgit.ai / admin / comms
Comms: tasks, requests, decisions
The working channel between the site agent and the project lead — what is open, what is needed from whom, and the decisions already taken. Updated with every release.
Needs from the project lead
| # | Status | Item |
|---|---|---|
| N1 | needed | Go live. Merge the site branch, allow dev in the repo's github-pages environment (Settings → Environments), and confirm Pages serves from Actions. A one-off push to main works as a deploy test in the meantime — same fallback nhi.sgit.ai used. |
| N2 | needed | DNS. Point sg-sentinel.sgit.ai (CNAME) at sgit-ai.github.io; the repo's CNAME file is already in place. Until then the github.io URL serves the site. |
| N3 | open | Confirm the code-snapshot licence. The site states "code under the repository licence" (Apache-2.0, per LICENSE); confirm that is the intended licence for the code/sentinel/ snapshot. |
Site tasks
| # | Status | Task |
|---|---|---|
| T1 | done | v0.1.0: the six narrative pages, the 23-document reader section, the code snapshot with reading guide, the validate gate, the CI pipeline, versioning, llms.txt, sitemap. |
| T2 | open | Update the site if/when somebody runs the live AWS leg. If a builder picks the design up and executes the parity matrix's AWS leg and the live smoke test against a real CloudFront distribution, the status language on the front page, try-it and roadmap changes from "code-complete, never run live" to measured results. Blocked on somebody building it — see the not-built note. |
| T3 | open | Add the measured cost comparison (Sentinel live path vs Firehose + WAF baseline) when it exists — the founding argument's loop-closer. No numbers before then. |
| T4 | open | Refresh the code snapshot and testing manual when the sentinel package moves past the packet's 23 May state, keeping the "captured at" provenance line accurate. |
Decisions taken while building
- The not-built note is load-bearing (v0.1.1, 20 Aug 2026, at the project lead's direction). SG/Sentinel has not been built: it is a set of research documents and ideas from May 2026, published as "this is how I would build it", in the hope that somebody builds it — the project lead would really like to use this next generation of WAF security layer in his projects, and has no plans to build it at the moment unless somebody wants to fund it. A site-wide notice bar, the front-page note (#not-built), and the "prototype exercise" framing on every status claim carry this; the nav pill changed from "mvp" to "not built".
- Light theme, not dark. The website brief suggested a near-dark theme; the commissioning instruction was to match the sgit.ai / nhi.sgit.ai design language, which is the cream-light theme with dark terminal blocks for code. The instruction wins; the terminal blocks keep the code-adjacent material dark and high-contrast.
- All 23 documents captured, not six pages of synthesis alone. The narrative pages synthesise (per the brief's "don't paste 3,000 words"); the documents section carries the full corpus verbatim with reader pages, following the nhi.sgit.ai raw-plus-curated pattern.
- The code snapshot ships in the repo. 556 KB buys verifiable provenance: every excerpt on the site can be diffed against
code/sentinel/. - Status language is fixed at the packet's precision. "149 unit tests passing", "code-complete and unit-tested via in-memory doubles, not yet run against a real CloudFront distribution" — verbatim discipline, enforced by review rather than tooling.
- The TUI/chat/traffic surfaces are presented as built, on the authority of the testing manual (23 May), which post-dates the dev brief that had deferred the TUI.