Our Software
Twin
The meeting stops waiting on a lookup.
Twin is a digital coworker. It joins meetings and calls as a colleague that has read everything in the graph, answers when asked, and remembers every decision. It speaks only when addressed, and everything it does is logged.
Half of every meeting is someone offering to check
Watch a morning meeting closely. The decisions take minutes. The delays are lookups: a set pressure nobody remembers, a drawing nobody has open, a prior decision nobody wrote down.
- “I'll check and get back to you.” The item becomes an action item. The decision waits a day for a fact the plant already has.
- “Didn't we decide this last month?” Someone did. It lives in a notebook, or in the memory of whoever was in the room.
- “Can someone pull up the sheet?” Five people wait while one person searches.
Twin sits in the meeting the way a well-read colleague does: silent until asked, and ready when asked.
The morning meeting
One question, answered while it is still on the table.
A deviation came in overnight. Here is how the item closes with Twin in the room.
The question comes up
The overnight trend looks wrong, and the discussion turns to the loop behind it. Normally this is where the item becomes an action item.
Someone asks Twin
Directly, by name, the way they would ask the engineer across the table. Twin does not interject on its own. It speaks when spoken to.
The answer lands in the chat
The trend, the sheet, the tag, the relevant document revision: posted in the thread with citations while the discussion continues. The meeting does not stop to watch a search.
The decision is logged
What was decided, by whom, and on what evidence, written to the graph. Not minutes that someone must remember to write. A record that exists because the meeting happened.
Tomorrow starts from the record
The next meeting asks what was decided and why, and gets the answer with the evidence attached. The thread never resets.
In the room, on the record
A coworker, not a console
- Joins as a colleague. Meetings and calls, on the tools the team already runs. No new screen to share, no operator to drive it.
- Answers when asked. Grounded in the graph and cited like every other answer on the platform. When it cannot verify, it says so, in front of everyone.
- Speaks only when addressed. Twin holds the discipline of a good junior engineer in a senior meeting: present, prepared, and quiet until called on.
- Remembers every decision. Decisions, owners, and reasoning are kept on the same graph the rest of the platform reads. What Twin remembers, Maven can answer.
Maven, the expert on the graph KC feeds the memory Marshal executes what was decided