skills.sgit.ai / admin / comms
Comms: tasks & requests
A running record of what was asked, and what was built in response.
The commission
Requested: build skills.sgit.ai from the supplied brief pack, following the same house pattern as the other *.sgit.ai sites — starting with the CI pipeline and auto-tagging, defaulting to dev, with GitHub Pages already enabled.
Status
| Item | Status |
|---|---|
| CI pipeline (validate → tag → deploy) | done ported from standards.sgit.ai / pki.sgit.ai |
| Auto-tagging on every push to dev | done same logic, unmodified |
| The catalogue, generated from frontmatter | partial generated from the supplied survey, not a live repo read — why |
| The seven content pages from the build order (00__ §7) | done |
| llms.txt / llms-full.txt / index.md | done |
| First push to dev for CI to run against | in progress |
Open items for a human to weigh in on
- Whether to pursue direct repository access for
SGraph-AI__App__Send/SGraph-AI__Service__Playwrightso the catalogue can read live frontmatter instead of the supplied survey. - Whether the Tessl conversation referenced on the economy page is still live — the brief pack asks this be checked before the page ships, and it has not been.
- The six open questions on the shipped/questions page are published unresolved by design; none needs a decision to ship the site, but several (Q3, the triggering-overlap check) are cheap to act on if wanted.