LiquidSilicon opens on a briefing, not a dashboard. It greets you, counts what needs you, and deals your live business one card at a time — each carrying why it surfaced, when it’s due, and how it’s asking you to answer. Reply in a tap or just talk back. When a card is a problem, an agent drafts the fix and shows you the diff — and applies nothing until you confirm. Every decision files itself to a status board and a history you can audit.
a briefing, dealt card by card — not a wall of alerts
the grammar every item carries, so you decide from the card
one-tap decisions, or barge-in voice that listens
agents draft fixes; nothing applies without your yes
The console opens with a spoken “Good morning — three items need your attention,” then starts dealing. One card holds the center; you handle it; the next deals in. The queue tells you how many remain, never all at once. Everything that doesn’t need you is triaged in the background — and if nothing is urgent, the briefing says “all clear” and steps aside.
The point is your attention, not your engagement. A briefing is a short list of decisions, not a feed to scroll. When it’s done, you’re done — there is nothing left to go check.
Each card is narrated as it lands and settles with a spring — the shipped console motion, not a mock. You can turn narration off entirely and read; the flow is identical.
A briefing card is not a headline you have to go investigate. It carries its own reasoning in three terse lines, so a decision can be made from the card itself.
WHY — One line of provenance — the reason it surfaced now. No alert ever arrives without telling you what tripped it.
“5 denials is 4× your daily baseline.”
WHEN — The temporal context from real timestamps — recency plus any hard deadline, pulled out as its own element rather than buried in prose.
“Detected 07:42 · ongoing.” “Due Aug 1.”
STYLE — How the card is asking you to respond, stated up front — so you know the kind of answer it wants before you read the detail.
DECIDE · APPROVE · REVIEW
You get a briefing card and two honest ways to respond — your voice, or a single tap that moves the real record.
The briefing narrates itself, and the moment you start speaking it stops and listens. A live transcript fills in as you talk; your reply routes straight into the conversation. No wake word, no waiting for it to finish — you interrupt it the way you would a person. Where a browser can’t do speech, the mic simply isn’t offered.
The buttons on a card are honest. Approve approves; Advance moves a lead a pipeline stage; Send sends — each on the actual record, and it tells you what it did (“Approved.” “Sent.”). A button that only opens a record to read says so, and leaves the item in your queue unhandled. No button pretends.
When a card is a problem — a spike in denials, a broken access policy — it can hold its own solution. The Builder drafts the actual change and renders it as a readable before → after diff with a risk note. You confirm & apply, or reject. Nothing is applied without your explicit confirm, and every apply writes a receipt.
Propose → confirm → receipt. The receipt is an attributed, timestamped record of exactly what was applied — part of the same append-only history everything else files into.
Never silently auto-applied — and we say so plainly, because the honesty is the product. An assistant that drafts fast but applies only on your yes is one you can actually leave running.
The desk reads like a real workspace, not one undifferentiated “handled” pile. Records you act on move across a live status board; the decision itself files into a history you can fan open and audit.
A spatial status board. Record-bearing items move New → In Progress → Done off to the side. Advance a deal and its card flies to In Progress; approve a payment and it lands in Done. You can see the state of the operation at a glance.
A macOS-style history. Every decision animates into a fan stack in the corner — filed by when you decided and what you chose. The console is its own record, so an answer is never lost.
There is no single, opaque “AI.” Five narrow agents each do one honest job — one watches, one ranks, one drafts, one guards, one learns — and the two that could change anything, Builder and Guardian, are the two you have the most control over.
Start with the agents drafting and you confirming everything. Autonomy is a dial, not a switch — five tiers, set per class of change. Agents earn the next tier by getting the last one right, and you decide when to grant it.
Agents watch and report. Nothing acts.
Ranked, costed recommendations. Still no changes made.
Change classes you approved run on their own — Guardian still watching.
Autonomy widens to adjacent decisions in the same class.
The agent owns that workflow end to end, every action still logged.
Grant autonomy one phase at a time, per change class — and pull it all the way back to observe-only in a single click, with no redeployment and no downtime. Guardian keeps its veto at every tier, so raising the dial never removes the safety screen.
Before the first briefing, you tell LiquidSilicon what your operation actually is — the entities, the relationships, the rules — in plain language. From that it generates your config-driven runtime: the data model, the workflows, the screens, and the knowledge graph the agents reason over. No schema to hand-author, no rebuild to sit through. Change the description and the runtime reshapes to match.
The briefing is the surface. Underneath sit three things — an event-sourced core, a knowledge graph, and a config-driven runtime — each boring on purpose: auditable, replayable, inspectable. It’s also why the console evolves with your business instead of being torn out and replaced every few years.
Every decision you make in the briefing is an append, never an overwrite. Any past state is replayable and every action carries its own audit trail — which is why the filed history is the real record, not a summary.
Your operation described as entities and relationships the agents reason over — not opaque tables they blindly mutate. The graph is the shared truth every briefing is drawn from.
Each tenant’s software is generated from their own description of the business. Change the description and the runtime reshapes — no rebuild, no migration project. The console fits the operation instead of forcing the operation to fit the product.
You get a briefing; IT gets a control plane. The same decision travels one path — an item you answer in the Business Console becomes a proposal an agent makes, which an IT reviewer approves in the Control Plane before it ships. Two audiences, two screens, one loop.
These are faithful recreations of the console.
Your agents
Morning briefing · 3 items
Review AI-generated suggestions
It greets you and tells you how many items need you — spoken aloud if you want, read if you don’t — then deals them one at a time. Each card carries why it surfaced, when it’s due, and how it’s asking you to respond, so you can decide from the card itself.
You answer in a tap or by talking back, the card files itself to a history and status board, and the next one deals in. When nothing is urgent, it says “all clear” and gets out of your way.
By default, no. When a card holds a fix, an agent drafts it and shows you a readable before → after diff with a risk note — but nothing is applied until you confirm. When you do, you get a receipt: an attributed, timestamped record of exactly what happened.
You set an autonomy tier per class of change; only the classes you deliberately raise run on their own, and even then, when Guardian scanning is enabled, it screens each one and can veto it. You can pull the whole system back to observe-only in a single click.
No. Voice is an option, not a requirement. The briefing narrates itself and listens if you speak — start talking and it pauses, fills in a live transcript, and routes your reply into the conversation. Every card is equally answerable with a single tap.
Voice degrades gracefully: where a browser can’t do speech recognition, the mic simply isn’t offered and nothing else changes.
LiquidSilicon is bring-your-own-key first. Connect a key from Anthropic, OpenAI, Google, DeepSeek, or Mistral and every agent call runs under your own provider account — your prompts and data are governed by the agreement you already hold with that provider, not by us.
If you would rather not wire up a key on day one, you can start on a capped starter allowance we provide and switch to your own key whenever you like. Either way, you always see exactly what each agent spends.
Point LiquidSilicon at your operation and let the work find you — the few decisions that actually need you, each ready to answer in a tap or a sentence, with the agents drafting and you confirming.
Free tier · Humans confirm every change