Chat
The @orgdevkit/kit-chat messaging surface — channels over circles and projects, named topics with a two-layer thread cap, DMs with people and with role-filling agents, a markdown-lite body, polls and mirrored actions in the feed, work and link unfurls, search, activity, and the agent axis with its consent blocks. One view model, rendered in the kit's three-column shell over synthetic fixtures.
You are Robin Vale, Delivery Lead. Everything here is invented — the people, the circles, the messages, the figures. Nothing is stored, nothing is sent.
About the agent seat
The Operations Steward answers from a short written script, not from a model: the kit ships no model mock, and a demo that invented figures would be worse than one that invents none. The script goes through the kit's own validator like any real reply would, so what you see is only what the kit would really accept — a proposal you consent to, a decision routed to the person who owns it, a preview held back because it read a source not everyone here can see. Questions it covers:
- What is slipping this week?
- Who is holding the migration window?
- What does the ledger say about the overspend?
- Which cut-off should we take?
The surface reports what just happened here.
Delivery
Ship what we said we would, at a pace we can keep.What the host was asked to do
Every write leaves the kit through a host port. Here they are accepted and recorded — nothing is persisted, nothing leaves the tab. The two seams that leave chat entirely, turning a message into work and consenting to an agent's draft, are in this list like any other.
- Nothing written yet.