Baseline guide

One screen that says what this site is: a composed Truvio Commerce Distribution swift-demo without sample data, kept as a reference implementation. It names the composition, the version pins, and the rule that branding never edits a layer. Every child page is one feature area.

<site-root> is the segment Dynamicweb serves for the area: the culture (/en-us/) on a single-area host, the area URL name (/swift-2/) when several areas share a host; resolve it with get_area_by_id + one storefront GET before trusting any path.

What the baseline guarantees

This site is a composition, not a hand-built demo. Its content came from
Truvio.Commerce.Distribution edition `swift-demo` (editions/swift-demo.json), minus the
`sample-data` layer.
Shipped by the composition:
- base 3.2.1 — framework only. 16 SQL sets under layers/base (replace tree) _sql: EcomCountries,
  EcomCountryText, EcomCurrencies (170 rows), EcomLanguages (20 rows),
  EcomMethodCountryRelation, EcomOrderFlow (4), EcomOrderStateRules, EcomOrderStates (14),
  EcomPayments (5), EcomShippings (17), EcomShopGroupRelation, EcomShopLanguageRelation (3),
  EcomShops (1: SHOP1 "B2B Commerce Store"), EcomVatCountryRelations, EcomVatGroups (2),
  AccessUser (3 group rows).
- surface-swift 1.5.1 — content area 3 "Swift 2", AreaUrlName `swift-2`, AreaCulture `en-US`,
  ~105 pages, its own 128 Swift v2.4.0 item-type XMLs, UrlPath, 32 design templates.
- six feature layers, each data-only except feature-pricing's compile-optional provider.
- theme-default 1.3.3 — disk overlay only, no database rows.
NOT present by design:
- No `sample-data` layer. No demo identities (IMCUser / IMCSalesrep), no FIXT* catalogue,
  no demo clock, no email-statistics backfill.
- No `surface-headless`. No `Headless_*` item types, no headless repository.
- No `surface-dap-portal`. Area 26 does not exist.
- No `Swift 2 Nederlands` area — surface-swift 1.2.0 removed it.
- No integration activities, endpoints or jobs. No layer ships any.
- No Data Models, no product categories beyond `reference_category`, no completeness rules,
  no workflows, no assortments, no dashboards.
Version pins are the reproducibility stamp: record the resolved Distribution commit SHA in
CUSTOMISATIONS.md (dw-demo-base/SKILL.md:77). Pin origin/main and assert INDEX.gateProven is
present; tags are provenance-only audit history, never a consumption pin.

Which skill covers it

dw-demo-base (dynamo: false) — the foundation skill. Read references/scaffold.md §5 for the
Distribution clone/checkout model and references/customer-context.md for the read-only
contract that governs branding input. Use FIRST; every sister skill is Use AFTER
(dw-demo-base/SKILL.md:24, :212-221).

Which MCP tools brand it

None. This page is a statement of fact about the composition and is edited only when the
composition changes. Read it with get_pages_by_parent_id + get_paragraphs_by_page_id.

Verify

MCP: get_areas returns exactly one area, Name "Swift 2"; get_pages_by_area_id returns the
Swift 2 tree. If a second area appears, a surface layer was activated that this composition
does not name.