← Back to scenario detail
Response style analysis
Applied 37 · Passed 27 · Failed 10 · Not applicable 31
Rubric: services/agent/prompts/editor/v1.tmpl · SHA-256 ad82285f2536995680bae1f21d87829d473812bd68a82c518246709a6fea8ae9
Prompt
Use the web_fetch tool to answer the prompt.
What events are scheduled next calendar month on https://www.chasecenter.com/events? List them chronologically with date, start time, and current ticket status.
Hark's responses
October at Chase Center has 31 events. Free Thrive City programs and concerts are both listed, all either ticketed or RSVP.
### October 2026 at Chase Center · chronological list
| Date | Event | Start | Status |
|---|---|---|---|
| Oct 2 | Little Bears Music Class | 10:00 AM | RSVP Now |
| Oct 3 | Weekly Fitness: Elevated Intervals + Aligned Pilates | 10:00 AM | RSVP Now |
| Oct 3 | Disney Worlds Collide Concert Tour | 7:00 PM | Buy Tickets |
| Oct 6 | Live Music Lunch Series | 12:00 PM | RSVP Now |
| Oct 6 | Warriors vs. Lakers (Preseason) | 7:00 PM | Buy Tickets |
| Oct 7 | Weekly Fitness: Yoga Flow | 12:00 PM | RSVP Now |
| Oct 7 | Rod Wave | 8:00 PM | Buy Tickets |
| Oct 9 | Little Bears Music Class | 10:00 AM | RSVP Now |
| Oct 10 | Weekly Fitness: Elevated Intervals + Aligned Pilates | 10:00 AM | RSVP Now |
| Oct 10 | Warriors vs. Kings (Preseason) | 5:30 PM | Buy Tickets |
| Oct 11 | Chayanne | 7:00 PM | Buy Tickets |
| Oct 13 | Live Music Lunch Series | 12:00 PM | RSVP Now |
| Oct 14 | Weekly Fitness: Yoga Core | 12:00 PM | RSVP Now |
| Oct 15 | Young Miko | 8:00 PM | Buy Tickets |
| Oct 16 | Little Bears Music Class | 10:00 AM | RSVP Now |
| Oct 16 | Warriors vs. Trail Blazers (Preseason) | 7:00 PM | Buy Tickets |
| Oct 17 | Weekly Fitness: Elevated Intervals + Aligned Pilates | 10:00 AM | RSVP Now |
| Oct 19 | Doja Cat with Latto | 7:30 PM | Buy Tickets |
| Oct 20 | Live Music Lunch Series | 12:00 PM | RSVP Now |
| Oct 21 | Weekly Fitness: Athletic Stretch | 12:00 PM | RSVP Now |
| Oct 23 | Little Bears Music Class | 10:00 AM | RSVP Now |
| Oct 23 | Warriors vs. Grizzlies | 7:00 PM | Buy Tickets |
| Oct 24 | Thrill-O-Ween | 12:00 PM | RSVP Now |
| Oct 25 | Football Sundays | 10:00 AM | RSVP Now |
| Oct 27 | Live Music Lunch Series | 12:00 PM | RSVP Now |
| Oct 27 | Phoebe Bridgers | 7:30 PM | Buy Tickets |
| Oct 28 | Weekly Fitness: Athletic Core | 12:00 PM | RSVP Now |
| Oct 28 | Phoebe Bridgers | 7:30 PM | Buy Tickets |
| Oct 30 | Little Bears Music Class | 10:00 AM | RSVP Now |
| Oct 30 | Warriors vs. Lakers (NBA Cup) | 7:00 PM | Buy Tickets |
| Oct 31 | Below the Belt + Aligned Pilates | 10:00 AM | RSVP Now |
Nothing's sold out yet, and no presale or on-sale-later labels are showing.
Fail
use_structure_only_when_helpful
FailAdvisoryApplies 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 inside an ordinary assistant message rather than a correctly tagged table bubble.
keep_one_thought_per_bubble
FailAdvisoryApplies 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 bubble combines the event count with a separate classification of free programs, concerts, ticketing, and RSVP status.
avoid_prose_markup
FailAdvisoryApplies 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 event listing uses a Markdown heading and Markdown table syntax in an assistant message.
choose_collection_format_for_comparison
FailAdvisoryApplies 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.
The comparable events use table-shaped Markdown, but not a properly tagged table bubble as required.
keep_deliverable_companions_brief
FailAdvisoryApplies 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 framing companion before the listing contains two sentences and 21 words, exceeding the one-sentence and 20-word limits.
avoid_markdown_in_prose
FailAdvisoryApplies 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 second assistant message visibly contains a Markdown heading and pipe-table markup rather than a rich table bubble.
isolate_rich_content
FailAdvisoryApplies 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-shaped content and its Markdown heading are mixed in a normal assistant message instead of an isolated, correctly tagged table bubble.
keep_card_companions_contextual
FailAdvisoryApplies 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 first companion summarizes the card’s count and status composition instead of providing only concise context or a caveat.
tag_every_bubble
FailAdvisoryApplies 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 evidence shows generic assistant messages and no matching text or table bubble tags, including for the Markdown table.
provide_rich_metadata
FailAdvisoryApplies 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.
Although the table has pipe rows and a heading, it lacks a proper table-bubble title field and the required “Excel Spreadsheet” subtitle.
Pass
follow_explicit_style_instructions
PassAdvisoryApplies 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.
The response lists the events chronologically with date, start time, and status, as requested.
preserve_draft_substance
PassAdvisoryApplies 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 delivered response retains the draft’s event set, ordering, times, statuses, and status takeaway.
preserve_factual_spans
PassAdvisoryApplies 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 dates, times, event names, count, and status labels selected from the draft retain their values and scope.
avoid_invented_content
PassAdvisoryApplies 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 response adds no unsupported option, suggestion, commitment, or material factual claim beyond the draft.
lead_with_outcome
PassAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Lead with the answer, result, necessary question, or blocker.
The first bubble immediately states the result: 31 October events.
use_direct_short_sentences
PassAdvisoryApplies when: Hark sends a user-visible prose response.
Requirement: Use direct, short sentences and the shortest phrasing that preserves the full meaning.
The prose companion bubbles use brief, direct sentences.
prefer_specific_details
PassAdvisoryApplies when: Specific names, dates, quantities, or outcomes are available.
Requirement: Use the specific details instead of vague adjectives or descriptions.
The table gives specific dates, event names, start times, and exact status labels.
avoid_condescending_explanations
PassAdvisoryApplies when: Hark explains information to the user.
Requirement: Explain the information without talking down to the user or belaboring basic points.
The status explanation is concise and neutral rather than patronizing.
avoid_throat_clearing
PassAdvisoryApplies 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 event count rather than praise, acknowledgment, or a preview.
use_plain_precise_language
PassAdvisoryApplies 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.
The response uses plain wording and retains the exact actionable labels “Buy Tickets” and “RSVP Now” in the table.
use_hearer_oriented_grammar
PassAdvisoryApplies 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-oriented grammar or incorrect wellbeing construction appears.
limit_prose_bubbles
PassAdvisoryApplies 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 short prose companion bubbles around the structured event listing, within the three-bubble limit.
keep_prose_bubbles_compact
PassAdvisoryApplies 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 companion is under 40 words.
punctuate_sentences
PassAdvisoryApplies when: Hark sends a plain-prose bubble.
Requirement: Use proper capitalization and end every sentence with a period or question mark.
The prose sentences are capitalized and end with periods.
avoid_duplicate_content
PassAdvisoryApplies 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 event rows appear once, and the companion text adds context rather than duplicating the full listing.
keep_one_entity_per_item
PassAdvisoryApplies when: Hark presents comparable entities or occurrences in a table.
Requirement: Put one comparable entity or occurrence in each row.
Each table row represents one scheduled event occurrence, including separate rows for repeated events.
use_consistent_collection_schema
PassAdvisoryApplies when: Hark presents multiple comparable items.
Requirement: Expose the same fields with the same meanings for every comparable item.
Every event uses the same four fields: date, event, start, and status.
keep_comparable_detail
PassAdvisoryApplies 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.
Every row includes all item-level facts supplied by the draft: date, event name, start time, and status.
keep_table_columns_focused
PassAdvisoryApplies when: Hark presents a table.
Requirement: Keep columns focused on the user's decision or question.
The four columns directly serve the user’s scheduling and ticket-status question.
keep_every_commissioned_item
PassAdvisoryApplies 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.
All 31 events contained in the draft are delivered in one collection without reducing the set.
answer_before_background
PassAdvisoryApplies when: Hark provides an answer or outcome with supporting background.
Requirement: Give the answer or outcome before the background detail.
The event count and overall result precede the detailed listing and status note.
avoid_repeated_conclusions
PassAdvisoryApplies 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 event count and the absence of sold-out or presale labels are distinct conclusions rather than repeated copies.
match_detail_to_request
PassAdvisoryApplies 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 user commissioned the complete monthly set, so retaining every event and requested field is appropriate.
avoid_generic_help_offers
PassAdvisoryApplies when: Hark has completed the requested response.
Requirement: Do not append a generic offer of further help.
The completed response does not append an offer of further help.
keep_narrow_screens_readable
PassAdvisoryApplies when: Hark presents structured content in web chat.
Requirement: Keep the response readable on a narrow screen and avoid unnecessarily wide tables.
The listing uses only four concise, decision-relevant columns and avoids unnecessary width.
include_result_in_message
PassAdvisoryApplies 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 complete event listing is included directly in the delivered message.
limit_rich_bubbles
PassAdvisoryApplies when: Hark sends rich content.
Requirement: Use one rich bubble unless the draft genuinely carries two distinct artifacts.
Only one structured artifact, the event table, is presented.
Not applicable
preserve_instruction_direction
Not applicableAdvisoryApplies 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 does not shorten or merge an instruction telling the user what to do.
avoid_unwarranted_social_language
Not applicableAdvisoryApplies 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 applicableAdvisoryApplies 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 applicableAdvisoryApplies when: Hark responds about a serious, painful, or high-stakes subject.
Requirement: Stay short and direct while dropping slang and swagger.
Not applicable. The event-list request is not serious, painful, or high stakes.
use_hark_first_person
Not applicableAdvisoryApplies 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 process, or its instructions.
avoid_forbidden_social_phrases
Not applicableAdvisoryApplies 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, preference, or opinion.
avoid_delivery_pointers
Not applicableAdvisoryApplies 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.
Not applicable. The response does not point the user to another message, location, or delivery step.
include_ranking_column
Not applicableAdvisoryApplies 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.
Not applicable. The user requested chronological ordering, not a cheapest, fastest, or other ranked comparison.
include_recommendation_links
Not applicableAdvisoryApplies 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. This is an event listing rather than a recommendation table, and the draft supplies no destination link for each event.
isolate_single_links
Not applicableAdvisoryApplies 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.
Not applicable. The delivered response shares no URL.
group_related_links
Not applicableAdvisoryApplies 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 no set of URLs.
preserve_link_urls
Not applicableAdvisoryApplies 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.
Not applicable. The delivered response does not share a URL from the draft.
avoid_request_restatement
Not applicableAdvisoryApplies 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.
Not applicable. The response does not repeat the user’s request as prose.
avoid_routine_tool_narration
Not applicableAdvisoryApplies when: Hark describes its research or routine tool use.
Requirement: Cut research, sourcing, verification, disambiguation, and routine tool-use narration from the response.
Not applicable. The delivered response does not narrate web fetching, browsing, sourcing, or verification.
make_progress_updates_material
Not applicableAdvisoryApplies 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 delivered assistant messages contain no progress update.
compress_summary
Not applicableAdvisoryApplies when: Hark provides a summary.
Requirement: Put the summary in one document bubble and keep it materially shorter than the source.
Not applicable. The response is a requested event listing, not a summary of a source document.
follow_summary_instructions
Not applicableAdvisoryApplies 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. The user did not request a summary.
use_default_summary_length
Not applicableAdvisoryApplies 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.
preserve_summary_skeleton
Not applicableAdvisoryApplies 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 summary.
preserve_summary_order
Not applicableAdvisoryApplies 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. The response does not summarize a source with sections or acts.
keep_summary_qualifications_local
Not applicableAdvisoryApplies when: A summarized statement needs a qualification.
Requirement: Keep the qualification next to the summarized statement it modifies.
Not applicable. No summarized statement requiring a local qualification is presented.
use_summary_numbered_lines
Not applicableAdvisoryApplies when: Hark formats a structured-source summary.
Requirement: Use short numbered lines inside the document bubble instead of flat prose bubbles.
Not applicable. The response is not a structured-source summary.
state_blocker_and_impact
Not applicableAdvisoryApplies 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.
Not applicable. The delivered response reports no inability or blocker.
present_partial_result_before_blocker_detail
Not applicableAdvisoryApplies when: Hark has a useful partial result and also reports a blocker.
Requirement: Present the partial result first and keep any blocker explanation compact.
Not applicable. No blocker is reported alongside a partial result.
give_one_concrete_next_step
Not applicableAdvisoryApplies 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.
avoid_internal_error_details
Not applicableAdvisoryApplies 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.
Not applicable. No blocker or internal error information is exposed.
avoid_repeated_apology
Not applicableAdvisoryApplies when: Hark reports a blocker or failure.
Requirement: Avoid repeated apologies and generic failure language.
Not applicable. The response reports no failure and contains no apology.
omit_running_task_updates
Not applicableAdvisoryApplies 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 relevant browser task had completed before the delivered final response.
preserve_code_exactly
Not applicableAdvisoryApplies 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. The draft contains no code block needed by the user.
preserve_document_exactly
Not applicableAdvisoryApplies 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.
preserve_attachment_names
Not applicableAdvisoryApplies 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.