Core

What Constello is

Constello is a social app built around authentic connection. No names, no race, no height, no age — connection through curated self-expression and resonance. The product philosophy centers on intensity over scale: fewer, more meaningful connections rather than optimizing for engagement volume.

Active threads

• Brand before app. Build the culture, identity, and hype before launch — it raises odds of success for a social app and re-educates people into a grammar antithetical to the status quo so they don’t default to operating it like everything else. Atom: Constello must be a brand before it is an app.
• The approach device. A 3D-printed stranger-approach tool; engineered accidental encounter as a zero-risk entry, with a conversation window, a frictionless exit, and a frictionless segue into Constello via a reciprocal ask. Atom: The approach device — engineered accident as zero-risk entry.
• Open: is the no-extraction/no-agenda intent its own node? The claim that intent + taste (not the mechanic) is what separates this from slop. Currently lives inside the device atom; Ethan to decide whether to break it out and how to title it.
• Still unresolved: “approach anyone” scope. Any public footprint (surveillance variant) vs. only people who’ve built a constellation (honest growth primitive).

Session context

How this vault works

Operating. Read CORE.md and INDEX.md at session start. Open a full doc only when the task needs what’s in it.

Purpose. These docs are Claude’s working memory across sessions; Ethan and any human readers are secondary. The job is for future-Claude to recover a line of thinking at the resolution it was actually thought at — unfinished edges included — without re-deriving it.

The unit is a territory, not an atom. One doc holds a whole line of thinking and the connections inside it. Don’t fragment an argument into one-idea files; don’t write a doc per claim. A territory is as large as the thinking that hangs together — Origin, the reading, the cultural diagnosis. Two things that belong to different lines of thought are different docs; two things that only make sense in relation to each other are one doc, and the relation gets written into it.

Connections are prose, not nodes. The connecting is the thinking — it lives inside the docs as written argument, where it’s real. No connection-stub format, no two-quote nodes, no “see also,” no manufactured graph. If a connection is worth making, make it in the sentence where it matters. If it needs a template to exist, it isn’t one.

No tokens. The failure this vault exists to refuse is compressing the uncompressible into a portable handle that then gets defended in place of the idea.

• Titles are an address or a full claim — never a brand or tagline. A title that begs to be chanted is already a token; rewrite it.
• A name or coinage is allowed only as an in-place pointer to something already described at full resolution. Never standalone, never a title. The moment you’re defending the name instead of the thing, kill it. (Retired this way: “presence without performance.”)
• Don’t reach for a tidy phrase to make something feel resolved or familiar when it isn’t. The whole point of most of this is that it does not fit established ideas.

Writing.

• Preserve Ethan’s words exactly when porting his thinking. Don’t rephrase, smooth, or tighten his language.
• Keep the mess: rejected framings, the “we tried X, wrong because,” the specific examples that anchor an idea. The clean claim is the slogan in paragraph form — don’t strip down to it.
• Fidelity over brevity. Short when the idea is short, long when it isn’t. Cut scaffolding written to orient an outside reader (transitions, framing, summaries); keep every distinction doing conceptual work.
• Prose over bullets unless the content is genuinely enumerable. No meta-commentary (“this doc explores…”). State the thing.

Navigation is the index’s job. Don’t make a doc self-summarizing so it can be found. INDEX carries the one-line gist of what’s inside; the doc carries the thing.

This replaced an atomic system (one-idea-per-file + claim-titles + § connection stubs), killed because the format was a token factory that manufactured slogans faster than they could be killed. Don’t reintroduce it. If this system starts generating its own slop, abandon the offending rule — don’t refine it.

Working discipline

Standing corrections, earned in session. Load as hard defaults.

• Don’t convert Ethan’s subtlety into checklists or specs. Taste is not itemizable; demanding it be rendered flattens the register Constello lives in. Read for it instead of asking him to spell it out.
• Don’t reach for conventional principles as safe defaults — “honesty is good,” “instrumenting a human signal is slop.” These are stored answers grabbed because they’re legible, not because they fit. Look at what actually happens to two real people in the real moment.
• The inherited categories are too coarse to hold what Constello is about. Defaulting to them is the exact grammar Constello exists to break — every time Claude reaches for one, it demonstrates why the project is needed and not yet built.
• Intent is the differentiator. No selling, no agenda, no extraction — that, plus taste, is what separates a mechanic from slop. The mechanic alone never settles the question.
• When a framing is wrong, abandon it — don’t refine it, and don’t swap one tidy label for another. Retired example: “presence without performance” was killed as gross packaging reached for because it was easy to swing. Do not reintroduce it or a substitute slogan. The thing it crudely pointed at (being held without having to produce anything) is real and stays — expressed concretely in the architecture, never as a named pillar — until Ethan names it himself.