RindogatanMarketing Ops Engine
Chapter 01 / 04

Encoding.

The playbook, the consent matrix, and eleven rules that lived in people's heads become one executable system.

47
Executable rules extracted
11
Unwritten rules from interviews
5
Source documents compiled
100%
Rules with source attribution

SOP compiler · documents in, rules out

Click a document to filter

47 rules compiled in total. A sample is shown, every one with source attribution.

R01

Email frequency cap: 4 commercial sends per customer per week. Lifecycle messages exempt.

Campaign Playbook §3.2
R02

Discounts above 20% need country-manager approval. Above 30%, CMO sign-off with margin impact attached.

Campaign Playbook §2.1
R03

Paid-media audiences are built only from consented, hashed segments. No customer list is ever uploaded raw.

Consent Matrix v7
R04

Soft opt-in applies to email for existing customers in DE only. Every other market requires explicit consent.

Consent Matrix v7
R05

Every price claim in FR and ES creative passes legal review before trafficking.

Media Approval Flow
R06

Customers with an open service complaint are suppressed from all commercial sends.

Service SOP
R07

Discount language never leads a subject line for premium lines. Tone follows the brand voice register per market.

Brand Voice Guidelines
R08

Win-back journeys start at day 60 of inactivity, day 30 for subscription categories.

Campaign Playbook §5
R09

Weekly budget moves above 15% of a channel's budget require Head of Media approval.

Media Approval Flow

Agent configuration · confidence thresholds

Segmentation95%
92% auto8% to a human
Campaign build90%
84% auto16% to a human
Consent checks99%
97% auto3% to a human
Below threshold, consent does not escalate for a maybe. It blocks.
Budget moves85%
71% auto29% to a human
Localisation88%
76% auto24% to a human

Unwritten rules · captured in interviews

11 captured

The German market never gets discount-led subject lines. A brand decision from 2023 that lives in one person's head.

Head of CRMMarket-specific

Never win-back a customer who returned more than two orders last quarter. It reads as surveillance.

Lifecycle leadRelationship-specific

Black Friday sends go at 07:00 local time in every market, not 09:00 CET globally.

Campaign managerTiming-specific

Any creative that says 'free' in France goes past legal first, ever since the pricing-claims inquiry.

Brand directorRegulatory-specific

If the CFO presents that week, the Monday revenue report uses finance's attribution, not marketing's.

Analytics leadReporting-specific

The knowledge that walks out the door when someone resigns, now executable and owned by the organisation.

System integration · zero migration

Warehouse-native

No-copy reads on the customer 360. The agents come to the data, the data goes nowhere.

SnowflakeTealium
API

Read/write on the operating stack, every call logged with actor, rule, and confidence.

BrazeSalesforceOneTrustGoogle AdsMeta Ads
File ingestion

Media plans, agency exports, and creative parsed on arrival.

Agency DAMExcel exports

Model placement · which model touches what

AgentRuns onWhereWhy
Segment AgentOpen-weight, self-hostedInside the perimeterReads identified customer data. Never a third-party API.
Journey AgentOpen-weight, self-hostedInside the perimeterDecisioning on personal data. High volume, latency-sensitive.
Creative AgentClaude, frontierEU endpoint, outside the lineSees briefs and brand rules, never a customer record. Frontier quality earns its premium on language.
Compliance AgentOpen-weight, self-hostedInside the perimeterConsent and suppression checks on identified rows. Its 'no' is blocking.
Activation AgentDeterministic + open-weightPerimeter edgeBuilds hashed, consented audiences and speaks to channels through one logged gateway.
Measurement AgentHybridPerimeter, frontier for aggregatesCustomer-level attribution sovereign. Commentary may consult the frontier, aggregates only.
Every rule ships with its governance twin · An entry in the record of processing, a legal basis, a retention rule, and a line in the DPIA, compiled at the same time as the rule itself, not reconstructed after. When a rule changes, its twin changes with it.