The agent does the job nobody has time to do.

A community manager reads the room, decides what should happen this week, writes it, puts it somewhere people will see it, and remembers what worked. This does all five, for every company at once, without being asked. Here is exactly how, including the parts that are not a model at all.

What it does, in the order it does it.

Nothing in this sequence waits for a person to have an idea. That is the whole difference between an agent and a tool for running events: a tool needs somebody to open it.

It reads the company.

From the name and the work email, before anyone has installed anything. Who their users are, what those people are into, and what the product actually is. A company we have never heard of gets a board written for their users on day one instead of a generic city calendar in their colours.

A model call, once per company, stored on the row.

It reads their design language.

It opens their real site and reads it the way a designer would: what the page is made of, what type they set, how round a corner is, whether cards are outlined or filled, and how they write. The tab renders in that, so it looks like their own team built it rather than like a widget someone pasted in.

Their site, parsed for design tokens, then judged by a model.

It reads each person.

A ring says early riser. A running app says runner. Those are different strings, so two people who both get up and run at dawn used to match on nothing. The agent reads each person once and writes down what it understands about them in one shared vocabulary, and everything downstream runs on that instead of on whatever words a third party API happened to choose.

Refreshed on a schedule, not once at signup.

It programs the week.

Real gatherings, at free public walk-in places, written for that company’s people in that company’s voice. Nothing is reserved and nobody is billed for a room, which is why it can program a city it has never touched on the day a company signs up.

Runs every six hours, for every company, unprompted.

It learns from who turned up.

Every run reads that company’s own past board first: which shapes of gathering filled, which drew nobody twice, which hours worked. That goes in as evidence rather than as a rule, because a model is better at "these three filled and these two did not" than at any rule we could invent about a stranger’s users.

Arrivals once there are enough of them, commitments until then.

How it learns a person.

This is the part that is ours. The inputs are coarse tags anyone could collect. The translation into something two strangers can be matched on is the asset, and reading our API shows you the output and none of it.

The vocabulary is closed.

The agent may only describe someone using a fixed set of traits. Free text would be fluent and useless: "loves early mornings" and "morning person" do not match each other, and we would be back to matching strings with better prose. A fixed set is the only way two people arriving from different apps land on the same word.

A trait is a join key, so it is never renamed.

Entries get added. None is ever renamed, because everyone already carrying the old word would silently stop matching anyone. Anything the model returns outside the vocabulary is dropped rather than trusted, and it does reach for plausible neighbours.

The matching itself is not a model.

Once people are described in one vocabulary, deciding who overlaps is whole word comparison plus a bias toward the hours someone actually keeps. It is deterministic, inspectable and the same every time. We would rather say that than imply a learned matcher we do not have.

It reads what it was given, not everything it could reach.

Coarse tags that were already reduced when the account was connected, and the titles of gatherings the person committed to. No heart rates, no sleep records, no locations, no listening history, no other members. A prompt cannot leak what was never loaded.

What it will not do.

Each of these is enforced in code rather than asked for in a prompt, which is the only version of a rule that survives a model having a creative afternoon.

It never invents a venue relationship.

Every gathering is somewhere anyone can walk into for free. Nothing is booked, nothing is held under our name, and if money is spent each person buys their own.

It never writes the same gathering twice.

Near duplicates are caught by shape, not by exact title, because a model varies the tail every time and a board carrying both reads generated.

It never fills a board with somebody else’s events.

A company’s tab is theirs. Shared gatherings only ever top up what is left after their own.

It never claims a turnstile.

A check in is self reported and can only be tapped while the gathering is happening. That is what makes it worth more than an RSVP, and it is still not proof of presence. We will not describe it as one.

Watch it program a board for your company.

The sandbox is free, needs no card and no call. Give it your company name and it writes your users a week, in your brand, in front of you.

Try it now →Book a demo