Kreeda. How marketing runs →

How Kreeda is run

The systems

Four systems, each meant to run itself on language models with one person approving. What each one is made of, how the parts talk to each other, and where a human is in the loop.

live — runs todaybuilding — part of it runsplanned — designed, not built

Same shape everywhere: Agents propose, code executes, a person approves by merging a pull request. In the diagrams: green is an Agent, blue is code, amber is the person, a cylinder is a store, dashed is not built yet.

Analytics live

What the site can see about who plays — GA4's numbers, drawn at /analytics/; an Analyst that reads them is next.

Analytics: every Game page sends events to GA4; an Actions job reads GA4 daily and after each Publish run and writes data.json; the graphs draw it; a planned Analyst reads it each morning and writes a note. Every Game pageanalytics.js on every load GA4events Snapshot jobGitHub Actions daily · after each Publish run data.jsonon main Graphs/analytics/ Analystwhat changed, one page 09:00 IST desk · planned page_view · played_30s reports writes draws reads X and Meta pixels get the same played_30s players read by a service account
Nothing here publishes or spends, so nothing here needs a signature.

Parts

analytics.jscode
On every Game; sends the page view and the honest Player (played_30s, thirty seconds of real input) to GA4, X and Meta from one clock.
GA4store
Holds the events; read per Game, Campaign, country and hour by a Viewer service account.
Snapshot jobcode · Actions
Reads GA4 daily and after each Publish run; writes data.json; never read back by anything that decides.
Analystagent · planned
Reads the snapshot each morning; writes what changed and why it matters.

Steps

  1. A Game page sends its page view and, after thirty seconds of real input, its Player.
  2. The snapshot job reads GA4 and writes data.json; the graphs draw it.
  3. The Analyst, once built, reads it and writes the morning note.

The person in the loop: nobody.

Read, never approved; its Analyst will write, never decide.

Shared with

Marketing's Analyst reads the same GA4; the Ledger's attribution is this data with money attached; Product Management's reports quote it per country.

Product Management building

Decides what to build next: reports per Market, a health note per Game, one ranked Backlog, a spec per item the CEO backs.

Product Management: the Market Researcher writes reports from a market; the Product Analyst writes the health note from GA4 and the feedback strip; the Product Manager reads both into the Backlog; the CEO backs an item; the Product Manager writes its spec; the CEO merges the spec pull request, which hands it to Product Development. A Marketthe web GA428 d · feedback Market Researcherone Market per run Tue · Fri 10:30 IST Product Analystevery Game, weekly Mon 10:30 IST Reportsresearch/markets Health noteproduct/health Product Managerbacklog · specs Mon, after the Analyst Backlogproduct/backlog CEObacks an item Product Managerwrites the spec Specsproduct/specs CEOmerges the PR Product Developmentplanned reads 28 days report health note both ranks reads backs spec PR merged
Three Agents, two amber gates: the CEO backs an item, and merges its spec.

Parts

Market Researcheragent · live
Tue/Fri, one Market from the growth rotation; GA4 for the country, the catalog, the web → the Market report, emailed to the CEO.
Product Analystagent · live
Mon; every Game over 28 days — sessions, honest Players, engaged seconds, returning share, 👍/👎 and why → the health note: delights · holds · loses · unreached, one change per weak Game as what the player gets.
Product Manageragent · live
Mon, after the Analyst: every concept and every change as one ranked Backlog; on demand, one spec per backed item — loop, controls, rules, scope, acceptance, success metric.
Reports · Health note · Backlog · Specsstores · on main
marketing/research/markets, product/health, product/backlog.json, product/specs; every one travels by pull request.
CEOperson
node cli.js product back <id> or decline, committed by hand; merges each spec's pull request. Approves nothing in Marketing.

Steps

  1. The Researcher reports on the rotation's Market; the Analyst grades every Game on what players did.
  2. The Product Manager folds both into the Backlog — one ranked list, with what to spec next.
  3. The CEO backs an item (or declines it, with a reason) and commits the Backlog.
  4. The Product Manager writes the backed item's spec; it goes to main as a pull request.
  5. The CEO merges it — that merge is the hand-off to Product Development.

The person in the loop: the CEO, as Product head.

Backs Backlog items and merges specs; nothing is built that nobody backed.

Shared with

All three run on Marketing's runtime and routines (ADR 0017); the Analyst's GA4 read is Analytics; a merged spec is Product Development's input.

Product Development planned

Builds a Game from a spec and ships it to the hub — designed, not built; every Game so far was built by hand with an AI pair.

Product Development, planned: a merged spec goes to a Builder agent, then the verify harness, then a Reviewer agent, then a pull request a person merges; the Game appears on the hub; a failing check returns to the Builder. Specsmerged Builderone HTML file per merged spec Verifyharness, virtual clock Revieweragainst the spec Pull requesta person merges the gate The huba new card, live spec build green review deploy failing check, named plays it, reads it
All dashed. The one rule already true: nothing reaches the hub except through a merged pull request.

Parts

Builderagent · planned
Writes the Game in house style: one self-contained HTML file, no build step, playable from disk, analytics.js included.
Verify harnesscode · planned
Drives the real page under a virtual clock; refuses a Game that fails its own checks.
Revieweragent · planned
Plays it, reads it against the spec and the brand rules, writes the review.
A personmerges
Merges the pull request; the deploy is automatic and the hub card appears.

Steps

  1. A merged spec starts a build.
  2. The Builder writes the Game and its harness; a failing check goes back to it, named.
  3. The Reviewer writes the review; a person merges; the Game is live.

The person in the loop: whoever merges.

One merge ships a Game; the review is written so it takes minutes.

Shared with

Input: Product Management's spec. Output: a Game Analytics measures from its first page view and Marketing promotes from its first week.

Marketing live

Grows the player base — organic Posts, paid Campaigns under fixed Caps, a public Ledger — with seven Agents proposing, a deterministic Producer executing, and the CMO merging one Review a day (the long version).

Marketing: the Analyst, Strategist, Media Buyer and Performance Analyst write to the state branch; the Producer reads it, calls the Creative, writes the Review the CMO merges, then publishes Posts and launches Campaigns on the Channels; metrics return to GA4 and the Ledger, which the Analysts read; the Chief of Staff briefs the CMO on Sunday. Analystinsights.json09:00 IST desk · daily Strategistweekly-plan + DraftsSunday Media Buyerads-proposals.jsondesk · when Caps allow Perf. Analystads-learnings.jsondesk · each Ended Campaign Chief of Staffbriefing.mdSunday Statemarketing-statebranch the Producer is the only writer Producercode · cli.jsCaps, kill rules,ladder, retries Windows 09 · 13 · 17 IST CreativeGemini, called by code The Reviewone PR a dayCMO merges, orit merges itselfin 15 min the gate ChannelsXFacebookInstagramMeta ads Ledgerpublic, on main GA4Players CMOunticks, merges proposals reads brief Post Review merged Post · Campaign metrics writes Ledger + GA4 back to the Analysts Briefing
Green proposes into the state branch, blue reads it and executes, amber approves. Nothing crosses from the Producer to a Channel except through the amber box; there is no autopublish flag.
The Review gate: Agents propose; the Producer writes the Review pull request, pre-ticked; it reaches the CMO's phone with a mention; fifteen minutes later it merges itself unless unticked, merged or closed; the Producer publishes and launches what was ticked. Agentspropose Producerwrites the Review CMO's phone@mention, checklist 15 minutesmerges itself Producerpublishes state PR, pre-ticked untick · close ticked unticked is rejected · closed asks again tomorrow the only route to a Channel
The Review gate. Silence is consent, and it is still the CMO's: the ticks at the moment of merging decide.

Parts

Producercode · cli.js
Never a language model; runs the Cycles, publishes, launches, enforces Caps and kill rules, writes the Review, Run log, Ledger, Alerts.
Analystagent · daily
Reads metrics, Ledger, Post-mortems, GA4; writes insights.json and which Game is ready for spend.
Strategistagent · Sunday
Reads the insights and catalog; writes the weekly Plan, one Draft Post per Slot, and the paid focus.
CreativeGemini · each Window
Fills each Draft ≤ 48 h out with copy, card, video; a failure leaves it Draft, never template copy.
Media Buyeragent · desk
Proposes a Campaign when the Caps have room a day ahead: Game, angle, targeting, budget from the ladder, a promise.
Performance Analystagent · desk
Post-mortem per Ended Campaign: promised vs delivered, cost per Player, Winner or Loser; a Winner renews itself.
Chief of Staffagent · Sunday
The CMO's Briefing: numbers, what worked, what the system decided, what needs a person.
Market Researcheragent · Tue/Fri
Shared with Product Management; not part of any Cycle.
The Reviewone PR a day
Every Post and proposal awaiting a decision, pre-ticked; merging approves the ticked; merges itself after fifteen minutes.
CMOperson
Reads the Review, the morning Campaign report, the Briefing; sets the Caps; answers what costs money.
Ledgerstore · public
/marketing/ledger/: what the system did and what it earned.

Steps

  1. Morning: the Analyst writes the insights; Sunday: the Strategist writes the Plan, one Draft per Slot.
  2. Each Window: the Producer calls the Creative for Drafts due within two days; the Media Buyer proposes when the Caps have room.
  3. The Producer writes the pre-ticked Review; it merges itself in fifteen minutes unless the CMO acts.
  4. The Producer publishes at the Slots and launches in money-safe order, kill rules on every live Campaign.
  5. The Performance Analyst judges each Ended Campaign; a Winner renews into the next Review; the Ledger records it.

The person in the loop: the CMO.

Merges the Review or lets it merge itself; reads the Campaign report and the Briefing; sets the Caps; answers the questions that cost money; never edits state by hand.

Shared with

Its Analyst reads Analytics' GA4; its Ledger is Analytics data with money attached; its Researcher is Product Management's; what it promotes is whatever Product Development ships. It grows once 25,000 real people a day play.

How the four fit

Analytics feeds Product Management, which hands specs to Product Development, which ships Games to the hub; players play; Marketing brings more players; every number flows back to Analytics. Three human gates: the CEO backs concepts, a person merges a Game, the CMO merges the Review. Analyticswhat is happening Product Mgmtwhat to build Product Devbuilds it The hubthe Games Players Marketingbrings more numbers spec Game play Posts, ads everything a player does comes back as a number CEO a merge CMO
One loop; the amber marks are the three signatures a person gives.

Analytics says what is happening; Product Management says what to build; Product Development builds it; Marketing brings the people who play it.

Three signatures keep it honest: the CEO backs a concept, a person merges a Game, the CMO merges the Review.

Marketing runs today; the rest arrive in order, and Marketing scales up once 25,000 real people a day play.

The company

One creator and seed money in; a self-sustaining company out, once monetization is figured out.

The company loop: the creator and seed funding feed the four systems, which bring players; monetization, once built, replaces the seed. Creatorapproves, funds Seed moneytokens · ad budget Four systems Analytics · Product Mgmt Product Dev · Marketing Agents propose code executes a person merges Players Monetizationnot built yet Revenuereplaces seed merges seed Games · ads play self-sustaining: revenue funds the next run

In: one creator, and seed money for tokens (development) and Campaigns (marketing).

Running: the four systems — Agents propose, code executes, the creator merges.

Out: players; once monetization is built, revenue replaces the seed and the company sustains itself.

Five directions

  1. Talk less, do more. Succinct, always.
  2. Never lie or assume. Measured, inferred or unknown — say which.
  3. Customer first, not money. Give value; payment follows.
  4. Go deep. Value is in the details.
  5. Take action. Don't block yourself.