subscriptions.sgit.ai / admin / comms
Comms: tasks & requests
The state of play on this site, kept here rather than in a chat message. 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 | Commission the solicitor review of the publishing rule and the register's first entry (B1). | The source's own flag: review costs less before than after. Nothing in /register/ gets a first row until this is done. | Blocking |
| N2 | Set the selection rule (B2): who gets asked, and on what basis. | A founder-led list is a founder's grievances until this is published. Recorded as not-yet-published on the page. | Blocking |
| N3 | Set the refusal interval (B3): the gap between the two asks that defines a refusal. | It defines a refusal; a per-case choice is indefensible once the register is live. | Blocking |
| N4 | Jurisdiction signalling (Q7): should the site present as UK-first with a general standard, or general-first with a clearly-badged UK law section? | Unanswered from the naming conversation. This release takes the general-first reading (the standard travels, the levers on /law/ are UK-badged) as a default, not a decision. | Open |
| N5 | Does the founder's own ten-company ask list pass the selection rule once N2 is answered? (Q8) | The first real test of the rule the register is about to publish. | Open, blocked on N2 |
| N6 | Is /exit/ global from day one, or UK-first alongside /law/? (Q9) | Exit-path measurements need no jurisdiction; the register's UK-flavoured levers might argue for scoping the first cohort. | Open |
| N7 | Take advice on the card-issuer lever's perimeter status (Q2) before it is added to /law/ or /service/. | It may sit inside the regulated claims-management perimeter. | Open |
Open work on this site
| # | Task | Status |
|---|---|---|
| T1 | Draft and version the question template (B4) — entries will quote it by version. | Open |
| T2 | Build the authority-capture workflow (B5) for representative access requests. | Open |
| T3 | Run the exit-path measurement against the first companies, once N6 is answered. | Open |
| T4 | Write the inconsistency test up as a repeatable, documented procedure before running it in anger. | Open |
| T5 | Write a method for archiving a sign-up flow retrospectively, so a disputed flow can be evidenced after the fact. | Open |
| T6 | Run check_siblings.py and publish the result here with its date, before the next release. | Open |
| T7 | First release: the pipeline, the pages, the agent surface, the brief pack published, the register launched empty and honestly. | Done |
Published unresolved
Not tasks. Questions the site carries in the open rather than answering for tidiness, per the pack's instruction:
- Does a published policy page count as an answer even when it means a company answers without ever knowing anything about the person who asked? This site's working answer is yes, recorded as a distinguishable row type — stated as a working position, not a settled one.
- What happens structurally at spring 2027? Planned, not absorbed: the standard's delta table is the transition artefact, and it is thin until there is register evidence to put in it.
- When does the register move to a non-profit? Easier before there is a register than after — the vault design makes it a re-point — but the decision itself is still a decision nobody has made.
- Is a founder-led first entry itself disqualifying, even once the selection rule is published? Named rather than assumed away.