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

  • agent-memory-design — continuation workshop for discussing revisions and companion artifacts around kb/notes/designing-agent-memory-systems.md
  • agent-memory-review-rerun — planning and tracking the remaining systems.csv agent-memory review reruns after the first six refreshed reviews
  • ingestion-and-deep-search — revisiting directed reading through cp-skill-connect, especially how connect should use installed-KB goals without carrying commonplace-specific assumptions
  • 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
  • read-back-symbol-availability — folding the symbol-availability bound on push into the agent-memory-system review framework's read-back treatment, and planning a re-characterization pass over existing reviews
  • research-wiki-integration — evaluating whether ARIS Research Wiki should become a commonplace workshop subsystem, source workflow upgrade, or only a set of borrowed lifecycle patterns
  • gate-refactor — moving review storage and selector state from monolithic review bundles to gate-native definitions, memberships, and per-gate acceptances
  • 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)
  • tool-loop-control — rewriting the framework-loop note so it starts from why the standard tool loop exists and where convenience should end
  • obsidian-affordances — deciding which Obsidian-facing affordances are useful compatibility layers versus representation drift for a repo-native KB
  • harness-taxonomy-convergence — mapping five independent harness decompositions into one table; uncovered a structure × governance two-axis split
  • 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
  • write-type-resolver — migrating type: from an enum-string to a path-valued pointer addressing a hand-authored instructions doc per type
  • 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
  • shipping-model — deciding how commonplace ships its content so user collections stay theirs while our library sits alongside as a read-only dependency
  • distributing-built-kbs — the downstream counterpart to 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)