Nine articles mapping your Obsidian canvas as a complete marketing operating system — from Knowledge Base to live campaigns across every platform.
Your Obsidian canvas is a complete marketing operating system — from company knowledge to live campaigns across 30+ platforms. Every layer has a name, a function, and a precise position in the hierarchy.
Every marketing operating system needs a root — a node that everything else reads from but nothing writes to casually. In the IO Marketing OS, that root is the amber Knowledge Base: eight documents that constitute the organization's constitutional layer.
In computer science, a knowledge base is a centralized repository of information that a system draws on to make decisions. It is not a to-do list, not a task board, not a project tracker. It is the stable, slowly-updated store of foundational truth. The IO Marketing OS opens with exactly this: an amber-bordered card containing eight sub-documents, each encoding a different dimension of organizational identity.
The amber color in the IO system signals supervisor-level importance. Every piece of content produced by this system, every campaign launched, every brief written, inherits its constraints from the Knowledge Base. The ICP determines who you're writing for. The Business Strategy determines which channels deserve budget. The Customer Lifecycle determines what content stage is prioritized this quarter.
"The Knowledge Base is not updated weekly. It is updated when the business changes. If you find yourself editing it every month, you are writing tactics into a strategic layer."
The eight items span identity (Company, Branding), offering (Services, Products), market (ICP, Customer Lifecycle), and direction (Business Strategy, Goals & KPIs). This is a complete organizational theory of itself. Any content created without consulting at least one of these eight documents is content created in a vacuum.
| Property | Value |
|---|---|
| Node type | Root / Supervisor — Read-mostly |
| Color | Amber — constitutional authority |
| Sub-documents | 8: Company, Branding, Services, ICP, Business Strategy, Products, Goals/KPIs, Customer Lifecycle |
| Update cadence | Quarterly or on strategic shift |
| Feeds into | All downstream nodes |
Below the Knowledge Base, the canvas splits into two green nodes — Deep Research and Market Intelligence. These are the system's intelligence-gathering subsystems that run continuously before any strategy is formed.
"Research is not a phase. In the IO Marketing OS it is a permanent, parallel process. The Research Layer never closes — it updates continuously as markets, algorithms, and competitors evolve."
| Property | Value |
|---|---|
| Node type | Intelligence / Environmental Scanning |
| Color | Green — living, continuous, organic |
| Deep Research domains | 13 |
| Market Intelligence modules | Market, Audiences, Targeting |
| Reads from | Knowledge Base (ICP, Business Strategy) |
| Feeds into | Strategies, Context Briefs |
The red Strategies node is where research findings become directional choices. Five strategy tracks run in parallel — Organic, Search, Paid, Sales, and Growth — each governing a different mode of market engagement with its own time horizon and cost model.
The Search track contains eight sub-strategies — more than any other. This reflects the current reality of information retrieval. GEO (Generative Engine Optimization) governs how your content surfaces inside AI-generated answers on platforms like Perplexity and ChatGPT Search. AEO (Answer Engine Optimization) governs featured snippets and direct answer boxes. LLM Search covers how language models retrieve and cite you without a traditional search query. AI Powered Browsers represents the browser-native AI frontier. The IO system was built knowing that search visibility is no longer a single-channel problem.
"Strategy is the bridge between research and execution. Without this bridge, research is just expensive reading and execution is just expensive guessing."
| Track | Time Horizon | Cost Model | Primary Metric |
|---|---|---|---|
| Organic | 6–18 months | Labor-intensive | Reach, followers |
| Search | 3–12 months | Mixed | Rankings, CTR |
| Paid | Immediate | Linear spend | ROAS, CPL, CPA |
| Sales | 1–6 months | High-touch | Pipeline, close rate |
| Growth | Experimental | Variable | Viral coefficient |
Between strategy and channel deployment sits a translation layer most marketing systems skip. The IO system calls it Context Briefs — a pink node with four sub-modules that converts strategic direction into actionable, channel-ready intelligence packets.
Each brief produced by this node is a unit of work issued to a downstream channel. It specifies the target audience segment (from ICP), the search terms to address (from User Search), the narrative angle (from Creative), the specific offer being made (from Offers & CTAs), and the performance context (from Actionable Insights). A channel receiving a brief has everything it needs to produce and deploy content without climbing back up the system to find context.
The Actionable Insights module is the only node in the system that runs in both directions. It receives campaign performance data from Execution (Article VII) and converts it back into forward-looking briefs. This is the mechanism that keeps the system learning: every campaign result becomes a brief update, every brief update changes what gets produced, every production change generates new results. The loop closes here.
"The Context Brief is the moment the system's intelligence becomes someone's instructions. It is the last step of thinking before the first step of making."
| Module | Inputs | Outputs |
|---|---|---|
| Actionable Insights | Campaign data | Performance briefs, learnings |
| User Search | Keyword research, intent data | Keyword briefs, prompt libraries |
| Creative | Brand strategy, UVP/USP | Topic trees, messaging guides |
| Offers & CTAs | Promotions, product offerings | Offer sheets, CTA libraries |
Below Context Briefs, the canvas fans out into six parallel channel columns covering every surface where an audience can be reached. Marketplaces, Paid, Organic, Website, AI Search, and AI-Chats — 30+ platforms mapped and organized.
"The Channel Architecture is the system's awareness of where it can operate. Most marketing systems build channels ad hoc. The IO OS maps them all at once, assigns them to types, and deploys in parallel."
| Channel Type | Platforms | Primary Mode |
|---|---|---|
| Marketplaces | Amazon, Etsy, Whop, Notion, Gumroad (5) | Product distribution |
| Paid Channels | 11 ad platforms | Paid acquisition — full campaign systems in Article IX |
| Organic Channels | 11 content platforms | Compounding presence — playbooks in Article VIII |
| Website | 5 sub-systems | Owned conversion hub |
| AI Search | 5 AI search surfaces | Generative visibility (GEO/AEO) |
| AI-Chats | 8 chat models | Conversational presence & citation |
Twenty-seven formats. One purple node. The Content Types layer is the IO system's complete taxonomy of output — every form in which strategy can be manifested as something a channel can actually deploy.
The 27 formats organize into three tiers. Foundation content (Knowledge Base, Documents, Strategy, Reports, Briefs, White Papers, E-Books) is slow to produce, long-lived, and serves as infrastructure. Distribution content (Articles, Social, Video, Podcasts, Ads, Paid Media, Story Cards, Scripts, Courses, Tweets, Memes, GIFs, Images) is the primary output that channels consume. Automation content (Emails & Newsletters, ManyChat Automations, Prompts/AI Communications) runs on triggers and builds the system's ability to communicate at scale without human intervention on every send.
Two of the 27 formats represent the frontier of modern content operations. ManyChat Automations are conversational flows inside messaging apps — programmed sequences that qualify, nurture, and convert leads through chat interfaces. Prompts/AI Communications are the structured instructions that power AI-assisted content generation — the system's internal language for directing AI tools toward brand-consistent output. Their inclusion signals that the IO Marketing OS was designed for the AI era, not retrofitted for it.
"Most content teams operate with an implicit format library — they make 'content' and hope the format matches the channel. The IO system makes the format explicit before a word is written."
| Tier | Formats | Lifespan |
|---|---|---|
| Foundation | Knowledge Base, Documents, Strategy, Reports, Briefs, White Papers, E-Books/Lead Magnets | 12–36 months |
| Distribution | Articles, Social Media, Videos, Podcasts, Images, Ads, Paid Media, Story Cards, Scripts, Courses, Tweets, Memes, GIFs | 1–90 days |
| Automation | Emails & Newsletters, ManyChat Automations, Prompts/AI Communications | Evergreen until updated |
The red Execution node is the operational engine that takes content types and deploys them across channels on a cadence, at scale, with measurement built in. Eight modules. Zero ambiguity about who does what, when.
Daily platform-specific rituals — commenting on trending posts, engaging within the algorithm's window, responding to mentions — compound over time in ways that scheduled posts alone never can. The IO system encodes these as a formal module, not an afterthought, because platforms reward consistency of presence, not just quality of output.
The Measurement module is not just the last step of Execution — it is the mechanism that feeds back into the Context Briefs layer. Campaign performance flows into Actionable Insights, which updates briefs, which changes what gets produced. Without Measurement, the system is open-loop: it produces but never learns.
"Execution is not the least glamorous layer. It is the layer that determines whether every other layer was worth building."
| Module | Cadence | Owner |
|---|---|---|
| Planning | Monthly / Quarterly | Strategy lead |
| Scheduling | Weekly | Content manager |
| Posting | Daily | Content manager / automation |
| Engaging | Daily (within 1h of post) | Community manager |
| Every Day Actions | Daily ritual | Platform specialist |
| Social Scaling | Weekly | Growth operator |
| Measurement | Weekly + Monthly | Analytics lead |
| Task Execution | Daily | All team members |
Below the Execution node, the canvas branches into per-platform organic content systems. Each platform gets a dedicated card — a production workspace with its own strategy, formats, cadence, and template library.
The organic platform playbooks are the deepest level of the IO system's organic architecture. They are reached via the Organic Channels hub — a routing node dispatching to each platform's dedicated workspace. Each card operates as an independent production environment with the same organizational logic but different platform constraints.
The canvas shows several platform cards (Pinterest, X/Twitter) as mostly blank — large, lightly-tinted areas with titles but no content yet. This is the system's template layer made visible. Space has been allocated, structure established, and the card is waiting to be activated. This is how a scalable system grows: platforms slot into pre-built homes rather than requiring new infrastructure for each one.
The Organic Channels node is a neutral routing node — it receives from Execution and dispatches to platform playbooks. It also receives gray lines from the Execution layer, indicating that the Organic Channels hub collects parallel inputs from Website, Paid Channel Campaigns, and Website sub-systems before dispatching to the individual platform cards. The hub is the moment the system's content becomes platform-specific.
"An organic platform playbook answers: what does success look like on this specific platform, for this specific brand? The system asks that question once, documents the answer, and executes against it consistently."
| Platform | Card Color | Primary Format |
|---|---|---|
| YouTube | Red | Long video, Shorts, Community |
| Blue | Feed, Reels, Groups, Live | |
| Blue | Posts, Articles, Newsletter | |
| Pink (template) | Pins, Boards, Idea Pins | |
| X (Twitter) | Gray (template) | Threads, Daily posts, Spaces |
| Others | Inherited structure | Platform-native formats |
Nine platform-specific paid campaign systems — each mapped across four dimensions: Campaign Architecture, Customer Journey, Campaign Objectives, and Ad Formats. The IO system imposes one universal structure across all nine platforms, making cross-platform campaign management coherent for the first time.
Every paid campaign in the IO system shares the same four-column structure regardless of platform. Campaign Architecture (Campaigns → Ad Sets → Ads) defines account organization. Customer Journey (Stage 00: Unaware through Stage 06: Advocacy & Referral) maps every campaign to a purchase cycle position. Campaign Objectives define the specific outcome the platform algorithm is asked to optimize for. Ad Formats define the creative container. This consistency is the system's key architectural insight: platforms differ in their specifics; the discipline of organized campaign structure does not.
One of the IO system's most powerful decisions is the use of a consistent 7-stage customer journey across all nine paid platforms — rather than adopting each platform's native funnel terminology.
"Nine platforms. One customer journey. The IO Marketing OS doesn't ask what each platform calls the consideration stage. It asks what stage the person is at — and which platform gives the best access to them there."
| Layer | Name | Function | Color |
|---|---|---|---|
| I | Knowledge Base | Root — Company, Branding, ICP, KPIs, Strategy | ◆ Amber |
| II | Research Layer | Deep Research (13) + Market Intelligence | ◆ Green |
| III | Strategies | Organic, Search (×8), Paid, Sales, Growth | ◆ Red |
| IV | Context Briefs | Insights, User Search, Creative, Offers & CTAs | ◆ Pink |
| V | Channel Architecture | 6 types, 30+ platforms | ◆ Blue |
| VI | Content Types | 27 formats — Foundation → Automation | ◆ Purple |
| VII | Execution | Planning, Posting, Engaging, Measuring (×8) | ◆ Red |
| VIII | Organic Playbooks | Per-platform organic content systems | ◆ Teal |
| IX | Paid Campaigns | 9 platform campaign architectures | ◆ Orange |