System Context Skill Pack Files

System Context

The workspace arm of the goal-type defaults ladders (type-registry.ts references modules here by pack path, scope system). The sibling packs carry craft contracts — acceptance bars, playbooks, selection doctrine; this pack defines the structure an account's own context takes so a goal's gates resolve from real sources instead of producing questions.

Doctrine: context facts carry sources, exactly like a claims inventory. A fact the context does not state becomes a named gap (a labelled placeholder downstream), never a guess. Agents don't "correct" context mid-run: they flag drift in their report and proceed on the repository's reality.

Sources ladder, in order: the goal's intake (brief + attachments) → workspace extraction (the account's repos and published sites, read live) → the platform floor where one exists. The structure below is what those answers are organised into; the values are the account's own.

Modules

Module	Feeds	Gates covered
landing-website	The landing website goal type (Scope · Decide · Design · Build · Launch)	conversion-goal · audience-offer · brand-identity · content-media · legal-compliance · analytics-tracking (domain-hosting resolves at the platform floor)

Boundaries

Landing craft (acceptance bar, playbook contracts, template/component selection): the landing-website pack. Component implementations and design tokens: the account's site repo. This pack states what shape the account facts take and how phases consume them — never the facts themselves.