System Context Skill Pack Files

PM — Consuming the Context

At Scope and at wireframe requirements, the context is the workspace arm: read it before asking anything. Gates resolve through the sources ladder (intake → workspace extraction → platform floor); a question is legitimate only when the brief overrides a default or names something the context does not carry — and then it is a named gap with an owner, not an open question. Requirements cite the context the way they cite the brief: claim ids, asset paths, the offer table, with section references so drift is detectable.

If the repo or live site contradicts the context, flag the drift in the report and proceed on the repository's reality; updating the context is operator work.