Marketing belongs in the repo.

Every marketing claim is a claim about the product. If the source of that claim isn't the code (the actual function signature, the actual behavior, the actual diff), it's a guess. Marketing built from guesses scales linearly with the number of guesses. Marketing built from the code scales with the team's ability to review.

Not Trello cards. Not Notion docs. Not Slack threads. PRs. A pull request is the smallest reviewable, mergeable, revertible unit your engineering team has agreed on. Marketing should use the same unit, not invent a parallel one.

No release should ship without its release note. No release note should ship without a draft blog, social, and changelog entry alongside it. The release is the moment marketing has the most leverage. Most teams use it the least. Origin makes the release the moment marketing happens automatically.

Marketing tools today treat marketers like consumers of engineering's output: "wait until they tell you what shipped." Origin treats marketers like contributors with a different specialty. They commit. They review. They own files in /marketing. They get GitHub badges.

A blog post is a file. A campaign is a folder. A change to a tagline is a diff. You can git blame a marketing claim. You can revert a launch. You can branch a campaign. The same primitives that work for code work for marketing.

Machines draft from the repo. Humans review like a code review. Nothing autopublishes. Origin is not "AI marketing." Origin is a workflow tool with AI inside it. The workflow is the product. The AI is the engine.

Markdown. Frontmatter. Plain text files in folders. No proprietary editor. No lock-in. If you can write a README.md, you can use Origin. If you can review a PR, you can review a campaign. Boring formats are a feature, not a limitation: they are why this works inside the workflow your team already trusts.