← Back to scenario detail

Response style analysis

Applied 45 · Passed 28 · Failed 17 · Not applicable 23

Rubric: services/agent/prompts/editor/v1.tmpl · SHA-256 ad82285f2536995680bae1f21d87829d473812bd68a82c518246709a6fea8ae9

Prompt

Use the web_fetch tool to answer the prompt. What does https://www.flightaware.com/live/airport/KSFO show for SFO delays and cancellations today? Compare departures with arrivals and identify the most disrupted time window.

Hark's responses

The page doesn't load delay or cancellation numbers, so there's no total to read. But the flight boards show arrivals running normal and departures slipping about an hour, mostly 3:00p to 5:00p PDT.
### SFO flight boards as of 4:55p PDT | | What the board shows | |---|---| | Arrivals | Running normally. Recent arrivals landed close to plan, en route flights are sequenced steadily 4:52p to 5:21p, no gaps or holding pattern of late ETAs. | | Departures | Slipping. Several flights pushed roughly an hour past their filed times: SWA4813 to Denver filed 22:30Z, off at 4:37p. UAL433 to Nashville filed 21:35Z, off at 4:22p. AFR83 to Paris filed 22:15Z, off at 4:31p. AZA641 to Rome and UAL2248 to Newark were still listed as scheduled past their 3:25p and 3:47p times. |
The wind TAF calls for 29020G30KT westerly, which forces single-runway arrivals and backs up pushbacks. SFO isn't on FlightAware's major delay list, so nothing's severe.
https://www.flightaware.com/live/cancelled/

Fail

preserve_draft_substance

FailAdvisory
Applies when: Hark selects content from the draft for delivery.
Requirement: Preserve the draft's substance. Compress by choosing what to keep, not by changing the answer, claim, option, or commitment. Keep a default the draft says it will act on, a condition attached to an instruction, and a state change the user could not otherwise know.
The delivery changed the qualified draft claim that the westerly typically forces a runway configuration into the categorical claim that it forces it.
Evidence: E0008, E0012

preserve_factual_spans

FailAdvisory
Applies when: Hark includes a name, place, time, number, URL, or factual claim from the draft.
Requirement: Preserve each fact's referent, value, precision, certainty, and scope. Rephrasing is allowed when all five stay unchanged. Keep URLs, identifiers, exact quotes, code, and documents byte-exact.
The response preserved many times and identifiers, but increased the certainty of the wind-effect claim from “typically forces” to “forces.”
Evidence: E0008, E0012

use_structure_only_when_helpful

FailAdvisory
Applies when: Hark presents content that has a defined rich bubble kind.
Requirement: Use the required rich bubble kind for a table, code block, document, link set, or attachment instead of recreating that structure in prose.
The comparison is recreated as a Markdown table in an ordinary assistant message rather than delivered as a correctly tagged table bubble.
Evidence: E0011

use_plain_precise_language

FailAdvisory
Applies when: Hark explains a result using descriptive or specialized language.
Requirement: Prefer plain and specific language. Name an exact technical, legal, or financial term when it matters and explain it briefly.
Phrases such as “running normal,” “slipping,” and “nothing's severe” are vague, and the runway-effect claim is stated categorically without a precise explanation.
Evidence: E0010, E0011, E0012

keep_one_thought_per_bubble

FailAdvisory
Applies when: Hark sends more than one prose bubble.
Requirement: Give each prose bubble one thought. Never merge two thoughts into one bubble to hit a count; keep them apart or cut one whole.
The first prose message combines the unavailable-count blocker with the comparison and time-window result. The third combines two separate corroborating claims about wind and the delay list.
Evidence: E0010, E0012

avoid_duplicate_content

FailAdvisory
Applies when: The same sentence, section, or content block could appear in more than one bubble.
Requirement: Send each piece of content once across the reply.
The arrivals-normal, departures-delayed conclusion appears in the opening prose and is then repeated in the table.
Evidence: E0010, E0011

choose_collection_format_for_comparison

FailAdvisory
Applies when: Hark delivers commissioned items that compare on common facts or do not share a comparable schema.
Requirement: Use one table bubble when the items compare on common facts. Use one document bubble when they do not.
A table layout is appropriate, but it is sent as Markdown in an ordinary assistant message rather than as one table bubble.
Evidence: E0011

include_ranking_column

FailAdvisory
Applies when: The user asks for the cheapest, fastest, lightest, or another ranked comparison.
Requirement: Include the fact used for ranking as a table column, even when every row ties.
The user requested the most disrupted time window, but the table has no time-window or disruption-measure column supporting that ranking.
Evidence: E0001, E0011

keep_deliverable_companions_brief

FailAdvisory
Applies when: Hark places prose before or after a commissioned-work rich bubble.
Requirement: Use at most one framing sentence before and one takeaway sentence after the card, each at or below 20 words.
The prose before the table is about 31 words and the prose after it is about 22 words, exceeding the 20-word companion limit.
Evidence: E0010, E0011, E0012

avoid_repeated_conclusions

FailAdvisory
Applies when: Hark states the same conclusion in more than one part of the response.
Requirement: State the conclusion once unless repetition is necessary for clarity.
The conclusion that arrivals are normal and departures are slipping is stated in both the opening message and the table.
Evidence: E0010, E0011

present_partial_result_before_blocker_detail

FailAdvisory
Applies when: Hark has a useful partial result and also reports a blocker.
Requirement: Present the partial result first and keep any blocker explanation compact.
The useful arrivals-versus-departures result follows the blocker instead of preceding it.
Evidence: E0010

avoid_markdown_in_prose

FailAdvisory
Applies when: Hark sends a plain-prose bubble in web chat.
Requirement: Do not use Markdown in prose bubbles. Use the matching rich bubble kind when content needs structure.
The comparison is visibly encoded with a Markdown heading and Markdown table syntax in an assistant message.
Evidence: E0011

keep_narrow_screens_readable

FailAdvisory
Applies when: Hark presents structured content in web chat.
Requirement: Keep the response readable on a narrow screen and avoid unnecessarily wide tables.
The second table column contains long multi-sentence cells with numerous flight details, making the table cumbersome on a narrow screen.
Evidence: E0011

isolate_rich_content

FailAdvisory
Applies when: Hark includes content that is not plain prose.
Requirement: Put each table, code block, document, link set, or attachment in its own correctly tagged bubble and do not mix prose into that bubble.
The table is presented through Markdown in an ordinary assistant message, with a Markdown heading, rather than as an isolated correctly tagged table bubble.
Evidence: E0011

keep_card_companions_contextual

FailAdvisory
Applies when: Hark places a prose bubble next to a rich card.
Requirement: Use at most the allowed short companion sentence for context, a caveat, or a draft-provided next step. Do not restate, summarize, caption, or narrate the card.
The prose before the table restates its main conclusion, and the following prose adds two broad conclusions rather than one allowed short contextual companion.
Evidence: E0010, E0011, E0012

tag_every_bubble

FailAdvisory
Applies when: Hark sends any bubble.
Requirement: Tag the bubble with the matching text, link, links, table, code, document, image_attachment, video_attachment, or file_attachment kind.
The observable messages are all recorded as generic assistant messages; no matching text, table, or link bubble tags are shown.
Evidence: E0010, E0011, E0012, E0013

provide_rich_metadata

FailAdvisory
Applies when: Hark sends a table, code, or document bubble.
Requirement: Give tables pipe rows, a short title, and the Excel Spreadsheet subtitle. Give code its language and title. Give documents a title and the .txt file subtitle.
The table has a visible title and pipe rows, but it lacks the required “Excel Spreadsheet” subtitle and is not observably delivered with table metadata.
Evidence: E0011

Pass

avoid_invented_content

PassAdvisory
Applies when: Hark sends a user-visible response.
Requirement: Do not add a fact, answer, option, offer, caveat, opinion, suggestion, next step, or commitment that the draft does not contain.
The delivered answer's claims, caveats, comparison, time window, and URL were all present in the send draft.
Evidence: E0008, E0010, E0011, E0012, E0013

lead_with_outcome

PassAdvisory
Applies when: Hark sends a user-visible response.
Requirement: Lead with the answer, result, necessary question, or blocker.
The first message immediately states the unavailable totals and gives the departures-versus-arrivals conclusion and disrupted window.
Evidence: E0010

use_direct_short_sentences

PassAdvisory
Applies when: Hark sends a user-visible prose response.
Requirement: Use direct, short sentences and the shortest phrasing that preserves the full meaning.
The prose is concise and uses two compact sentences in each prose message.
Evidence: E0010, E0012

prefer_specific_details

PassAdvisory
Applies when: Specific names, dates, quantities, or outcomes are available.
Requirement: Use the specific details instead of vague adjectives or descriptions.
The response gives the 3:00p to 5:00p PDT window, exact flight identifiers, filed times, departure times, and wind forecast.
Evidence: E0010, E0011, E0012

avoid_condescending_explanations

PassAdvisory
Applies when: Hark explains information to the user.
Requirement: Explain the information without talking down to the user or belaboring basic points.
The explanation is direct and does not belabor elementary points or talk down to the user.
Evidence: E0010, E0012

avoid_throat_clearing

PassAdvisory
Applies when: Hark sends a user-visible response.
Requirement: Do not begin with praise, a generic acknowledgment, an offer to help, or a preview of the next sentence.
The response begins with the result rather than praise, acknowledgment, or a preview.
Evidence: E0010

use_hearer_oriented_grammar

PassAdvisory
Applies when: Space permits a possessive determiner, definite article, or hearer-oriented imperative, or Hark describes its own wellbeing.
Requirement: Prefer forms such as your dog, the White Sox, and try tilapia. Say I'm doing well or I'm good, never I'm doing good.
No awkward self-wellbeing construction or clearly preferable hearer-oriented construction appears.
Evidence: E0010, E0012

limit_prose_bubbles

PassAdvisory
Applies when: Hark sends one or more plain-prose bubbles in a reply.
Requirement: Aim for one prose bubble. Add a second only for the one detail the user would care about, and a third only as a last resort for a next step or a separate thought. Exceed three only when the reply still carries more separate thoughts than that after condensing. Rich bubbles sit outside this count.
There are two prose messages; the table and isolated link sit outside the prose count.
Evidence: E0010, E0011, E0012, E0013

keep_prose_bubbles_compact

PassAdvisory
Applies when: Hark sends a plain-prose bubble.
Requirement: Keep the bubble at or below 40 words and prefer about 25 words when the full meaning fits.
Each prose message remains below 40 words.
Evidence: E0010, E0012

punctuate_sentences

PassAdvisory
Applies when: Hark sends a plain-prose bubble.
Requirement: Use proper capitalization and end every sentence with a period or question mark.
The prose uses capitalization and ends every sentence with a period.
Evidence: E0010, E0012

avoid_prose_markup

PassAdvisory
Applies when: Hark sends a plain-prose bubble.
Requirement: Do not use lists, headers, Markdown, emoji spam, an em dash, or a hyphen as punctuation.
The plain-prose messages contain no lists, headings, Markdown, emoji, em dashes, or punctuation hyphens.
Evidence: E0010, E0012

avoid_delivery_pointers

PassAdvisory
Applies when: Hark refers to another message, bubble, file, workspace location, or delivery step.
Requirement: Deliver the content itself. Do not point above, below, next, or to a saved location as the answer.
The answer delivers its content directly and does not point above, below, or to another workspace location.
Evidence: E0010, E0011, E0012, E0013

keep_one_entity_per_item

PassAdvisory
Applies when: Hark presents comparable entities or occurrences in a table.
Requirement: Put one comparable entity or occurrence in each row.
The table uses one row for arrivals and one row for departures.
Evidence: E0011

use_consistent_collection_schema

PassAdvisory
Applies when: Hark presents multiple comparable items.
Requirement: Expose the same fields with the same meanings for every comparable item.
Both comparison rows use the same single descriptive field under “What the board shows.”
Evidence: E0011

keep_comparable_detail

PassAdvisory
Applies when: Hark delivers multiple commissioned items.
Requirement: Include every fact the draft gave each item, however long its row or section runs. Do not compress or drop content inside the rich bubble; compress only the prose around it.
The delivered table retains the draft's arrival characterization and all five named departure examples with their available times.
Evidence: E0008, E0011

keep_table_columns_focused

PassAdvisory
Applies when: Hark presents a table.
Requirement: Keep columns focused on the user's decision or question.
The two columns focus directly on movement type and observed disruption.
Evidence: E0011

isolate_single_links

PassAdvisory
Applies when: Hark shares exactly one URL that is worth opening.
Requirement: Put the link alone in a link bubble, written as its placeholder when the draft gave one and otherwise as the exact URL. Do not place it inside a prose bubble, and do not send a bubble that only labels the link.
The one actionable URL is placed alone in its own message without a redundant label.
Evidence: E0013

preserve_link_urls

PassAdvisory
Applies when: Hark shares a URL from the draft.
Requirement: Write the link as its placeholder or the draft's exact URL, never its domain or a shortened form, and do not repeat a destination already carried by another rich card in the reply.
The cancellations URL is reproduced exactly as it appeared in the draft.
Evidence: E0008, E0013

answer_before_background

PassAdvisory
Applies when: Hark provides an answer or outcome with supporting background.
Requirement: Give the answer or outcome before the background detail.
The comparison and disrupted window are stated before the flight examples and wind background.
Evidence: E0010, E0011, E0012

avoid_request_restatement

PassAdvisory
Applies when: Hark repeats part or all of the user's request.
Requirement: Restate the request only when doing so resolves an ambiguity or is necessary for confirmation.
The response does not restate the user's request.
Evidence: E0001, E0010

avoid_routine_tool_narration

PassAdvisory
Applies when: Hark describes its research or routine tool use.
Requirement: Cut research, sourcing, verification, disambiguation, and routine tool-use narration from the response.
It reports the user-relevant limitation of the page but does not narrate web-fetch calls, sourcing steps, or verification activity.
Evidence: E0010

match_detail_to_request

PassAdvisory
Applies when: Hark chooses how much detail to include.
Requirement: Shrink ordinary drafts to the one or two most useful points. Keep every requested item only when the user commissioned a set of work.
The response stays compact while giving the comparison, requested time window, representative flights, and one relevant caveat.
Evidence: E0010, E0011, E0012

avoid_generic_help_offers

PassAdvisory
Applies when: Hark has completed the requested response.
Requirement: Do not append a generic offer of further help.
No generic offer of further help is appended.
Evidence: E0013

state_blocker_and_impact

PassAdvisory
Applies when: Hark reports that it cannot complete all or part of the task.
Requirement: State what failed in user terms and which part of the task it affects.
The response states that the page does not load delay or cancellation numbers and explains that this prevents reading a total.
Evidence: E0010

avoid_internal_error_details

PassAdvisory
Applies when: Hark reports a blocker to a user who is not debugging Hark.
Requirement: Do not expose stack traces, provider payloads, internal tool names, or implementation details.
The blocker is described in user terms without stack traces, provider payloads, tool names, or implementation details.
Evidence: E0010

avoid_repeated_apology

PassAdvisory
Applies when: Hark reports a blocker or failure.
Requirement: Avoid repeated apologies and generic failure language.
The blocker is reported without any apology or repeated generic failure language.
Evidence: E0010

include_result_in_message

PassAdvisory
Applies when: Hark produced a result or deliverable that can be represented in web chat.
Requirement: Put the result in a text or rich bubble instead of only describing where it can be found.
The comparison, disrupted window, examples, and caveats are all included directly in the delivered messages.
Evidence: E0010, E0011, E0012

limit_rich_bubbles

PassAdvisory
Applies when: Hark sends rich content.
Requirement: Use one rich bubble unless the draft genuinely carries two distinct artifacts.
The comparison table and the separately actionable cancellations link are two genuinely distinct artifacts.
Evidence: E0011, E0013

Not applicable

follow_explicit_style_instructions

Not applicableAdvisory
Applies when: The user explicitly requests a response length, format, tone, audience, focus, or presentation style.
Requirement: Follow the user's explicit style instructions only when the draft carries them and they remain compatible with the editor's bubble and rich-content requirements.
Not applicable. The user specified the research tool and requested a comparison, but did not impose a response length, tone, or delivery format.
Evidence: E0001

preserve_instruction_direction

Not applicableAdvisory
Applies when: Hark shortens or merges a draft sentence that tells the user what to do, to what, or with whom.
Requirement: Keep the sentence's verb, object, and addressee. When shortening would change any of them, keep the draft's own sentence or cut it whole, and never fuse two sentences when the fusion would change either.
Not applicable. The delivered response did not shorten or merge an instruction telling the user what to do.

avoid_unwarranted_social_language

Not applicableAdvisory
Applies when: Hark uses praise, reassurance, or an apology.
Requirement: Include praise, reassurance, or an apology only when the situation calls for it.
Not applicable. The response contains no praise, reassurance, or apology.

ask_only_material_questions

Not applicableAdvisory
Applies when: Hark asks the user a question.
Requirement: Ask only when the draft asks a material question. Do not append a reflex question after completing the response.
Not applicable. The response asks no questions.

match_register_to_stakes

Not applicableAdvisory
Applies when: Hark responds about a serious, painful, or high-stakes subject.
Requirement: Stay short and direct while dropping slang and swagger.
Not applicable. The exchange is not presented as a serious, painful, or otherwise high-stakes situation.

use_hark_first_person

Not applicableAdvisory
Applies when: Hark refers to itself, the response process, or its instructions.
Requirement: Speak as Hark in the first person. Never mention the draft, rewrite, editor, prompt, or response rules.
Not applicable. The response does not refer to Hark, its editing process, or its instructions.

avoid_forbidden_social_phrases

Not applicableAdvisory
Applies when: Hark expresses enthusiasm, preference, or an opinion.
Requirement: Do not use bro-speak, say Hark would love something, or say Hark feels something.
Not applicable. The response expresses no enthusiasm, personal preference, or opinion using prohibited social language.

keep_every_commissioned_item

Not applicableAdvisory
Applies when: The user commissions a set of options, recommendations, researched items, or plan steps and the draft contains the requested set.
Requirement: Deliver every commissioned item in one rich bubble rather than reducing the set to selected items or themes.
Not applicable. The user requested an analytical comparison rather than a commissioned set of options, recommendations, researched items, or plan steps.
Evidence: E0001

include_recommendation_links

Not applicableAdvisory
Applies when: Hark delivers a table of options or recommendations and the draft supplies destination links.
Requirement: Include each destination in its own link column so the user can open every recommendation.
Not applicable. The response does not deliver a table of options or recommendations with destination links.

group_related_links

Not applicableAdvisory
Applies when: Hark shares two or more URLs that answer one request or belong to one conversational beat.
Requirement: Put the links together in one links bubble, one per line, each as its placeholder or the draft's exact URL, with at most one short prose bubble framing the set that does more than label it.
Not applicable. The delivered response shares only one URL.
Evidence: E0013

make_progress_updates_material

Not applicableAdvisory
Applies when: The draft contains a progress update and the input does not say the task is still running.
Requirement: Send only a new fact, completed result, observed blocker, or changed estimate that the draft offers.
Not applicable. The response is a completed answer, not a progress update.

compress_summary

Not applicableAdvisory
Applies when: Hark provides a summary.
Requirement: Put the summary in one document bubble and keep it materially shorter than the source.
Not applicable. The user requested an answer and comparison, not a summary deliverable.
Evidence: E0001

follow_summary_instructions

Not applicableAdvisory
Applies when: The user requests a summary with a specified length, format, audience, focus, or reading level.
Requirement: Follow the requested summary constraints when the draft carries them and they remain compatible with the required document-bubble delivery.
Not applicable. No summary with specified constraints was requested.
Evidence: E0001

use_default_summary_length

Not applicableAdvisory
Applies when: The user requests a summary without specifying a length or format.
Requirement: Use one document bubble whose content is normally no more than a couple hundred words, extending only when the source's section count requires it.
Not applicable. The user did not request an unconstrained summary.
Evidence: E0001

preserve_summary_skeleton

Not applicableAdvisory
Applies when: Hark provides a summary.
Requirement: Keep the source's own skeleton while making each section or act a short numbered line.
Not applicable. The response is not a structured-source summary.

preserve_summary_order

Not applicableAdvisory
Applies when: Hark summarizes a source with sections or acts.
Requirement: Preserve the source's section or act order and do not drop one.
Not applicable. No source sections or acts were being summarized.

keep_summary_qualifications_local

Not applicableAdvisory
Applies when: A summarized statement needs a qualification.
Requirement: Keep the qualification next to the summarized statement it modifies.
Not applicable. The response is not governed by the summary-specific qualification rule.

use_summary_numbered_lines

Not applicableAdvisory
Applies when: Hark formats a structured-source summary.
Requirement: Use short numbered lines inside the document bubble instead of flat prose bubbles.
Not applicable. No structured-source summary was requested or delivered.

give_one_concrete_next_step

Not applicableAdvisory
Applies when: The user must act before Hark can continue.
Requirement: State one concrete next step only when the draft offers it.
Not applicable. The user does not need to act before Hark can continue.

omit_running_task_updates

Not applicableAdvisory
Applies when: The input says a task is still running.
Requirement: Send no response about the running task. Do not claim a lack of access, suggest the user do it, or announce that work continues.
Not applicable. The task had completed before the assistant messages were delivered.
Evidence: E0007, E0009

preserve_code_exactly

Not applicableAdvisory
Applies when: The draft contains a code block the user needs.
Requirement: Copy the code byte for byte into one code bubble with its language and a short sentence-case title.
Not applicable. No needed code block appears in the draft.

preserve_document_exactly

Not applicableAdvisory
Applies when: The draft contains an email, message, template, letter, exact quote, or list meant for use elsewhere.
Requirement: Copy the full text byte for byte into one document bubble. A message the user is meant to send, paste, or forward is always a document bubble, never prose. A composed summary card is the only exception.
Not applicable. The draft contains no email, message, template, letter, exact quote, or reusable document artifact.

preserve_attachment_names

Not applicableAdvisory
Applies when: The input lists an attachment riding with the reply.
Requirement: Put each attachment in its own matching attachment bubble and use the attachment's exact input name.
Not applicable. No attachment rides with the reply.