A point of view workout.

For the interview tomorrow. The meeting next week the rest of the company will judge you on. The concept you've been circling for a month and still can't say cleanly what you think about. Each is a rep. You bring the question; a panel of advisors with different angles takes it on; a critic attacks what emerges; you walk out with a view you can defend. Your reps compound, over time, into a working library of your own expertise.

Pick up a rep Private alpha — sign-in restricted to invited users.

What this is

A structured rep for the views that matter.

Consilium is for people who care about what they think — working professionals, students, researchers, self-studiers — and who want the practice of thinking to compound. You show up with a specific question. A panel of advisors takes independent positions on it; a critic attacks the emerging view; you leave with a durable paragraph of what you now think, and why, in language you'll still recognise under pressure. That's one rep. Do enough of them, across the questions that matter in your work or study, and what you build is something the rest of the internet has stopped producing: defensible expertise that is yours, not synthetic, not borrowed, not approximate.

Not a note-taking app. Not ChatGPT-in-a-wrapper. A structured second mind that argues with you, and a library that remembers what you concluded and why.

What you might bring

Three reasons to pick up a rep.

An interview tomorrow

You're being evaluated on how you think.

Whatever the field — architecture, claims in your discipline, strategy, policy, methodology — your interviewer is testing whether your view holds up. A rep gets you to the durable version of what you think before you walk in. Another rep hardens it against the challenge you know is coming.

An important meeting next week

You'll be asked to take a position.

In front of people whose opinion of you matters. A rep gets you to a real view before the room does. A second rep makes sure the view survives the sharpest objection the room could plausibly bring. You arrive clearer than the meeting is expecting.

A concept you've been circling

Develop yourself and your understanding.

You've been reading about it for months and still can't say cleanly what you think. A rep maps the field; a rep forces a stance on a specific question inside it; a rep sharpens that stance against the best objections. The concept stops being a thing you've read about and becomes a thing you have a view on.

How it works

Three kinds of rep. One compounding library.

Form a view

Ask a question that matters.

A panel of advisors — strategic, technical, stakeholder — each takes an independent position. A critic attacks the emerging view. You walk out with a short, durable paragraph of what you now think, and why, in language you will recognise as yours three months from now.

Map a domain

Name an area of expertise.

The panel maps the field — the big questions, the schools of thought, the canonical sources to engage with, the debates you will need to take a position on. The domain becomes a container for all the views you will form inside it.

Stress-test a view

Bring back a view you already hold.

The panel attacks it. The critic sharpens. You walk out with an updated view — and a visible record of how your thinking changed, superseded paragraphs and all.

What you get, over time

A working library of the views that make up your expertise.

Example domain · what a month's worth of Consilium can become

Event-driven architecture for staff engineering

Current stance: Event sourcing is the right primitive for platforms where audit, replay, and debuggability are first-order concerns — but only when the team can commit to strong schemas and a small, stable set of event shapes. For everything else, a conventional transactional model with a separate event log is the more honest trade.
Views in this domain: View 1 When event sourcing pays off in a 5-year platform horizon

View 2 The right CQRS boundary for a team of 6 engineers

View 3 Why "eventual consistency is fine" is usually a product-shape argument in disguise
Canonical sources engaged: Young on event sourcing · Fowler on CQRS · Kleppmann on log-structured data · internal transcripts from 3 team post-mortems.
Open debates: Does event sourcing help or hurt onboarding speed? · Is the "projections are cheap" claim actually honest?

Who this is for

People who spend their days thinking about things that matter.

Working in any of these? You are the target:

Senior engineers and technical leads forming views on architecture, tooling, and team design.
Product, design, and strategy leaders forming views on markets, positioning, and bets.
PhD students, postdocs, and researchers forming views on claims in their field.
Clinicians, lawyers, analysts, and policy people forming views on contested evidence.
Career-changers and self-studiers forming views on a field they are moving into.
Writers, essayists, and founders forming views on the subjects of their public work.

If you read, think, and want your thinking to be yours and defensible — Consilium is for you.

Have an invite?

Open the app