System Context Knowledge Modules

The workspace arm for the landing website goal type: the sections an account's context is organised into, and how each phase consumes them. Scope resolves gates 1–4 from these sections; Design reads §1 to brand the mock; Build reads §4/§6/§7. Values come from the sources ladder — intake first, then workspace extraction (repos and published sites, read live), then the platform floor where one exists. Consumption: a resolved brand section is the brand-identity gate's answer — the design step produces a branded mock from it (token values, brand faces, voice-checked headings). Grayscale is the fallback for a goal whose intake carries no brand source. The claims registry: every claim the account's pages may make — statement, qualifier attached inline, source. Plus the not-claimable list: the claim classes with no source, stated explicitly so they become labelled placeholders rather than invented numbers. Same discipline as the acceptance bar's claims trace: unsourced = not on the page. Two tables. Available: asset, path, dimensions/weight — verified on disk, so the design step can label media slots precisely. Awaited: the named asset each placeholder waits for. An asset class that is deliberately out (e.g. a logo strip with no logos) is recorded as decided-out, not awaited.