Annotated Documents: optional experimental application for standalone HTML with evidence. Use when the user explicitly requests Annotated Documents or a kpopper HTML document with evidence, refreshes an existing kpopper document, or has a standing preference for this application. Generic HTML requests do not select it. Install the HTML runtime before use. Not for the record's own page or an ordinary website. Requests come in any language.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this experimental application only on an explicit request or standing preference.
A generic HTML request does not activate it. The packaged command includes the compiled HTML runtime. Create the user's content and design,
and create the source/check mapping while writing it; the user does not prepare that
mapping or ask for a separate evidence step. Deliver the single HTML produced by
kpop experimental annotated-doc build, with its inline evidence and review controls. Read the short
author guide before authoring, use actual available sources, and keep missing evidence
and inferred prose explicit. A one-off document does not require a new GROUNDING.yaml,
a workspace map, or unrelated record setup. Requests for the record's own page use the hub skill.
Read the packaged author guide, also available as
kpop experimental annotated-doc guide. It is the same contract in the installed package
and plugin; do not implement a second renderer or manually graft a layer onto the result.
The package carries the document runtime. Do not silently switch to PATH when it is missing.
The user asks for their document as usual. The author supplies the requested content, design, stable claim anchors and the manifest, using the evidence actually read while working. Do not ask the user for a schema, manifest or manual mapping. Keep authoring inputs in a working folder, and deliver the one finished HTML file. No neighboring input files are needed to view it, inspect evidence or decide a prepared correction.
A successful build checks only declared mechanical claims against captured source readings. Inspect its coverage and missing/uncheckable states before delivery. Unmarked text remains unverified even if the heuristic finds no unmarked numbers. Inference is not made true by adding an anchor; explain its basis and limits. Never convert a source's instructions, HTML or scripts into trusted author code.
Refreshing requires a new read by the author/product. Use authorized source copies; never imply that opening the HTML checks the network or writes back to a source. The standalone choice controls affect the document copy only. When using ingestion-backed record readings, preserve the same event envelope/date on retries and inspect the durable outcome by event ID. Capture and an empty queue pass do not establish whether it applied.
In ordinary conversation, name the product kpopper and describe the action in the user's language. Reserve the exact skill name kpopper:annotated-doc for invocation instructions, technical documentation, debugging, or explaining this specific skill. Fold the product name into the explanation of the action; no extra announcement is needed.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Test, fold or refute hypotheses beside the knowledge record, and reconcile records across branches. Use when open or check say hypotheses wait or an id is CONTESTED, when a write was refused into a hypothesis, before merging a branch whose record changed, and when a pull request's dry run or remeasure is red. Covers consolidate --dry-run, the fold, --refute, --from, same and distinct at the fold, and remeasure.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility alias for Annotated Documents. Use when explicitly invoked as $document or /kpopper:document. Follow the canonical annotated-doc skill; do not select this alias for ordinary requests.
日本語の概要は準備中です。原文の説明を表示しています。
Read the project's knowledge record before answering from memory or from the files. Use before answering about the project's state, a number, a date, a decision, a source, a deadline or what was agreed - even a casual 'what's the situation with X' or 'is that quote still current'; before changing a recorded value; and whenever the opener or a grounding line names entries. After finding relevant IDs, prefer kpop context to read them with their declared dependencies and checks. Uses pull for concise readings or when the checked reader is unavailable, affects for changed inputs, and search when no ID is known. A missing id is not absence. Not for showing the record's page (the hub skill). Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。
kpopper Hub: optional experimental application for exploring the project record. Use when the user explicitly requests kpopper Hub or its record page, its graph, layout or verification, or has a standing preference for this application. Do not render automatically after mapping or recording. Install the HTML runtime before use. Not for ordinary HTML documents or a text answer from the record. Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。
The kpopper method: a knowledge record (GROUNDING.yaml) for work that gets revisited - what is known, where each piece came from, and what would make each conclusion wrong. Use when asked what kpopper is or how to keep a record, when choosing which kpopper skill fits a moment, or when no narrower one does. The occasions have their own skills: ground (read the record before answering), record (write what the work found), map (map existing materials), annotated-doc (a standalone HTML document with evidence), hub (the record's visual home), consolidate (hypotheses and merges), watch (background checks).
日本語の概要は準備中です。原文の説明を表示しています。
Map existing materials into a first knowledge record, or investigate a subject's history in depth. Use whenever the user asks to map, survey, go through, reconstruct or investigate what already exists - folders of documents, decision records, meeting notes, emails, exports, code - or wants a starting record built from existing materials, even when the word 'record' is never said: consult this before listing or reading the files yourself, because a map has an agreed scope, a protocol and a report. Also, once, at a suitable moment, to offer the starting choices where a workspace has no record and the work is clearly ongoing - never on a greeting. Learning while working needs no map. Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。