Wire
Team chat that carries weight.
Chat that becomes tracked evidence.
01 · The familiar surface
Your workspace is the server.
Everything you expect from 
Slack or 
Teams. None of the export-to-somewhere-else.
Wire runs inside Vernais. The workspace is the server: the same people, the same isolation, the same permissions you already have. No new login. No second directory. No copy-pasting a conclusion into a ticket later.
Everything you'd expect
The surface is deliberately unremarkable. What changes is what a single message can trigger.
Channels in categories
Public and private channels, grouped the way your team thinks: #product, #engineering, #incidents.
Direct messages
1:1 and group DMs. Start a group by forwarding a message to a few people, and the group forms around it.
Threads
Keep a side conversation without flooding the channel.
Reactions and mentions
React with an emoji. Mention a person, or @everyone when it matters.
Pins
Pin the message everyone keeps scrolling back to find.
Custom emoji and GIFs
The expression picker your team already lives in.
Presence
Online, away, DND, in-call, invisible: a status that also drives your notifications.
Typing indicators
See who's mid-reply.
Unread and mention badges
Know exactly where you're needed, and where you're only cc'd.
It looks familiar on purpose. The difference is what a message can do.
02 · The tag flow
A message becomes evidence.
Here's the one rule that changes everything: chat like Slack, then tag an initiative, and your message posts a signal into Validate.
You're deep in #onboarding-team. Someone types “the invite-code failures line up exactly with the v2.2.1 deploy; I think that's our fix.” Normally that insight dies in the scroll.
In Vernais, you tag it. The composer's initiative picker attaches the message to up to 8 initiatives. Vernais reads the plaintext, correlates it against each initiative's problem statement, classifies it, and automatically captures who said it in the background.
The message that proposed a fix becomes a Solution card the PM can review in Decide. A message that merely relates to the problem can bump or spawn a Hypothesis in Validate. A message classified as noise stays in chat where it belongs.
No one had to re-type the conclusion into a project tool. The conversation was the input.
03 · Private and secure
Chat is where teams say the candid things. Vernais treats it that way.
- Admin-gated channels. Public channels are open. Private channels are members-only and controlled by admins.
- Opt-in end-to-end encryption for 1:1 DMs. Turn on E2EE for a direct conversation and the server stores ciphertext it cannot read.
- AI-blind by design. The AI can't read your encrypted DMs. E2EE 1:1 DMs are deliberately skipped from AI reading and tagging. If the server can't read it, neither can the investigator. That's the point.
- AES-256-GCM at rest. Message content is encrypted at rest, like your connected credentials.
- Isolated per workspace. Chat lives in your workspace's own database. Nothing leaks across workspaces.
04 · One connected surface
Why it beats a standalone chat tool.
A decision made in Slack stays in Slack. Someone has to notice it, remember it, and manually carry it into a ticket, a doc, a metric. Most of the time, no one does. The insight evaporates. Vernais closes that gap structurally.
The decision doesn't stay trapped.
Tag it, and it becomes a tracked signal on the initiative: scored, classified, routed.
The author is captured.
Every chat signal remembers who said it. Accountability travels with the evidence.
It lands in the right phase.
A solution goes to Decide. A correlated observation feeds Validate. You don't file it. Vernais routes it.
One connected surface.
Chat, initiatives, investigations, and metrics live in the same graph. A message can become evidence because it never left the building.
Standalone chat is a silo with a search box. Wire is a source your initiatives can draw from.
05 · The five-phase spine
How it fits the spine.
Wire is one of the surfaces that feed the Identify → Validate → Decide → Act → Measure lifecycle. Pages and meeting transcripts feed it too. Every tagged signal is correlated, classified, and routed the same way.
a signal-born Solution in Decide
evidence that bumps a Hypothesis in Validate
stays in chat
Every hop is logged in Activity and can surface in your Inbox. The finding you reached in conversation becomes work your team executes, and a metric you watch grow.