Structure

The hub launcher for the detail layer. Every node is a chip, grouped into Global elements and Pages; each chip carries its number, name, and type, and opens that node's architecture page. This long list lives only here, never in the sidebar. For the hierarchy and cluster transitions, see the Site map.

Global elements

Canonical components defined once and referenced everywhere (cluster 0).

Pages

Every page and state node, ordered by cluster.

Block bank

Block bank by page type

Where the composition of a page comes from. Thirty nodes are eight to ten page types, so the pass is one per type, not one per node. Two sources answer two different questions and neither is enough alone: competitors give the domain truth (what a company in our category actually puts on this page), Refero gives the craft truth (how a page of this type is built in best-in-class products outside it). A block that traces to no job, barrier or SEO requirement is not taken. Full bank with tracing per block: ia/docs/blocks.md.

T1 Marketing landing0.0, 1.5The privacy mechanism sits above the fold. Nobody in the category puts the anonymity rule on the landing page.

T2 Pricing1.0A published per-seat number, and one line saying the privacy rule does not change with the plan.

T3 Trust and content1.1, 1.6, 1.2A two-column table of what the owner sees and never sees. The category states what is protected; we state what is visible.

T4 Auth form2.0 to 2.4The privacy sentence sits where the decision is made, not one click away.

T5 Guided wizard step3.0 to 3.3A pre-selected default with its rationale, and the reason this step exists under the question.

T6 Read surface4.0, 4.1, 4.2, 9.0, 9.2The reading is the largest element and the number is second. Every reference dashboard does the reverse.

T7 List and detail5.0 to 5.2, 6.0, 6.1Participation as a count, with no per-person answer column, ever.

T8 Settings section8.0 to 8.4, 7.0 to 7.3The privacy centre repeats the mechanism verbatim. A paraphrase would be a second edition of the promise.

T9 Linear task flow10.0 to 10.6The pre-question disclosure, its own screen, every cycle. The block the category does not have.

T10 System state11.0 to 11.4One plain sentence and the one way back that is useful from here. No apology theatre.

The honest gap, named rather than papered over. Refero holds no screen of the type "what your employer can and cannot see" as a product surface, and no pre-question privacy disclosure: the closest craft reference is a marketing security page. The competitor half is worse, because the one competitor with a genuinely specific anonymity model explains it in a help-centre article, outside the product. For types T3 and T9 the craft half is therefore thin, and the composition is carried by our own research instead. This is the one place in the bank where "where we are better" is not a comparison but a hole in the category.