Use and adapt Marketing-OS

Use the documented interfaces and source layout for Marketing-OS. The sections below retain the README’s examples and configuration details.

How It Works

foundation → research and audiences → positioning and voice → strategy → craft and launches → measurement → compounding

Every skill loads foundation/marketing-os as its root. Research and audience evidence inform positioning. Strategy turns that position into decisions and plans. Craft and launch skills produce the work. Measurement connects Marketing-sourced demand to subscriber quality and business economics. Completed work improves the system only when the learning transfers beyond the project that produced it.

See ARCHITECTURE.md for the full dependency graph.

Taxonomy

The repository has seven skill families:

1. foundation/ — Every's marketing doctrine, canon, operating frameworks, collaboration rules, and native-document editing protocol
2. brand-voice/ — Voice systems for Every and its products
3. positioning/ — Durable, ruled master-brand and product positioning
4. strategy/ — Compound Brand, messaging architecture, measurable program briefs, and executive one-pagers
5. craft/ — Verbal identity, art direction, copywriting, editing, naming, PR, social, email, web, and long-form execution
6. launches/ — The canonical launch process, launch calendar, brief, GTM strategy, claims clearance, wireframing, email flows, and three launch tiers
7. marketing-science/ — Research, audience archetypes, brand equity, messaging evidence, attribution, Fame Score, cohort economics, and results compounding

Optional historical cases live in docs/cases/. Skills never load them by default.

What Belongs in the OS

Marketing OS stores reusable methods: how to execute a launch, GTM plan, campaign, email series, channel strategy, measurement plan, or post-project review.

It does not store active roadmaps, launch briefs, campaign concepts, current rosters, temporary claims, prices, budgets, embargoes, or project calendars. Durable positioning and voice may live in their product modules only after they have been ruled as canon.

Project work can change the OS when Douglas explicitly makes the learning a standard, the pattern succeeds across multiple relevant projects, or unusually strong evidence supports a bounded rule. Otherwise the learning stays with the project or in an optional case.

Troubleshoot a local change

1. Reproduce the smallest example from the quick-start guide.
2. Compare required configuration and dependency versions with the README.
3. Check the linked issue tracker for the same error. Include the command, runtime version, and relevant error when reporting a problem; omit credentials.

Source and help

• GitHub repository
• Original README
• Issues and existing reports

This catalog entry is a fork. The README may describe upstream packages, domains, or release procedures; those destinations do not establish a separate release of this fork.