Combobulato — Manifesto

Most of the internet is built to engage System 1 — Daniel Kahneman’s name for the fast, automatic, reflexive mode of thinking. What the industry calls “engagement” is, in System-1 terms, a thoughtless, immediate, emotional response: tap, scroll, react, repeat. Combobulato is built in the opposite direction. Everything that follows in this manifesto is in service of one shift — from the System-1 response the rest of the industry is designed to provoke, to the System-2 act that only deliberate, slow, considered attention can produce. The thesis, the substrate, the dissenting voice — all of it is the shape that commitment takes when it becomes a product.

What that commitment looks like in practice: a small, opinionated, human-heavy app, building against the prevailing direction of the industry — something closer to a cooperative that happens to be software than to a platform trying to scale to millions with a skeleton crew.

The thesis: three things move us

What is said, what is done, and presents.

Move is the load-bearing verb. It does not mean engage with; it means change position. A reader is moved when their stance shifts — when reading, hearing, or receiving something from another person leaves them somewhere other than where they started. The product is built to make that kind of shift more likely and to give it a place to land. Every feature is answerable to the question: does this make moving easier, or does it make it cheaper?

The three things are separate but inter-related vectors. Each is its own product surface, with its own data model, its own UI, its own commitment-shape from the user. They are not facets of the same thing. They cross-reference — a note can be about a to-do; a to-do can generate a wishlist item; a gift can fulfil what a note articulated — but the three vectors are first-class on their own terms. The three are not equal in current implementation (notes are shipped most fully; to-do lists are shipped — personal layer in place, shared-and-pledged layer partial; presents are partially shipped) but they are equal in standing.

What is said — notes

• The product surface is the note. A note is what one person has considered and put into words for others. Notes are written, not posted — the language we use should reflect deliberation, not publishing.
• Comments are responses from one named person to the writer of the note. They are not Reddit-style replies-to-replies-to-replies. The relational unit is the pair, not the thread.
• Attribution is the substrate. Who said it, to whom, in what circle, when. Pseudonymous-with-persistent-identity is the floor; anonymity is not on offer.
• Topics, circles, and mentions are how notes find context. A note in a personal circle is private; the same note shared to a &circle carries a different obligation; the same note tagged #topic finds readers across circles. Context governs reach.

What is done — to-do lists

• The product surface is the to-do list. A to-do is what one person has committed to do. Doing is the second axis on which people change position relative to each other — alongside saying (notes) and giving (presents). Not a productivity feature; one of three things the product is about.
• Each list belongs to one circle. A personal list lives in &personal and is private; a list in a shared circle is visible to circle members. Lists advance from personal to shared-with-a-circle by deliberate UI step, not automatic propagation. List visibility is always gated by circle membership — even on anyone-read circles (curated and open), lists stay members-only. Notes have an additional anyone-read surface on curated and open circles that lists do not share; the doing vector is structurally anchored to relational containers in a way the saying vector is not.
• Items on shared lists can be pledged, the way wishlist items can. I’ll do that one is the doing-vector’s coordination mechanic, structurally parallel to gift-giving’s. When someone has pledged, the relationship around the item has standing — deletion becomes a request, not a unilateral act.
• The navbar surfaces doing at all times. A clipboard icon with a count of incomplete items lives in the navbar. Doing is not a feature buried two clicks deep; it is one of three things the product is about.

Presents — wishlists and gift occasions

• The product surfaces are wishlists and gift occasions. A wishlist is what one person hopes to receive; a gift occasion is the moment that anchors the giving (a birthday, an anniversary, a milestone, a “just because”). Inside a circle, the two are coupled: a wishlist anchors to one or more occasions, and an occasion without a wishlist is an empty prompt. Both surfaces are anchored to the shared social context of a circle, and degenerate on a public surface — neither admits an anyone-read path.
• Gifts happen inside trusted relational containers. Wishlists are unique-per-user-per-circle; pledges are one-per-user-per-item. Scarcity is preserved; coordination is the substance. There is no public gift surface.
• Combobulato is an organisational layer for real-world gift-giving, not a delivery intermediary. The product holds the social context — who, when, what is hoped for, who has pledged. The gift itself flows through the real-world relationship between giver and recipient. No payment integration in the presents path; no escrow of pledged contributions; no address brokerage; no tipjars. (Principle-level treatment: principles/GIFT_ORGANISER_NOT_DELIVERY.md.)
• The marketplace, if it ever arrives, must respect the principle that people like marketplaces but not being sold there. Discovery for users is welcome; transactional pressure on users is not. The Virtuous Circle (see principles/VIRTUOUS_CIRCLE.md) explores this as a possible future, not a committed direction — and is admissible only insofar as it stays consistent with the gift-organiser-not-delivery commitment above.

The substrate

Three platform-level commitments sit underneath every interaction. They are not features that can be turned off, redesigned, or scoped out. They are the architecture of the relationship between two users at the moment of attention.

The lorry — Moved Me

A small lorry icon sits at the foot of every note (and, in time, every comment). Tapping it says: this moved me. The metaphor is deliberate — a lorry implies weight and transport, a journey from one position to another. Not a heart. Hearts are instant and disposable; the lorry is the unit of the thesis.

The lorry is two-tempo. The first tap is System 1: gut, instinctive, in the moment. Days later, the note resurfaces on the reader’s home feed and asks the second question: still moving me? The reflective confirmation is the substantive signal. This split between the fast first response and the slow second one is the structural commitment underneath every product surface that reports impact.

The home feed inverts recency: posts confirmed still moving me sit above posts that were merely written most recently. The principle is recency of impact, not recency of publication. (Full elaboration: docs/MOVED-ME-feature-spec.md; principle-level treatment: principles/MOVED_ME.md.)

Out of frame

The complementary mark to the lorry, for posture failures: comments written in bad faith, thoughtlessly, or intended to hurt. Three explicit criteria, named in the product, applied by the reader.

Out of frame is a judgement about the comment as an act, not a report of how the reader felt. The mark is single-name — which of the three criteria applies stays in the reader’s head — and is signed, dated, and preserved beside the comment. Mutually exclusive with the lorry per reader: a single comment can be moved-me’d or out-of-frame’d, not both.

The lorry and Out of frame together are the platform’s full reactive vocabulary at the comment level. Everything else — deletion, blocking, hiding, downvoting — is rejected. (Principle-level treatment: principles/OUT_OF_FRAME.md.)

The open-platform contract

Open posts are considered, not raw.

To publish a note into an anyone-read &circle — curated (admin-curated posting) or open (self-join posting) — is to engage from a deliberate distance: professional, academic, or at-least-somewhat-abstracted. Anyone-read circles are the platform’s public-facing surface: notes published there are read and commented on by anyone, including non-members and logged-out visitors. The act of publishing into one is consent to robust criticism and consent to be aggregated to &townsquare if the mover signal says you landed — &townsquare is the platform’s first-impression surface, gathering the most-moving content from across all anyone-read circles. Emotional support, vulnerable disclosure, and unguarded thinking live in members-only &circles (private), where the relational container is the protection. A reader who needs protection from open criticism — or from amplification — should not be publishing into an anyone-read circle; the product will not pretend otherwise.

The contract is the answer to why don’t you protect open commenters more? — and the answer is that the protection lives in choosing the right surface, not in the platform second-guessing the writer’s choice. (Principle-level treatment: principles/OPEN_PLATFORM_CONTRACT.md.)

The dissenting voice

Despite everything, I value what you reckon.

Even in a system designed for System 2, people will be people, and we respect that.

This line stays in the manifesto deliberately. It is the dissenting voice within the manifesto’s own architecture — the personal, the gut, the System-1 response that doesn’t fit the deliberative frame of the rest of the document. We keep it because the alternative is a manifesto that pretends its author is purely deliberative, and that would be a lie about the product as well as the author.

The principle this commits the product to: System-1 responses have standing. The lorry as the affordance for the gut this moved me tap is the same move at feature level that this line is at manifesto level. The contrarian comment preserved with attribution, the standing-aside that names a non-engagement without silencing the other party, the personal voice within a deliberative architecture — these are all instances of the same move. The dissent the product cares about most is the dissent it makes legible.

A System-2 product that refuses System-1 responses entirely is not honest about what humans are. We do not make that refusal. (Principle-level treatment: principles/DISSENTING_VOICE.md.)

Status

This manifesto is a working document. The principles enumerated above each have a sibling file in principles/ that elaborates them; values about the nature of the work — how we build, who we build with, what we will and will not do — live in VALUES.md. Decisions made under any of these principles are recorded as ADRs in docs/. The methodology for all of this is ../DESIGN_METHOD.md at the workspace root.

The manifesto is expected to iterate. Earlier versions live in git.