nfrs.sgit.ai / admin / comms
Comms: tasks & requests
The state of play on this site, kept here rather than in a chat message — which is the same argument the memory thesis makes about the sentence that commissioned it. Numbered so a reply can refer to an item without quoting it.
Asks back to the project lead
| # | Ask | Why it needs you | Status |
|---|---|---|---|
| N1 | Is the vault model already the backups doctrine? Versioning plus escrow may be it, unnamed. | It decides whether /backups/ becomes a doctrine page or stays a stub. An hour of thinking, then either. | Open |
| N2 | Confirm the publish-IFD decision. The site publishes it, reasoning from the open-source position that the moat is a rate rather than a wall. | It is the estate's competitive methodology and the reasoning is inherited from a sibling site's argument rather than stated by you. Recorded as a decision on the page. | Confirm |
| N3 | Should the memory thesis also land on sgit.ai? The pack recommends it. | It explains all fourteen sites, so it arguably belongs on the hub more than here. The page as written would need trimming for that context. | Open |
| N4 | Confirm the source-manifest decision. The pack's ninth file is not published. | It indexes do-not-publish material by path. The reasoning is stated publicly; if you disagree it is one commit to add. | Confirm |
| N5 | House style: em dashes. The pack's style note asks for none; every sibling site and every pack document uses them throughout. | This site follows the siblings, because it has to read as one of the family. Say the word and it changes. | Confirm |
Open work on this site
| # | Task | Status |
|---|---|---|
| T1 | The scorecard generator — rebuild each cell from its sibling pack at release time rather than hand-assembling and dating. | Open |
| T2 | Verify every sibling link resolves. check_siblings.py now reports it — deliberately as a report and not as a gate, because a sibling's outage should not turn this repository's build red for a reason nobody here can fix. It found one genuine defect, fixed in v0.1.2: the network line said sentinel. where the site is sg-sentinel.. See the network state below. | Done |
| T3 | Count the day-indexes and debriefs, so the PM page's scale claim can drop its tilde. | Open |
| T4 | Confirm the IFD guides against current practice, so the page can stop describing itself as unverified. | Open |
| T5 | The site's own markdown twins beyond the front page — every page, per the house rule. | Open |
| T6 | First release: the pipeline, the pages, the agent surface, the brief pack published. | Done |
The network, as this hub sees it
Output of check_siblings.py, 25 August 2026: 12 of 14 hosts answering.
Two siblings are linked and not yet live:
coding.sgit.ai and skills.sgit.ai both return 404. The hostnames are correct — each repository carries the matching CNAME — so these are sites that exist and have not shipped, not links that are wrong. The links stay. Removing a correct link to an unshipped sibling would make this hub less useful rather than more accurate, and it would hide a fact about the network that a reader is better off knowing. Restated here, dated, rather than silently carried.Published unresolved
Not tasks. Questions the site carries in the open rather than answering for tidiness, per the pack's instruction:
- Is a hub site worth its drift risk? Stated on the topic map, with the fallback named: if the mitigations fail, the map alone is the site.
- Do the budget disciplines survive contact with real figures? Published as discipline, with this estate's application marked pending.
- Where does consistency live? Three homes, named rather than merged.