Asking Sera Well: Search by Meaning, Charts, and Receipts

Sera is not a search box that needs the right keyword. She reads meaning, she can draw what she finds, and she can always show you where an answer came from. Knowing those three things changes how much you get out of a question.

Search finds meaning, not matching words

Every record in the hub carries an embedding: a mathematical representation of what it is about. When you ask a question, Sera compares the meaning of your question against the meaning of the records, so a match does not depend on using the same words.

In practice:

• "Who is worried about money?" finds a risk written as "cash flow concern for Q3."
• "What did we agree with the neighbors?" finds a decision recorded as "boundary agreement with the adjacent lot."
• "Anything about water?" finds well permits, ASADA letters, and irrigation tasks together.

Two things follow. First, ask in ordinary language rather than guessing at the exact wording of the record. Second, this search is scoped to your organization only. It cannot reach another client's records, and it does not touch the web.

Ask for a chart when the answer is a shape

When a question is about magnitudes, a breakdown, a trend, or a schedule, a chart reads faster than a paragraph of figures. Just ask for one in plain language, and it appears inline in the conversation.

• Donut for a breakdown of a whole with a total in the middle. "Show me open tasks by status as a donut."
• Bar for ranked or compared magnitudes. "Chart spend by project."
• Line for a value moving over time, one line or several. "Chart our volunteer hours over the last six months."
• Timeline for a project schedule, Gantt style, with dated tasks and optional milestones and dependencies. "Draw the timeline for the Rancho project."

Two boundaries are worth knowing, because they are what makes a chart trustworthy. Every value in a chart comes from records Sera actually retrieved to answer that question, never from a number she is recalling or estimating. And charts visualize hub data only: ask for a logo or an illustration and she will say plainly that this is not what the tool is for.

If a chart would need hundreds of rows, narrow the question instead. "Spend by project this quarter" produces a readable chart; "every line item ever" does not.

Ask for the receipts

Statements carry their provenance: the source, the date of that source, who asserted it, and how confident the extraction was. So the follow-up question is always fair and always answerable:

• "Where does that come from?"
• "Which meeting was that decided in?"
• "How confident is that number?"

If Sera does not have a source for something, she says so rather than dressing an inference up as a fact. An answer with no record behind it is reported as unknown.

Ask what changed

Notion shows a record's current values. Its past is invisible in the interface, which is why "was this always due in March?" is such a hard question to answer by hand. Sera can read the record's change history:

• "When did this due date move, and who moved it?"
• "Was this decision always marked Confirmed?"
• "Has the owner of this task changed?"

If no change has been logged, she says exactly that. That is not the same as proof the record never changed, and she will not present it as stability.

---

The habit

Ask the way you would ask a colleague who has read everything: in your own words, one question at a time, and follow up. "What is blocked?" then "chart that by project" then "where did the second one come from?" is a two-minute conversation that would take an afternoon by hand.

Key points

Search is semantic: every record is embedded so a question finds records that mean the same thing even when no word matches, and search is scoped to your own organization only. Ask for a chart when the answer is comparative or over time: donut for a breakdown of a whole, bar for ranked magnitudes, line for a trend, timeline for a project schedule with dated tasks. Charts render inline in the conversation and are drawn only from records retrieved for that answer, never from estimates; Sera will decline to draw logos or illustrations because charts visualize hub data, not artwork. Every statement carries provenance, so "where does that come from?" always has an answer, and "when did this change?" reads the record history that Notion itself does not show. Ask narrower questions rather than asking for hundreds of rows, and phrase questions as a person would rather than as a database query.