Instructions Directory

Type: kb/types/generated-index.md

Parent

Subdirectories

Files

  • Critique a note (instruction) - Build the strongest case that a note's central commitment is wrong, then check whether the note already answers it; use when a caller needs a report-only adversarial assay.
  • Decompose a note into premises and counterexample each (instruction) - Experimental run-by-hand report method that decomposes a note's central commitment into the premises it rests on and hunts a counterexample for each, routing failures as local (revise a premise) or global (the commitment fails)
  • Edit with Churchill and Zinsser (instruction) - Use when testing a compact Churchill-and-Zinsser cue for making complete prose shorter, more direct, and easier to follow without weakening it
  • Evaluate a log entry for note creation (instruction) - Evaluate whether a kb/log.md entry should be rejected, retained, folded into an existing artifact, or promoted into a new note
  • Example: Onboard a Second Brain on Commonplace (instruction) - One worked recipe for onboarding an operator who wants to build a personal Second Brain on top of Commonplace. Use as a starting template, not the canonical path.
  • Fix system
  • Ingest a directory (instruction) - Ingest a directory of related files (e.g. a cloned code repository) as a single source unit, producing one coherent .ingest.md that cites evidence across files.
  • Ingest a paper with code (instruction) - Use when source ingest receives a Papers with Code URL or the user requests an arXiv paper analysis grounded in its released implementation.
  • Invert solution-shaped requests (instruction) - Use before accepting a solution-shaped request as the task; recover the underlying problem, evidence status, alternative framings, and least-committing next move.
  • Maintain curated indexes (instruction) - Audit and maintain curated tag-index pages — evaluate editorial groupings, check for orphaned notes, and split or merge indexes where needed.
  • Migrate a directional link label (instruction) - Use after a directional link label has an adopted source-as-subject successor and a complete edge-disposition ledger, to migrate contracts, guidance, and active corpus tuples without rewriting history
  • Migrate semantics-preserving gate changes (instruction) - Carry current gate verdicts across a wording-only criterion edit without treating the edit as a fresh review
  • Publish an article (instruction) - Use when a circulating kb/articles draft has explicit approval to become a working paper or frozen dated article on the ProperDocs site
  • Re-Ingest (instruction) - Re-ingest a source whose .ingest.md report is stale — regenerate the analysis against current KB state, then update all notes that reference the old report.
  • Reconstruct a note's composition friction (instruction) - Experimental run-by-hand report method that tests whether a note's central claim survives concretization and locates its least-supported inferential joints
  • Refresh agent-memory review taxonomy (instruction) - Use when refreshing existing agent-memory-system reviews for the current artifact taxonomy without doing a full source re-review
  • Resolve a full-pass disposition (instruction) - Resolve, reject, supersede, or reconcile a retained full-pass delete, merge, or rehome disposition
  • Retire an artifact (instruction) - Retire a committed KB artifact — destination lookup, extraction gate, inbound handling, published redirect, and freshness-baseline retirement
  • Review triage (instruction) - Inspect diffs for note-changed assay pairs and acknowledge changes that do not invalidate their existing evidence
  • Revise Note (instruction) - Editorial revision of a single KB note — rewrites for logic, flow, and cohesion. Reads linked notes for context. Edits the file in place and reports changes.
  • Rewrite a note with ASD-STE100-inspired language (instruction) - Use when explicitly asked to experiment with rewriting one KB note in language inspired by ASD-STE100 while preserving its knowledge content
  • Run a full improvement pass on one note (instruction) - Run the full improvement pipeline over one note, apply its editorial packet, then close review over the resulting text with one assay cycle.
  • Run review batches (instruction) - Run snapshot-anchored verdict or report assays by selecting pairs, creating homogeneous jobs, delegating each job, and finalizing results
  • Run the compression bundle on one note (instruction) - Produce a disposable edit-strategy report for one note using the unanchored compression criteria and high-impact synthesis
  • Simplify prose sentence by sentence (instruction) - Use when simplifying all reader-facing prose in one Markdown file through a compact sentence-by-sentence pass without changing its meaning or structure
  • Simplify prose using established style advice (instruction) - Use when simplifying reader-facing prose through broad established style guidance while preserving its substantive claims and technical precision
  • Verify review quote grounding (instruction) - Verify that quote-anchored citations in a code-grounded review resolve to verbatim text in the reviewed source, run against the live checkout before it is discarded.
  • Write an Instruction (instruction) - Create a new instruction in kb/instructions/ by abstracting the stable core of repeated manual operations into a reusable, execution-optimized procedure.
  • Writing conventions for kb/instructions/ (prescriptive profile)