Same context.
Every member, human or AI, works from the visible room thread: conversation, artifacts, decisions, sources, and open questions. Nothing important has to happen in a side window.
Shared room model · Human authority stays visible
Everyone in. The right context in reach.
A room.
where work participatesA
ArcherResearchdrafting launch angles3 sources · pending PriyaP
PriyaProductreviewing v1approval requestedF
ForgeEngineeringstaging issue #8472 files · ready for reviewD
DevonDesignmarking up framesin the roomL
LedgerRecordsrecording receipt 3f7adraft.create · pendingK
KaiAccount execforwarding customer SMSinto the roomM
MuseWriterdrafting Q4 narrativein Sarah's voiceS
SarahFoundersetting the launch tonebrief in flightEmail · async replies
Slack · channel messages
GitHub · code & PRs
Files · shared docs
SMS · texts
Voice · phone calls
Calendar · meetings
Browser · web access
Sociail puts people, named AI teammates, shared context, approvals, artifacts, and receipts into one reviewable workspace. The team stays in the room. The work gains memory, hands, and boundaries.
Room anatomy
Native page
One model, not a stitched mockup.
The room is the unit of work.
The visual above is intentionally dense because a real room has people, AI teammates, source context, decisions, and prepared work moving together. This page keeps the model simple: shared room first, scoped reach second, human authority always visible.
Bounded reach.
Approved channels and tools can come into reach, but they do not become a free-for-all. The room stages work, asks for review, and keeps scope visible.
Every receipt.
Consequential work should leave a record of what happened, under whose authority, with what source context, and what approval state. Trust the receipt, not the model.
Members
Human + AI
Two kinds of members. Same room.
Teammates are named, scoped, and visible.
Named people keep authority.
Founders, operators, product owners, engineers, designers, and customer-facing teammates stay visible as owners, reviewers, and decision makers.
Named agents do bounded jobs.
Archer brings context into focus. Forge stages implementation work. Muse shapes the message. Ledger keeps the record straight.
Hands
Bounded action
The trait that reaches.
Hands move work forward without overstepping.
A teammate earns capability in layers: context, role, memory, action, and follow-through. Hands are the action layer: useful because they can prepare work, safer because they stop at the review boundary.
Prepare
Drafts, summaries, tickets, briefs, and scoped tool calls can be prepared before anything consequential ships.
Request
The owning human is asked for approval in the room. The request is visible to the team, not buried in a side DM.
Record
The receipt records actor, authority, scope, source context, and approval state so the team can review it later.
Scope
Approval-aware
The room reaches outward carefully.
Context in reach. Not everything on autopilot.
The room can bring approved context and tools close to the work, but the trust posture is deliberately conservative. It should make authority easier to inspect, not easier to blur.
A Sociail room is not a promise of unbounded automation. It is a promise of visible context, prepared work, review points, and receipts the team can understand later.
Not ambient surveillance
Not automatic authority
Not hidden tool use
Not model confidence replacing human review
See the room in motion
Walk through real workflow paths.
Request-led Early Access
Put AI in the room with your team.
Sociail is onboarding small teams where one focused room can prove value with shared context, visible approvals, and useful follow-through.