Connector Twin: a business plan and a working replay

A business plan, with a working replay

Published on sgit.ai for somebody else to build. The session below is invented; the Gmail and Calendar behaviour it relies on is documented by Google and cited in the plan.

Replay the session Read the business

The sales question

An agent with a Gmail or Calendar connector can read, send, move, decline and delete on somebody's behalf. The table is what an organisation can answer about that agent, without a twin of the connector and with one.

Question	Without a twin	With a twin

The replay

One agent session, rebuilt from its journal

A scheduling assistant was given a Gmail and a Google Calendar connector and one instruction. Every call it made was captured as an entry, request and response, into an append-only journal. Drag the slider: the inbox and the calendar below are rebuilt from those entries alone, showing what the agent saw and changed up to that step. Nothing here is a copy of the mailbox.

The instruction, captured

What the agent said it did

Explainability

What the agent said, against what the journal shows

The agent's summary is accurate as far as it goes. The journal is what turns it into something a person can check, and in two places it changes the meaning.

The summary said	The journal shows	Can it be put back?

The business

What you sell, and to whom

A service that gives every agent deployment a twin of its connectors: capture, retention, the rebuilt views, and a revert plan. Sold with one question, do you know what your agents did?, and one fact: for several of the actions a connector allows, the platform keeps no way back.

Set-up, once

Monthly, per agent

On demand

Where the capture runs

Mode	Where	Evidence	Trade-off

The numbers, as a calculator

Customers Agents per customer Tier Average set-up per new customer Monthly burn

monthly recurring revenue

annual run rate

set-up revenue from these customers

infrastructure a month, at £3.10 per agent

gross margin on infrastructure

agents to cover the burn

Assumptions, not measurements.

How it is built

Five steps, and only the fourth is new work

CaptureRequest and response for every connector call, and the instruction behind it when prompt capture is on. The authorisation header is never captured.

AppendEach entry goes to a vault append lane: write-only, blind to the sender, and not processed on the hot path, so capture costs the agent almost nothing.

ChainEach entry carries the hash of the one before it, so a missing or edited entry is visible to anyone who holds the read key.

ProcessA scheduled reader moves entries from pending to processed and folds them into views. When and how often it runs is the open design question.

Replay and revertA vault app, like this one, rebuilds what the agent saw, shows before and after, and writes the revert plan. Executing it is a separate, approved step.

The capture format, the processor and the revert rules are specified in spec/ and prototypes/. The replay above is the reference implementation of step five, running on the invented journal in journal/.

In this vault

Everything needed to start

Path	What it is
`plan/00-START-HERE.md` to `plan/10-open-questions.md`	The plan as documents: the idea, the facts, the architecture, the service, pricing, the business model, go-to-market, the first ninety days, investors, risks, and what is still open.
`spec/journal-entry.md`	The entry format: the contract between whatever captures and whatever replays.
`spec/revert-rules.md`	Every Gmail and Calendar action in scope, what the platform keeps, and the inverse the twin can offer.
`prototypes/`	The agent-reported capture instruction, the broker design, and the processor schedule, enough to run the first customer.
`journal/`	The invented session: 17 hash-chained entries and the captured instruction.
`diagrams/`	The pipeline and the three capture modes, as SVG and WebP.
`tools/`	The journal generator, the chain verifier and the content builder.

Connector Twin is published on sgit.ai under the same terms as the code behind it: take it, run it, change it. Every person, company and address in the session is invented and uses the reserved .example domain. See PUBLIC.md.