For small research and engineering teams

ChaTEAM

Linked in.
Not locked in.

Most AI tools promise to do more work. ChaTEAM helps teams of three to ten stay aligned across separate AI spaces—without copying every conversation or asking everyone to stay online.

Separate AI workspacesOne lightweight team traceHumans choose what happens next
A natural sailboat rope tied as a figure-eight knot with painted color accents

Figure eight · Stable under load

Day · People createNight · Approved work continuesMorning · Evidence arrivesHumans decide

Built for teams of 3–10

Work together without losing the thread.

ChaTEAM turns one bounded task into a routed Human-Agent workflow without centralizing private conversations. The team returns to compact evidence and one Human-owned decision.

Deterministic fixture · Task state is the source of truth

One Task. One accountable path to handoff.

TaskVerify the bounded release handoffTASK-DEMO-PASS-001 · medium risk
completed
01 · Router

Why this team?

Selected Decision Owner (Project lead), Engineering Agent (Bounded implementer), Assurance Agent (Independent evidence reviewer) because together they cover engineering, evidence-review.

  • Decision Ownerhuman · Project lead
  • Engineering Agentagent · Bounded implementer
  • Assurance Agentagent · Independent evidence reviewer
02 · Assurance

standard review · passed

The team completed a bounded verification with evidence suitable for Human review.

  • verifiedThe bounded verification reproduced the expected behavior on the frozen fixture.
  • verifiedThe selected team covered implementation and independent evidence review.
03 · Human decision

A Human owns the handoff.

  1. Handoff approvedThe evidence is sufficient for a bounded handoff.
Recorded HandoffThe team completed a bounded verification with evidence suitable for Human review.
  1. 01task created
  2. 02team routed
  3. 03bounded run completed
  4. 04assurance completed
  5. 05human decision
  6. 06handoff saved
Team Setup · Step 01 of 03

Start with the rules your Agents must respect.

This creates a Team Charter: a shared agreement about goals, ownership, visibility, and Human authority.

01 · Shared direction

What does this team exist to move forward?

Agents may organize work around this goal. They may not silently redefine it.

After Team Setup · One Context · Four Jobs · Two Human Gates

Run work against the Charter.

The current Relay demonstration is a fixture. The next implementation step will route each run from the saved Team Charter.

Actions-inspired Context Relay

Release handoff: onboarding regression

RUN COMPLETERUN-RELAY-DEMO-001

Private source stays out of the Run. The workflow keeps only a digest, then moves approved artifacts through explicit Jobs and Human Gates.

SHA-256 d8b70466dd60294195
shareable capsule · owner

Release handoff: onboarding regression — owner approval copy

The owner submitted the supplied context for a bounded engineering and product handoff. The team receives a distilled decision surface rather than the raw conversation.

fixture · deterministic-relay-fixture-v1 · structured output
owner shareapprove

The owner approves the minimal capsule for engineering and product review.

final handoffapprove

The owner accepts the bounded reviews and creates a handoff.

CHECKED-IN FIXTURE RUN · Raw source text is not persisted · Live Jobs require explicit OpenAI opt-in in the CLI

Original Collaboration Relay

Accept. Disconnect. Review.

The original three-expert replay remains a governed workflow example. The Relay Run above is the new Actions-inspired execution model.

Interactive replayThree clear steps. One Human-owned decision.
CURRENT STEP · 01 OF 03 · DAY

Everyone accepts.

Each person chooses their own bounded work before the team disconnects.

TODAY17:30
  1. 01
    Accept0/3 people
  2. 02
    Night Loopwaiting
  3. 03
    Review0/3 experts
Before anyone disconnects

Each person chooses what can continue.

No acceptance is inferred. All three people sign off on their own proposed work.

Plocalization
Peter

Replay the frozen corrected-observation trace through the estimator outside Gym and inspect estimator state and covariance at the first divergence.

Mgym environment
Maya

Validate timestamp and coordinate-frame contracts, then compare the frozen trace inside and outside the Gym mission runtime.

Gnoise simulation
Gavin

Compare correction residuals from the frozen failing trace with the frozen tolerance contract before the estimator update.

Team progress0 of 3 people have accepted tonight’s work.

Fixture replay—not authentication · Evidence appears only after 3/3 local acceptances · Browser actions are not persisted

What this replay proves—and what it does not

The local ChaTEAM CLI persists the same acceptance, mailbox, packet-bound review, and Human-only delivery sequence. This page is a simplified checked-in replay: its Night Loop and role routing are simulated, and it is not a hosted authority service or live background worker.

chateam team-start → accept-task × 3 → Night Loop → mailbox → review × 3 → authorize

One small team · One protected workday

Create separately. Continue together.

The first layer stays simple: private creation, approved night work, an independent check, and morning Human review. Exact contracts remain available as evidence.

Human time · System continuity01 / 04
TODAY · Individual work09:00
Two researchers creating independently during the day09:00 · INDIVIDUAL WORK · YOUR CREATIVE SPACE
01 · Individual work

Your best work still begins with your own thinking.

Peter, Maya, and Gavin create in their own Codex spaces. Their unfinished ideas stay private. Only the update each person chooses to share enters the team’s night plan.

Your space · Your method · Shared by choice
02 · Night Loop I · Plan and work

One role keeps the plan. Bounded workers move the tasks.

The team approves the source, scope, budget, and stop conditions before disconnecting. A planning role keeps that shared boundary visible while finite tasks move forward.

One team plan · Bounded work · No automatic expansion
03 · Night Loop II · Independent check

A separate check challenges the answer before morning.

A distinct review role checks assumptions, scope, evidence, and integrity. Failed checks stop the loop. What returns to the team includes both the result and its limits.

Check the result · Stop on failure · Keep the limits
04 · Morning · Human review

You wake up to evidence—not another night of supervision.

Peter receives localization, Maya the environment check, and Gavin noise simulation. Everyone reviews the part they understand. The team chooses what changes next.

The right evidence · The right expert · Humans decide

Private by default · Connected by choice

The work stays visible.

Everyone keeps their own conversation and creative method. ChaTEAM shares only deliberate updates, returned evidence, and Human decisions.

P
Peter's creative spaceLOCALIZATION · PRIVATE

Conversation, sketches, drafts, and personal working style stay with Peter.

What Peter sharesone clear update
M
Maya's creative spaceGYM ENVIRONMENT · PRIVATE

Environment checks and unfinished hypotheses stay with Maya.

What Maya sharesone clear update
G
Gavin's creative spaceNOISE SIMULATION · PRIVATE

Exploration and unfinished thinking stay inside Gavin's workspace.

What Gavin sharesone clear update
SHARED BY CHOICE
SHARED BY CHOICE
SHARED BY CHOICE
ChaTEAMThe work stays visibleSHARED PROJECT VIEW
UpdateApproved workEvidenceDecisionNext step

Conversations stay local. The team sees only what each person deliberately shares.

WHILE PEOPLE ARE OFFLINEApproved work continues

Fixed source, scope, time, and stop conditions. Evidence returns by expertise.

01Your space is yours

Private chats and unfinished thinking never become team memory automatically.

02Share on purpose

One deliberate update carries the work forward without copying the whole conversation.

03Progress has proof

The shared view comes from work, evidence, and decisions—not from a model's recollection.

Self-reported · Sanitized design provenance

Built from work we actually had to coordinate.

ChaTEAM grew out of patterns tested in a one-workweek research workflow window and a separate bounded night-maintenance rehearsal. These self-reported aggregates describe our design inputs—not a live ChaTEAM deployment or an operational result.

1research-week workflow window
10completed stage summaries · one lane
7bounded night checkpoints
0authority-changing actions

SELF-REPORTED SANITIZED DESIGN PROVENANCE · NO LIVE UNATTENDED OR OPERATIONAL PERFORMANCE CLAIM

Read the counting method and claim boundary →

Simulated research fixture · No live drone or field claim

One difficult research question.

A simulated Drone Search & Rescue scenario shows one difficult question moving across three experts, two approved Night Loops, and one Human delivery decision. This is a replay—not evidence that a live flight occurred.

FLIGHT REPLAY · WEEK-2026-2901 / 06
TASK OF THE WEEK

Determine whether the localization deviation is estimator-driven or induced by the noisy simulator boundary.

OBSERVATION

Gavin observes a deviation.

Localization error rises after a noisy observation update. Root cause remains unconfirmed.

OBSERVE · DO NOT PREJUDGE
DRAG DOWN
01
SCROLL OR DRAG

Simulated research fixture. It demonstrates coordination mechanics only—not a field result, confirmed root cause, or live unattended night.

Behind the work

The morning result comes with a trail.

See who approved the work, what ran, what came back, and who decided. The exact technical proof stays one level deeper.

View the Multi-agent Work TraceActor IDs · source · budget · verifier · integrity
What happened overnight
SIMULATED FIXTURE · LOOP-DEMO-001
01
HUM-RESEARCH-LEAD

Human intent captured

Objective, maximum claim, and morning owner entered the governed Work Trace.

02
SYS-CHATEAM

Adaptive Reasoning selected

Risk and responsibility produced the lightest credible assurance floor.

03
HUM-RESEARCH-LEAD

Night Contract frozen

Source, scope, budget, quiet hours, and stop conditions became integrity-bound.

04
AGT-CODING-01

Bounded Agent run started

One registered executor began from the Human-approved source.

05
AGT-VERIFY-01

Evidence Packet ready

A distinct Verification Agent bound the result, receipts, and limitations.

06
HUM-RESEARCH-LEAD

Morning Human decision

The decision owner accepted the packet; no autonomous next cycle opened.

The right amount of review

Less process when less is enough.

Small, reversible work stays light. Shared or consequential work gets deeper checks. Human responsibility never gets lighter.

View Micro, Light, and Full checksAdaptive assurance details
01Micro

Mechanical, isolated work.

Receipts + actual diff

02Light

Bounded work with known consumers.

Targeted tests + self-check

03Full

Novel, shared, or consequential work.

Required suite + independent verification

Never reducedHuman authorityScopePrivacyFinite budgetActual evidenceStop conditions
A tactile ChaTEAM Evidence Packet box filled with postcards, emails, handoff receipts, and plan cards tied with a painted figure-eight rope

The Evidence Mailbox

Morning mail for work that continued.

Each person gets one compact paper box they can understand: what changed, what passed, what failed, and what still needs a decision.

The right evidence reaches the right person.

You sign off

Approved work continues. Human control does too.

Every night run is limited before it starts. The system cannot widen the work, copy private chats, or begin another cycle by itself.

  • 01Humans approve what continues overnight.
  • 02Private conversation stays private by default.
  • 03Agents cannot begin another cycle.
  • 04Everyone signs off before delivery.
A natural sailboat rope tied as a figure-eight knot with painted color accents

ChaTEAM

The work stays visible. Human time stays human.

Everyone keeps their creative space. Approved work can continue while the team is offline. Every consequential decision comes back to people.

Open the team mailbox