kpopper

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.

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' - because the recorded answer, with its source, beats a fresh search of the tree; before changing a value the record may hold; and whenever the session opener or a grounding line names entries. Runs pull, affects and check, reads what hypotheses and other branches propose, and searches when a question maps to no name. 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.

Compatibility alias for kpopper Hub. Use when explicitly invoked as $page or /kpopper:page. Follow the canonical hub skill; do not select this alias for ordinary requests.

Write what the work found into the project's knowledge record, so the next session inherits it instead of re-deriving it. Use the moment something worth keeping exists: a fact taken from a source, a rule worked out, a decision or conclusion, a measurement, a correction to a recorded value, or a question left open - and check for unrecorded findings before implementation, handoff (including a PR), or finishing work. Record within the user's write authorization. The first write creates GROUNDING.yaml. Covers one-report update, add, set, review, same and distinct, judgments with a falsifier, and background capture.

Set up kpopper watch for background branch compatibility, scoped shared facts, and daily review. Use when asked to watch a project's graph, check worktree changes against main, share external observations, or install a kpopper routine. Ordinary followup capture recommends scheduling without enabling it.