← Back to scenario detail

Response style analysis

Applied 45 · Passed 36 · Failed 9 · Not applicable 23

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

Prompt

Use the web_fetch tool to answer the prompt. What release announcements were published on https://kubernetes.io/blog/ in the past 14 days? Summarize patch versions, security fixes, regressions, and upgrade warnings.

Hark's responses

No patch releases, CVEs, or regressions on the Kubernetes blog in the past 14 days. Just v1.37 feature posts.
### v1.37 announcements (Aug 28–Sep 10) · Blog posts | Date | Post | What it covers | |---|---|---| | Sep 10 | [Scheduler Preemption for In-Place Pod Resize](https://kubernetes.io/blog/2026/09/10/kubernetes-v1-37-scheduler-preemption-for-in-place-pod-resize-alpha/) | Alpha | | Sep 9 | [Node Lifecycle Conditions](https://kubernetes.io/blog/2026/09/09/kubernetes-v1-37-node-lifecycle-conditions/) | New node condition API | | Sep 8 | [Advancing Workload-Aware Scheduling](https://kubernetes.io/blog/2026/09/08/kubernetes-v1-37-advancing-workload-aware-scheduling/) | AI/ML batch scheduling | | Sep 4 | [KubeletInUserNamespace (rootless)](https://kubernetes.io/blog/2026/09/04/kubernetes-v1-37-rootless-beta/) | Beta | | Sep 3 | [DRA Updates](https://kubernetes.io/blog/2026/09/03/kubernetes-v1-37-dra-updates/) | DRA Extended Resource to GA | | Sep 2 | [HPA scale to zero](https://kubernetes.io/blog/2026/09/02/kubernetes-v1-37-hpa-scale-to-zero-beta/) | Beta, on by default | | Sep 1 | [etcd RangeStream](https://kubernetes.io/blog/2026/09/01/kubernetes-v1-37-etcd-range-stream/) | Beta, less memory on large lists | | Aug 31 | [Storage Version Migration](https://kubernetes.io/blog/2026/08/31/kubernetes-v1-37-storage-version-migration-ga/) | GA, enabled by default | | Aug 28 | [Pod Certificates and Cluster Trust Bundles](https://kubernetes.io/blog/2026/08/28/kubernetes-v1-37-pod-certificates-and-cluster-trust-bundles/) | Workload identity certs |
One heads-up: storage version migration is now on by default in v1.37. During the metrics API transition to v1, implementations should serve both v1 and v1beta1 since kubectl top prefers v1 but HPA still only speaks v1beta1.

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.
Most draft substance is preserved, but the response drops the important qualification that the Metrics API post was published August 27, outside the 14-day window. This makes the final warning appear to belong to the requested period.
Evidence: E0011, E0014

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.
Names, versions, dates, and URLs are otherwise preserved, but omitting the August 27 date changes the scope of the Metrics API warning relative to the requested 14-day period.
Evidence: E0001, E0010, E0011, E0014

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 post-table companion is two sentences and about 35 words, exceeding the allowed one sentence and 20 words.
Evidence: E0014

group_related_links

FailAdvisory
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.
The reply shares multiple related URLs in a table rather than one links bubble. Although the table is useful for comparison, this rule's literal link-set requirement is not met.
Evidence: E0013

compress_summary

FailAdvisory
Applies when: Hark provides a summary.
Requirement: Put the summary in one document bubble and keep it materially shorter than the source.
The response provides a summary, but it is delivered as prose plus a table rather than one document bubble.
Evidence: E0012, E0013, E0014

preserve_summary_skeleton

FailAdvisory
Applies 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 announcement sequence but does not use the required short numbered-line summary skeleton in a document bubble.
Evidence: E0013

use_summary_numbered_lines

FailAdvisory
Applies when: Hark formats a structured-source summary.
Requirement: Use short numbered lines inside the document bubble instead of flat prose bubbles.
The structured summary uses a table rather than short numbered lines inside a document bubble.
Evidence: E0013

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 companion content is relevant, but the post-table companion exceeds the permitted short single-sentence form.
Evidence: E0014

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 pipe-style rows and a short title, but its visible subtitle is “Blog posts” rather than the required “Excel Spreadsheet.”
Evidence: E0013

Pass

follow_explicit_style_instructions

PassAdvisory
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.
The response uses a concise table and focuses on patch releases, security issues, regressions, and upgrade warnings as requested.
Evidence: E0001, E0012, E0013, E0014

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 claims and warnings all appear in the draft or fetched Kubernetes pages.
Evidence: E0007, E0010, E0011, E0012, E0013, E0014

lead_with_outcome

PassAdvisory
Applies when: Hark sends a user-visible response.
Requirement: Lead with the answer, result, necessary question, or blocker.
The first bubble immediately states the main result: no patch releases, CVEs, or regressions were found in the period.
Evidence: E0012

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 direct and compact, with short sentences and little filler.
Evidence: E0012, E0014

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 names dates, Kubernetes v1.37 features, API versions, and release stages rather than using vague descriptions.
Evidence: E0013, E0014

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 technical explanation is brief and neutral without belaboring basic concepts.
Evidence: E0014

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: E0012

use_structure_only_when_helpful

PassAdvisory
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 comparable announcements are presented as a table rather than recreated as unstructured prose.
Evidence: E0013

use_plain_precise_language

PassAdvisory
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.
The response uses exact technical terms such as Storage Version Migration, Metrics API, HPA, v1, and v1beta1 while remaining concise.
Evidence: E0013, E0014

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 contrary self-oriented possessive or incorrect wellbeing construction appears.
Evidence: E0012, E0014

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.
The reply uses two prose bubbles: one for the main finding and one for the upgrade caveat.
Evidence: E0012, E0014

keep_one_thought_per_bubble

PassAdvisory
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 bubble gives the overall finding, while the second gives related upgrade-transition warnings.
Evidence: E0012, E0014

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.
Both prose bubbles are under 40 words.
Evidence: E0012, E0014

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 each sentence with a period.
Evidence: E0012, E0014

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 bubbles contain no lists, headers, Markdown, em dashes, or decorative markup.
Evidence: E0012, E0014

avoid_duplicate_content

PassAdvisory
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 overview, table rows, and upgrade caveat carry distinct content without repeating a section or conclusion verbatim.
Evidence: E0012, E0013, E0014

choose_collection_format_for_comparison

PassAdvisory
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.
The announcements share common date, post, and coverage fields, and the response uses one table.
Evidence: 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.
Each table row represents one Kubernetes blog announcement.
Evidence: E0013

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.
Every announcement uses the same Date, Post, and What it covers fields.
Evidence: E0013

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.
All nine in-window announcements and their draft-provided row descriptions are retained in the table.
Evidence: E0011, E0013

keep_table_columns_focused

PassAdvisory
Applies when: Hark presents a table.
Requirement: Keep columns focused on the user's decision or question.
The three columns directly support identifying each announcement and understanding its release significance.
Evidence: E0013

keep_every_commissioned_item

PassAdvisory
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.
The table includes every one of the nine in-window posts identified in the draft.
Evidence: E0011, 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 announcement destinations are preserved as exact absolute URLs and are not shortened or duplicated elsewhere.
Evidence: E0011, 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 main finding appears before the detailed announcement table and transition background.
Evidence: E0012, E0013, E0014

avoid_repeated_conclusions

PassAdvisory
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 no-patch, no-CVE, no-regression conclusion is stated once.
Evidence: E0012

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 user commissioned a set of announcements, and the response keeps the full set while limiting prose to the main result and warning.
Evidence: E0001, E0012, E0013, E0014

avoid_generic_help_offers

PassAdvisory
Applies 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.
Evidence: E0014

follow_summary_instructions

PassAdvisory
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.
The response follows the requested focus on patch versions, security fixes, regressions, and upgrade warnings.
Evidence: E0001, E0012, E0014

preserve_summary_order

PassAdvisory
Applies when: Hark summarizes a source with sections or acts.
Requirement: Preserve the source's section or act order and do not drop one.
The announcements remain in the source's reverse-chronological order from September 10 through August 28.
Evidence: E0004, E0013

keep_summary_qualifications_local

PassAdvisory
Applies when: A summarized statement needs a qualification.
Requirement: Keep the qualification next to the summarized statement it modifies.
The compatibility qualification about serving both API versions is placed directly with the Metrics API transition statement.
Evidence: E0014

avoid_markdown_in_prose

PassAdvisory
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 prose bubbles contain no Markdown; the structured content is separated into the table presentation.
Evidence: E0012, E0013, E0014

keep_narrow_screens_readable

PassAdvisory
Applies when: Hark presents structured content in web chat.
Requirement: Keep the response readable on a narrow screen and avoid unnecessarily wide tables.
The table has only three focused columns and short cell contents, keeping it reasonably readable on narrow screens.
Evidence: E0013

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 findings and announcement set are included directly in the response.
Evidence: E0012, E0013, E0014

isolate_rich_content

PassAdvisory
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 separately from the surrounding prose bubbles.
Evidence: E0012, E0013, E0014

tag_every_bubble

PassAdvisory
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 observed delivery separates two prose messages from one structured table message, with no visibly mismatched content kind.
Evidence: E0012, E0013, E0014

limit_rich_bubbles

PassAdvisory
Applies when: Hark sends rich content.
Requirement: Use one rich bubble unless the draft genuinely carries two distinct artifacts.
The response uses one rich table bubble.
Evidence: E0013

Not applicable

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 does 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 subject is technical release reporting, not clearly a serious, painful, or high-stakes personal 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 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, preference, or opinion and uses no forbidden social phrase.

avoid_delivery_pointers

Not applicableAdvisory
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.
Not applicable. The response does not point the user to another bubble, file, or saved location as a substitute for the answer.

include_ranking_column

Not applicableAdvisory
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.
Not applicable. The user did not request a ranked comparison.

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 table lists release announcements, not options or recommendations.

isolate_single_links

Not applicableAdvisory
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.
Not applicable. The response shares more than one URL.

avoid_request_restatement

Not applicableAdvisory
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.
Not applicable. The response does not unnecessarily repeat the user's request.

avoid_routine_tool_narration

Not applicableAdvisory
Applies 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 does not narrate web fetching, research, sourcing, or verification steps.

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 delivered response contains no progress update.

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 specified a focus for the summary, so the default unconstrained-summary condition does not apply.

state_blocker_and_impact

Not applicableAdvisory
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.
Not applicable. The response reports no blocker or inability to complete the task.

present_partial_result_before_blocker_detail

Not applicableAdvisory
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.
Not applicable. No blocker is reported.

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 is not required to act before Hark can continue.

avoid_internal_error_details

Not applicableAdvisory
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.
Not applicable. No blocker or internal error is reported.

avoid_repeated_apology

Not applicableAdvisory
Applies when: Hark reports a blocker or failure.
Requirement: Avoid repeated apologies and generic failure language.
Not applicable. The response contains no apology or failure language.

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 tool had completed before the delivered response, and the response does not discuss a running task.
Evidence: E0004, E0007, E0010

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 or delivered response.

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 requiring byte-exact delivery.

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 is listed in the input.