← Back to scenario detail
Response style analysis
Applied 39 · Passed 24 · Failed 15 · Not applicable 29
Rubric: services/agent/prompts/editor/v1.tmpl · SHA-256 ad82285f2536995680bae1f21d87829d473812bd68a82c518246709a6fea8ae9
Prompt
I already verified these notes, so do not research them. Give me exactly one sentence per article, with the article's link in that sentence. Then add one sentence naming the main theme.
Atlas compiler update: the team replaced its interpreter with a native compiler to reduce startup time. It has 103 points and 308 comments. https://example.com/articles/atlas-compiler
Harbor database update: the project added online schema changes for large production tables. It has 241 points and 36 comments. https://example.com/articles/harbor-database
Meadow accessibility study: researchers found that descriptive button labels reduced navigation errors. It has 77 points and 19 comments. https://example.com/articles/meadow-accessibility
Orbit battery report: the new cell chemistry retained 92 percent capacity after 1,000 cycles. It has 164 points and 52 comments. https://example.com/articles/orbit-battery
Hark's responses
The Atlas compiler update replaced the interpreter with a native compiler to cut startup time. https://example.com/articles/atlas-compiler
The Harbor database update added online schema changes for large production tables. https://example.com/articles/harbor-database
The Meadow accessibility study found descriptive button labels reduced navigation errors. https://example.com/articles/meadow-accessibility
The Orbit battery report describes a new cell chemistry that retained 92 percent capacity after 1,000 cycles. https://example.com/articles/orbit-battery
Main theme: concrete engineering upgrades that make existing systems faster, safer to change, easier to use, and longer lasting.
Fail
follow_explicit_style_instructions
FailAdvisoryApplies 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 gives one summary sentence per article and one theme sentence, but each URL appears after the article sentence’s closing period rather than within that sentence.
preserve_draft_substance
FailAdvisoryApplies 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 article summaries omit every points and comments count that appeared in the selected draft content.
prefer_specific_details
FailAdvisoryApplies when: Specific names, dates, quantities, or outcomes are available.
Requirement: Use the specific details instead of vague adjectives or descriptions.
Specific points and comments counts were available for every article but were omitted.
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 response presents a related set of links and commissioned article summaries as plain prose rather than using the applicable rich-content structure.
limit_prose_bubbles
FailAdvisoryApplies 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.
The response uses five prose bubbles even though the five short sentences could have been delivered together without exceeding three bubbles.
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 four commissioned articles share a common schema, but the response does not use one table bubble.
keep_comparable_detail
FailAdvisoryApplies 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 response drops the points and comments facts supplied for every commissioned article.
keep_every_commissioned_item
FailAdvisoryApplies 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 four articles are present, but they are split across prose messages rather than delivered together in one rich bubble as required.
group_related_links
FailAdvisoryApplies 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.
The four URLs answer one request but are distributed through separate prose bubbles rather than grouped in one links bubble.
compress_summary
FailAdvisoryApplies when: Hark provides a summary.
Requirement: Put the summary in one document bubble and keep it materially shorter than the source.
The article summaries are materially shorter than the notes, but they are sent as prose bubbles rather than one document bubble.
follow_summary_instructions
FailAdvisoryApplies 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.
The response broadly follows the requested sentence count, but the links are outside the article sentences and the summary is not delivered in the required document bubble.
preserve_summary_skeleton
FailAdvisoryApplies when: Hark provides a summary.
Requirement: Keep the source's own skeleton while making each section or act a short numbered line.
The response preserves the four-article skeleton but does not format the sections as short numbered lines in a document bubble.
use_summary_numbered_lines
FailAdvisoryApplies when: Hark formats a structured-source summary.
Requirement: Use short numbered lines inside the document bubble instead of flat prose bubbles.
The structured summary is delivered as separate unnumbered prose bubbles rather than numbered lines inside a document 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.
Each URL is mixed into a prose bubble instead of being placed in an appropriately tagged link or links bubble.
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 observed assistant messages show plain message content without matching text, links, or document bubble tags.
Pass
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 names, technical claims, quantities retained in the response, and all four URLs preserve their original referents, 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 delivered claims and theme all come from the draft; no new option, caveat, next step, or commitment was added.
lead_with_outcome
PassAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Lead with the answer, result, necessary question, or blocker.
Each bubble begins directly with the relevant article result or the main theme.
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 response uses concise, direct sentences without unnecessary explanation.
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 article explanations are neutral and do not belabor basic points or talk down to the user.
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 immediately with the first article 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 language while retaining exact technical terms such as native compiler and online schema changes.
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.
The response uses natural definite articles and contains no inappropriate self-wellbeing phrasing.
avoid_forbidden_social_phrases
PassAdvisoryApplies when: Hark expresses enthusiasm, preference, or an opinion.
Requirement: Do not use bro-speak, say Hark would love something, or say Hark feels something.
The thematic opinion contains no bro-speak and does not say Hark loves or feels anything.
keep_one_thought_per_bubble
PassAdvisoryApplies 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.
Each of the five prose bubbles contains one article thought or the separate theme thought.
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.
Every prose bubble is well below 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.
Each prose sentence is capitalized and ends with a period; the trailing URLs are not sentences.
avoid_prose_markup
PassAdvisoryApplies 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 prose contains no lists, Markdown syntax, emoji spam, em dashes, or punctuation hyphens.
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.
No article summary, URL, or conclusion is repeated across bubbles.
use_consistent_collection_schema
PassAdvisoryApplies when: Hark presents multiple comparable items.
Requirement: Expose the same fields with the same meanings for every comparable item.
Each article item consistently includes its name, central finding or update, and URL.
preserve_link_urls
PassAdvisoryApplies 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.
Each URL is reproduced exactly and appears only once.
answer_before_background
PassAdvisoryApplies when: Hark provides an answer or outcome with supporting background.
Requirement: Give the answer or outcome before the background detail.
Each item states the update or finding directly without placing background before it.
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 response remains concise while retaining all four commissioned article items and the requested theme.
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.
preserve_summary_order
PassAdvisoryApplies when: Hark summarizes a source with sections or acts.
Requirement: Preserve the source's section or act order and do not drop one.
The articles remain in the source order: Atlas, Harbor, Meadow, then Orbit.
keep_summary_qualifications_local
PassAdvisoryApplies when: A summarized statement needs a qualification.
Requirement: Keep the qualification next to the summarized statement it modifies.
The Orbit retention result keeps its 92 percent and 1,000-cycle qualification in the same sentence.
avoid_markdown_in_prose
PassAdvisoryApplies 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 delivered prose uses raw URLs and contains no Markdown syntax.
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 short, single-thought messages are easy to read on a narrow screen and contain no wide table.
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 article summaries and theme are included directly in the delivered messages.
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 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 subject is not serious, painful, or high stakes in the sense covered by this rule.
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_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, file, or location.
keep_one_entity_per_item
Not applicableAdvisoryApplies when: Hark presents comparable entities or occurrences in a table.
Requirement: Put one comparable entity or occurrence in each row.
Not applicable. The response does not present a table.
keep_table_columns_focused
Not applicableAdvisoryApplies when: Hark presents a table.
Requirement: Keep columns focused on the user's decision or question.
Not applicable. The response contains no table.
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 did not request a 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. The response is not a table of options or recommendations.
keep_deliverable_companions_brief
Not applicableAdvisoryApplies 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.
Not applicable. No commissioned-work rich bubble has prose companions.
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 reply shares four related URLs, not exactly one URL.
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 restate the user's request.
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 response contains no research, verification, sourcing, or tool-use narration.
avoid_repeated_conclusions
Not applicableAdvisoryApplies 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.
Not applicable. The main theme is stated only once.
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 response is not a progress update.
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 specified the summary format and length.
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 response reports no blocker or incomplete task.
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. The response contains no blocker or partial-result report.
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. The response reports no error or blocker.
avoid_repeated_apology
Not applicableAdvisoryApplies when: Hark reports a blocker or failure.
Requirement: Avoid repeated apologies and generic failure language.
Not applicable. The response contains no failure report or 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 input does not say that a task is still running.
keep_card_companions_contextual
Not applicableAdvisoryApplies 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.
Not applicable. The response contains no rich card with an adjacent prose companion.
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, template, exact quote, or other reusable document requiring byte-exact delivery.
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. The input lists no attachments.
limit_rich_bubbles
Not applicableAdvisoryApplies when: Hark sends rich content.
Requirement: Use one rich bubble unless the draft genuinely carries two distinct artifacts.
Not applicable. The response sends no rich bubbles.
provide_rich_metadata
Not applicableAdvisoryApplies 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.
Not applicable. The response sends no table, code, or document bubble requiring metadata.