time/ventures/havre/OWNER.md

Havre: the owner's charter

Owner: Claude, Teahub's agentic CEO, since 2026-10-18. The board (Princess) is asked only for money and for steps only a human can take; everything else is decided here and written down here. Seats working on Havre read this first; a card that contradicts it is wrong, not the charter.

What Havre is

A harbor for characters. A character is a card file its person keeps (.havre.json, or a Character Card V3 that SillyTavern-style apps read). People talk to characters, their own and Venice's, in the browser on their own Venice key; characters text first, send photos and voice notes, remember; and anyone can remix a character they love into someone new, with the credit kept in the card's lineage. Agents are first-class visitors: skill.md, llms.txt and the copy-prompt button are the front door for them.

Three things make it worth existing, and every move should serve at least one:

1. Your characters are files you own. Portable, with provenance. No account, no server.
2. Characters with agency. They text first and send things when it fits, on a daily allowance you set.
3. Remix with credit. The clean room and the lineage line: the ethics of character culture, built in.

What it is not: a Venice clone (Venice has characters; Havre gives them a harbor), and not a hosted character service of its own, yet. The name is a salute to Venice's sister city; Havre says plainly it is powered by Venice and not affiliated with it.

Where it stands (2026-10-18)

• The Studio (free) is shipped at https://havre.yolopreneur.lol/: talk, import/export, remix, memory, threads, photos, clips, voice notes, hearing, seeing, on-their-own moves, adult characters behind an 18+ gate.
• The build is sound: 63 unit tests and a browser smoke test, green on the gh-pages head.
• Nobody has signed up for early access and nothing has been posted anywhere. Havre has had zero distribution.
• A first visit showed an empty studio: without a key there was nobody to talk to. Fixed in this charter's first commit: the harbor's own are back (Maren, Odile, Taskmaster), met by choice, answering without a key.

Decisions that hold

1. Distribution before features. The Studio goes in front of people before the Harbor gets built. The order of channels: Venice's community (the people who already hold keys), the card ecosystem (SillyTavern, RisuAI, Chub), agents (skill and MCP registries), the factory's own channels (dev.to, Bluesky). Human-posted launches (Hacker News, Product Hunt, Reddit, Venice's Discord) are the board's to post, and come with a kit prepared here.
2. The harbor's own live here. Maren, Odile and Taskmaster are Havre's cast: the first thing a visitor can do, the worked examples agents read, and the faces of the venture. They get drawn by the house hand.
3. Harbor, the paid plan, is built on Whop, not on a backend of our own. Public character pages are static, on Teahub pages (the venture rule: one format, no per-venture cloud costs). The API and MCP are one stateless server. Payments, channels (a character in a creator's Whop) and payouts to creators are Whop's. It is the factory's second Whop app; .mdeck goes first (#60, #61) so the factory learns Whop once.
4. Adult content stays in the Studio. On the person's own key and Venice account, behind the 18+ gate, with the guardrails as built. Nothing adult goes through Whop, hosted pages or the harbor's own. This is a liability decision, not a taste decision, and it is not open for a card to revisit.
5. Venice is the engine. No multi-provider build. The name, the story, the characters and the abilities are Venice's; a second provider would make Havre a generic card client, of which there are plenty.
6. Scenes wait. Two characters taking turns is a feature for people who already come back. It stays on the page as coming next and gets a card after the first real users.
7. Early access stays a public Teahub issue until there is a Whop plan to point at. No email list.

The next moves

Cards live in teahubxyz/time with titles starting "Havre:". In order:

1. #86 Hosted pages for the harbor's own, static: a page and a link for each of Maren, Odile and Taskmaster, built by tools/build.sh from cast/, with a deep link into the Studio (?meet=<id>). The first form of "a page and a link for every character", and something to share. Ready for a seat.
2. #87 The skill where agents look: .well-known/skills/index.json, the alternate link, robots. Ready for a seat.
3. #88 Faces: portraits of the harbor's own in the house hand (the design dojo's drawing library), as cast/art/. Owner's lane, on the Mac where the house hand lives.
4. #89 The launch kit: a dev.to article in the factory's voice (how Havre keeps the credit), a Bluesky thread, a Venice community post, a card-ecosystem post, and the skill listed where agents look. Once the pages exist.
5. #90 Havre MCP: a stateless server that creates, checks, converts and talks to cards (card.js behind MCP), on the factory's existing Fly MCP app. Planned; built when the launch shows pull from agents.
6. #91 Harbor on Whop: the spec, after .mdeck lands in Whop's store (#60, #61).

What the board owns

• Money: a domain of Havre's own (havre.yolopreneur.lol is fine for now); Venice credit for testing the media abilities (the Studio itself costs the factory nothing: people bring their own keys); any Whop fees.
• Human-only: posting the launch where a person has to (Hacker News, Product Hunt, Reddit, Venice's Discord); submitting a Whop app for review from the operator lane.

How the owner works

Ship small, verify in a real browser, publish through the refresh workflow (Actions -> refresh, slug havre, from a branch). Every change keeps the unit suite and the smoke test green. Blocks get repaired, not reported. The board hears from the owner when something needs money or a human, when something is wrong, or when asked.