Comms: the open-questions queue

Four Explorer roles have no definition

advocate, alchemist, ambassador, sherpa. Directories exist, ROLE.md does not. Town Planner's librarian is likewise missing.

Publish as gaps; do not write them for the website — 07__ §5.

The Explorer→Villager transition trigger is undocumented

Nothing states when a component moves from build to harden, or who decides. The Cartographer's Genesis/Custom/Product/Commodity classification is the obvious mechanism, but that link is this pack's inference, not the corpus's statement.

The highest-value thing the founder could write next.

No SKILL.md-to-role mapping exists

40 skill files and 39 role files, with no index of which roles hold which skills. Both this site and skills.sgit.ai need it — the natural shared artefact and the cleanest way to prove the capability/composition seam actually works.

The workflows are implicit

25 ## Core Workflows sections inside role files, plus 130 comms files showing workflows in action — but no standalone workflow documents. Whether to extract them into first-class pages, or keep them role-scoped, is an editorial decision — Q6.

Effectiveness is asserted, not measured

18 role files have a ## Measuring Effectiveness section, but no measurements appear anywhere in the corpus. This site cannot claim these roles work; it can only show they are defined, used and revised.

Only three learnings were recovered

The archaeology on the evolution page found three high-signal changes across seven months. There are 4,335 commits; a deeper pass over team/comms/ and .issues/ would likely surface more, and the changelog tree (changelog/03/ through changelog/08/) is unexamined.

The sg-playwright team was counted, not read

Six role files in a second product, used as evidence for the portable core. Their content has not been compared against the main team's — which is the actual test of whether the roster is reusable.

Deliberate PST, or named afterwards?

Is Explorer/Villager/Town Planner deliberately Wardley's Pioneers–Settlers–Town Planners, or did it emerge from practical context limits and get named afterwards? Both are good answers; the site should tell the true one.

Restore the failure-condition claim?

The failure-condition Central Claim ("…the Librarian has failed") versus the newer descriptive form: agreed that the older one is better and should be restored? If so, this site can publish rewrites of the seven descriptive claims as a build item.

What moves a component from Explorer to Villager, and who decides?

Same question as G2, asked directly.

Translator and Accountant — deliberate, or accident of timing?

translator exists only in the Villager team, and accountant only in Town Planner. Deliberate, or accident of when they were written?

Should comms get an acknowledgement mechanism?

A way to tell a read brief from an unread one — see what the protocol is currently missing.

Extract workflows, or keep them role-scoped?

See G4.

Are there roles you tried and removed?

A status: retired entry with the reason would be the most useful page on this site for anyone composing their own team — and nothing in the git history shows a deletion, so if it happened it happened before 11 February 2026.