Work

Experimental workshop space. Purpose-driven working artifacts that haven't codified into notes yet.

Each workshop is a directory exploring a specific workflow end-to-end: from question through sourcing and extraction to finished notes. The goal is to discover what patterns actually emerge from use, rather than designing structure upfront.

Active Workshops

  • extensible-controlled-vocabularies — designing how a code-enforced closed enum (ingest-report's source_type) becomes open-ended per installed KB while staying validator-checkable
  • lineage-mechanisms — revising lineage mechanisms across sources, generated reports, distillation records, report persistence, and source-to-source/source-to-note relation labels
  • src-architecture-alternatives — alternative architectures for src/commonplace/ from a full code read; active thread is an append-only event log as review-store source of truth with acceptance events that embed their snapshots
  • relocation-move-map-engine — collapsing note and directory relocation around one move-map engine for link rewriting, file moves, redirects, and removal of review-store rekeying
  • kb-graph-loader — testing whether validation, generated indexes, docs hooks, and review targeting should share one loaded KB note/graph model
  • epistack-competition — framework-side pointer to the sibling epistack-casebooks repo (FLF competition entry): what it's for and the backlog-to-commonplace.md protocol for moving ideas between the two repos
  • epistack-framework-additions — brainstorm of Commonplace additions that would make epistemic casework (FLF lab-leak/black-hole/egg-style cases) easier, plus a recommended two-layer personal-epistemology stance; a design menu feeding the sibling repo's backlog
  • agent-note-improvement — testing instructions that help agents improve weak existing notes by comparing an older weak revision against a later accepted revision
  • agent-memory-design — continuation workshop for discussing revisions and companion artifacts around kb/notes/designing-agent-memory-systems.md
  • bulk-operations — generalizing deep research, review reruns, connect triage, source refresh, validation sweeps, and corpus migrations into a reusable target-selection, sharding, execution, merge-back, and validation pattern
  • pi-agent-zerostack-comparison — preparing a code-grounded comparison instruction for the two Rust coding-agent CLIs cloned under related-systems/
  • vocabulary-governance — deciding how global, collection-local, and type-specific vocabularies should be declared and used by shipped KBs
  • aris-full-trial — running a private full-ARIS paper-production trial while keeping only framing and lessons learned in the public KB
  • review-bundle-packing — measuring and deciding whether review prompts must stay bundle-local or may pack multiple bundles into one run
  • validation — making validation a reliable part of the workflow: when, what, and how to validate (hooks, skill upgrades, periodic revalidation)
  • obsidian-affordances — deciding which Obsidian-facing affordances are useful compatibility layers versus representation drift for a repo-native KB
  • philosophy-borrowing — evaluating Peirce's abduction, Quine's web of belief, speech-act theory, and Carnap's explication as operational borrowings for KB methodology
  • agent-complexity-theory — formal consequences of the bounded-context orchestration model; candidate theorem sketches for academic collaboration
  • semantic-search-replacement — evaluating whether to replace qmd as the semantic-search layer, and with what
  • latent-space-generation-without-training — exploring whether embedding-guided novelty-generation papers can become a practical no-large-training workflow
  • review-revise-gated — finding review/revise arrangements that reliably produce the manual-edit quality bar, then codifying as reusable instructions
  • auditable-llm-editing — testing whether sparse, anchored writing state prevents accidental claim drift across repeated LLM editing passes
  • distributing-built-kbs — downstream counterpart to ADR 021's Commonplace-library shipping model: most hassle-free way to distribute a domain KB someone built, by separating the lightweight consumer path from the authoring machinery
  • lifecycle-management — mapping the full artifact life-cycle (intake, promotion, maturation, retirement); the agent-memory-design test case landed as a note + synthesis trait in kb/notes/designing-agent-memory-systems.md
  • derivative-report-uniformity — unifying frontmatter, directory structure, and (deliberately fuzzy) validation/staleness across the three source-derived reports: reviews, connect reports, critiques
  • scaffolding-relaxation — preserving the unresolved theory question from the Fable/workstream and vertical-agent ingests: which scaffolding recedes with stronger models, and which persists because it supplies state, authority, verification, lifecycle, or context economy
  • condensation-faithfulness-experiment — designing an experiment to test whether our condensation methodology (write conventions + gate suite) produces more behaviorally faithful memory than naive auto-summary, using the Faithful Self-Evolvers perturbation protocol

Complete file listing (generated at build time)