A public record

A public record of a community, and nobody published who did not ask

Your discussions findable on the web, with publication decided one person at a time.

The question

a searchable public record of my community, without publishing anybody who did not ask

Yes, and the default is silence. She keeps a record of the room, and none of it reaches the public web until a member asks for their own messages to be published. Consent is first-person, so nobody can publish anybody else.

Who this is for

A user group, an open project or an association whose knowledge is currently locked inside a chat and lost to anybody who was not there.

How it works

Forward-only, and reversible in a single read

The two decisions that make this different from an archive with a consent checkbox on it.

Opting in publishes what a member says from that moment onward and never reaches backwards, and the intervals while consent was withdrawn stay permanently unpublished. Publication is not a flag written onto a message: it is a view worked out on every read, so withdrawing consent removes the messages on the next render with no republish step, no cache and no backfill.

What it will not do

It cannot reach into a copy somebody else already took. A feed reader or a crawler that fetched a page keeps what it fetched, and the console says so rather than letting an operator believe otherwise.

Which door

What this needs, and what state it is in

Read from the same table the ways-in page renders, so it cannot be current there and stale here.

The doors this touches

Over a chat network built

What runs today: the chat core embedded in-process, with no daemon and no exposed port, one directory as the only SDK importer, and one core hosting every enabled bot with commands serialized and events routed per profile

Over a web server, as an ordinary web assistantstarted

More than nothing, honestly: a demo route drives the real interaction engine, consent logic and persistence over the fake adapter, with a deterministic rules layer, a 25 message budget and synthetic data. The admin console and the public archive are web surfaces rather than chat ways in

The web door is the one most readers of this page assume they are buying, and it is not finished. The door that is built is a chat network you would have to adopt. That is the honest answer, and it will cost us some readers.

Every way in, and its state

Where to go next

The pages that carry the checks

This page makes no claim of its own. Each one below is where the thing is written down with the way to verify it.

What to read

The archive page carries both gates, the hide-against-delete choice and the withdrawal path; the consent page carries the retention sweep in full.

The archiveHow consent worksSecurity, claim by claim