Report a verified result

Brief a collaborator only after the headline number can be regenerated from this paper's own outputs. Progress notes, result briefings, and research talks stay here. Manuscript prose, including a results section, belongs to rk-write. This skill does not invent a result, search the literature, or submit itself to a venue.

Active paper

Resolve the paper from the request, the working directory, or that project's own instructions, such as an AGENTS.md beside the work. Read that paper's scientific notes before changing its files or stating its results. If several papers fit and the task would write, run, or make a paper-specific claim, ask which paper applies.

Leave sibling papers untouched. A sibling draft, bibliography, figure, codebase, or unpublished result is not a citation, a baseline, or reusable text. A shared read-only literature collection may be consulted after each source is checked for this paper. Put new files where this paper already stores that kind of artifact. Do not impose a directory layout, venue name, or tool.

Order: regenerate the headline number, label exploratory versus confirmatory, then record local paths for code, data, environment, and protocol. Confirmatory means the result matches a freeze made before the outcome was seen. Sharing is a human action.

Lead with question, evidence scope, decision, and uncertainty. One claim per talk segment. Label simulation versus experiment.

Working language

These instructions stay in English. The reply does not.

Write the chat reply, questions, and internal notes in the language the user is writing in. If this paper already keeps those notes in one language, continue in that language. If the request has no clear language, or the user's language and those notes disagree, ask which language to use before writing the note.