Skip to content

Part 3 · Operate

Live answers

Answers drawn as parts of the product: channel cards, charts, deals, approvals and checklists, with every number opening its rows.

01What it is

A fixed set of components an answer can be drawn from, the read-only data tools that fill them, and the buttons they may carry. A number in an answer always comes from a data tool, and a button always runs through the same approvals and state machines as the screen it belongs to.

02Why it exists

An answer written as a paragraph asks you to trust it and then go and find the thing it talks about. An answer drawn as the channel card, the chart or the draft itself can be checked where it stands and acted on in place.

That only holds if the parts are honest. So nothing in an answer is free text with numbers in it: the components take ids, the server reads the data, and every object it returns says which rows it came from and which actions it allows right now. A button the data did not allow is not drawn, and a click is checked again on the server before anything runs.

Changes are never made on your behalf. A new angle or a longer test is written as a proposal you accept or decline with the team's own; pausing a channel, approving a send and buying credits each ask you to confirm first.

03How to use it

  1. 01Live answers wait behind the intelligent_ui flag. Once it is on for your account, open Settings, Live answers, and turn them on for the venture.
  2. 02Every number carries the rows it came from: press See the evidence, or Evidence under a report line, and the rows open in a sheet beside it, read from your venture only.
  3. 03With live answers on, the weekly report, Approvals and the plan rail are drawn from the same parts, straight from your data with no model: the report as numbers, a chart, channel cards and a checklist you clear in place; each draft as an approval card. Your GTM Plan is drawn from these parts for everyone with the team on, live answers or not: a timeline, and a slider that shows what a change would do before you save it.
  4. 04Press a button on a card to act on that item. Opening a channel or a deal is a link; pausing, approving and buying ask you to confirm.
  5. 05Propose a new angle or more days from a channel card, then accept or decline the proposal on the team screen with the others.
  6. 06Correct what we know from a memory item: it opens the memory prompt with the words filled in, and nothing changes until you send and confirm them.

04What good looks like

You give it
Pause the channel, pressed on a running channel’s card, then confirmed.
You get
The first press returns a confirmation asking you to confirm, and the channel is still running. Confirmed, the channel moves to paused through the same move the team screen makes, and the audit log records ui.pause_lane with the answer it came from.
Why
pause_lane declares a confirmation and runs the existing pause action, which checks the move against the channel state machine.

Derived from the rules in the code

05What weak looks like, and what it costs

You give it
An answer asks for website numbers on a venture with analytics off.
You get
The tool returns that website analytics are not on for this venture, and no numbers.
Why
A tool for a feature that is off says so and returns nothing else, so an answer can never fill the gap with a guess or another venture’s data.

Derived from the rules in the code

06Read next