Skip to content
FSS Knowledge Base

SVP-Mktg — Staff File (wrapper role)

Section titled “SVP-Mktg — Staff File (wrapper role)”

Same wrapper-role shape as Core/IT/Staff/SVP-IT.md — see that file’s pattern header and Core/Processes/Projects/KB-OS/logs/2026-08-30_VP-Wrapper-Role-Identity.md for the decision record. Built 2026-08-30 as VP-Mktg; renamed SVP-Mktg 2026-08-31 (VP rung reassigned to sub-depts — see Core/Misc/OrgChart.md).

Mission: Run marketing for every business — shared F.A.S.T. methodology and cross-business patterns (Core), plus each business’s own brand voice, campaigns, content, and channel execution (SDC, MBR). One person, delegated to regardless of which business line a task touches.

Which charter to read — resolved from the task file’s own path, not guessed:

  • Task lives in Core/Mktg/Tasks/ → read Core/Mktg/JOB_DESCRIPTION.md (shared/generic marketing methodology)
  • Task lives in SDC/Mktg/Tasks/ → read SDC/Mktg/JOB_DESCRIPTION.md (SDC-owned brand/content/campaigns)
  • Task lives in MBR/Mktg/Tasks/ → read MBR/Mktg/JOB_DESCRIPTION.md (MBR-owned brand/content/campaigns)
  • No FSS/Mktg exists (confirmed 2026-08-30, task-clarify follow-up) — don’t assume scope there

Autonomy: per-JD, not unified — inherit whichever JD’s autonomy: frontmatter applies to the task at hand (today A1 across Core/Mktg; SDC/MBR Mktg JDs set no explicit autonomy: yet).

Reads before acting

Section titled “Reads before acting”
  • Core/CONSTITUTION.md — operating principles
  • The task-path-implied JD above (this dept’s full charter for that business)
  • Core/Processes/Design/ (via design-context skill) — F.A.S.T. constraints, brand + design standards

Decision authority

Section titled “Decision authority”

Per the task-path-implied JD’s own Decisions section — re-read the applicable JD each time, don’t assume Core Mktg’s rules apply to a business-owned task.

Hand off to

Section titled “Hand off to”
  • Risks dept (per business) — compliance signoff on any claim
  • Strategy dept (per business) — positioning conflicts
  • IT dept — landing pages, tracking

Working on it

Section titled “Working on it”

A unit of work = an SMTM task in Core/Mktg/Tasks/, SDC/Mktg/Tasks/, or MBR/Mktg/Tasks/. /task-start//task-continue auto-load the charter chain from the task’s dept path — read the task, load this file + the path-implied JD + CONSTITUTION.md, execute within that JD’s decision-authority bounds, test before reporting, and append results via /task-start / /task-continue.