Notes · for me

Two talks,
one argument

B (territory) is the economic case for A (platform). Goal isn't his agreement — it's no objection on record + concrete next steps he didn't refuse. Just scroll.

Reading Anthony

He's British and he never commits — no clear yes, no clear no. Don't chase a yes; it isn't coming. Silence and politeness = permission to proceed. Only an active objection stops me. Convert everything into a small concrete step he'd have to actively refuse.

🟢 Green — real progress

Asks implementation questions ("who'd run it?", "when?") — he's already inside the how.
Mentions the Board / CA or third parties.
Asks to see it written.
Doesn't object. Silence here is a yes.

🔴 Red — brake dressed as politeness

"Let's not rush." / "Worth thinking about." / "Let me reflect."
"Interesting" with no follow-up question.
Redirects to a different topic. That's a soft no — don't read it as a yes.

✈ Before I walk in

Phone on Do Not Disturb.
Heads-up line: "I prepared this carefully — I'll glance at my phone to keep the thread, not because I'm distracted."
Mindset: I'm not here to win a yes. I'm here to put it on record and pin next steps.

Platform / Membership

What it is, where it goes

🎯GoalIt's on record as a structural line of Demsoc — first infrastructure toward membership — with no objection from him.

🙋PinA date he'll get a draft article from me. Not "will you publish?" — "I'll send you a draft Friday, alright?"

( my position, in one stroke — not an org-chart recap )

C&M isn't one lever among three. Local Infrastructure and Policymaking are the other two — and C&M is the one that connects them, knowledge flowing both ways.

My real job is connecting the four layers — Board (CA), team, collaborators, public — each needing its own kind of relationship. Today that connecting work lives in my head. The platform is what makes it visible and persistent. That's the whole point of what follows.

C&M connects the other two levers

The platform makes the connection visible & persistent

Anchor in his goal

Don't start with the platform. Start with what he wants — harder for him to stay neutral on his own ambition.

I know you've spent years thinking about how Demsoc becomes a membership project. I want to show you this has started to exist — and how.

Makes it "I'm bringing you what you wanted," not "I have a project to defend."

The backbone

Not a gadget. A structural backbone — the infrastructure equivalent of what DSI is as a framework.
Unique value no project solves alone: every project starts from zero at bringing in non-participants, engaging different actors, connecting layers.
The platform is a trusted space where they're already connected. Demsoc becomes the orchestrator that holds the network, not a provider that executes.

The rhythm — 360 Democracy Fest

The network needs a recognisable beat. The annual fest is where it becomes visible — once in person, once online.

Demsoc as connector, not as host celebrating itself. We're at the centre as the ones who connect — not from self-promotion.
It tackles the real problems practitioners face in this field — what events usually skip in favour of theoretical celebration.
It's the moment the layers (Board, team, collaborators, public) and allies across territories meet without us having to be in each territory. (This is the A2 backbone made visible — and it prefigures B2: method + network, not presence.)

Proof — the payment sequence

State it as fact, not proposal. Facts are harder to be non-committal about than ideas.

Each rung is a real test, already in motion

End of June: first paid course (Foundations of DSI). Carlota next week → team validation → sales by month-end if validated.
= the first test of paid access.
Next: premium access to content + interaction.
Destination: paid membership.

Now = test run; next year = real version

Now: the test, done with very little.
Next year: defined, structured, on our own infrastructure (not the US server).
US server: name it myself, lightly, known limitation + alternative pending, move on. I raise it = footnote. He raises it = headline.

The pin — not "will you publish?"

Asking "would you publish something?" hands him a perfect non-answer ("good idea, let me think"). Instead, pin a concrete step he'd have to actively refuse.

I'll draft a short piece for you and send it Friday — you tweak it in your own voice. Does that work?

Silence or "sure" = a yes. He's now on a deliverable, not a vague intention. Have the angle ready: why Demsoc builds community / what it means from the Board's seat that people come back.

Why him: he's the piece connecting team ↔ Board (CA); his written presence materialises the connection of layers.

💬 If he pushes back (A)

Isn't this just another platform / tool?

No tool does the connecting. It's where the network lives — what every project rebuilds from scratch, now persistent.

Let me think about it / let's not rush.

Fine — but shrink the ask, don't drop it. "No pressure on publishing — can I just send the draft for you to look at?" Keep a foot in the door.

Interesting. (and nothing else)

That's not a yes. Land the pin out loud before moving on, so the next step is on record: "Great — I'll send Friday then."

🌉 Bridge A → B

And this — the platform, the network — is exactly what solves the problem that worries me most about the territory.

Territory / Scalability

What the platform is economically for

🎯GoalThe principle is stated and not objected to. That's the bar — not an explicit "I agree."

🙋PinThat we put Valencia's governance on a named agenda (next 1:1 / a short note). A scheduled conversation, not a verdict today.

The principle

Direct territorial action isn't scalable + no spectacular resources — needs allies, presence, effort.
But it's the pilot that proves our capacity for concrete impact.
Once done, it lets us sell the same services where we have no presence. Deep pilot = commercial asset; demonstrated example = what scales.
Gives the why to our pilot logic: not justified by financial return, but as the proof that makes everything else credible.

The scalable model it makes possible

We don't scale presence — we scale method + network. Platform = the infrastructure.

Allies run it locally; the platform holds the connection

Allies across territories using our methodology (DSI).
Relating to each other on the platform.
Without us physically in each territory — unsustainable.
Result: big impact + capacity, small team.

This is the "and how does it get paid for" of the membership talk — the platform turns an expensive territorial pilot into a scalable service model.

Comms = hybrid functionmin dose

Enters as a consequence of the model, in 1–2 sentences, not its own argument.

And that's why, when we talk about who we hire for communications, it isn't a classic profile — the model demands someone hybrid: understands method, curates knowledge, sustains relationships, keeps impact circulating.

Plant it, connect to the model, leave for the hiring talk.

Valencia + my roleif he didn't object to step 1

New gate: I proceed unless he actively objected to the principle. Polite silence passes the gate — otherwise I'd never get here with someone who never commits.

And precisely for that reason, we should clarify how Valencia is governed and read internally — can we put it on the next 1:1?

I'll send you a two-line note on the governance question before then. Alright?

Don't seek a verdict on Valencia today — he won't give one. Pin a scheduled conversation instead. A date is a commitment even when an opinion isn't.

Not about Domenico. About a strategic Demsoc asset with no clear institutional owner.
Framing: "Valencia is read as one person's project, when it's a strategic Demsoc pilot touching my C&M function. That reading takes the asset from Demsoc and confuses who governs it."

💬 If he pushes back (B)

Territory costs too much for what it returns.

Agreed — that's the point. Not a profit centre; the proof of capacity that makes the scalable model sellable.

Isn't Valencia Domenico's project?

That reading is the problem. A Demsoc asset without a clear owner, not a person's project. (Calm register.)

Let's see how it develops.

Classic non-commit. Accept it for the principle, but still pin the governance note: "Sure — I'll send the two lines anyway so it's not lost."

🛑 Objection vs. polite non-commit — tell them apart

Active objection ("I don't think the territory work is worth it", "I disagree the platform is structural"): this is the only thing that stops me on Valencia. Park B4, don't force the role question — pushing it without the principle turns it into a personal complaint.

Polite non-commit ("let's see", "interesting", silence): proceed. With Anthony this is the default, not a refusal. Keep going and pin the next step.

🎬 Close — lock the record, don't fish for a verdict

None of this is a new direction — it's the infrastructure under what Demsoc already does.

So I'll send you the draft Friday and the governance note before the 1:1 — shout if anything doesn't sit right.

And if it helps, I'll write up a short summary of what I've walked you through — want me to send it over?

Offering the summary is itself a pin — a "yes" (or no refusal) is permission to put it on record in writing. Only operational agreements go in it: the pinned steps. Not the internal read of him, not the Valencia framing, not Horizon. Keep that in my head.

⚠️ Keep in mind

Don't chase a yes. It isn't coming. Aim for no objection + a pinned step.
Silence = consent only if I've stated the next step out loud first. Unstated, it's just lost.
Sacred order: principle → consequence → role. Never reverse.
No Horizon / "silent" comms. Opens the trust flank. Separate talk.
Valencia: missing institutional owner, not the person. Calm register.