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

  • operator-led-article-clarification — recording a two-phase method for clarifying draft articles (operator-flagged passages diagnosed by kind, then an agent sweep by pattern) and its working taxonomy of reader difficulties, until enough article runs exist to promote a procedure
  • agentic-analysis-consumer-migration — migrating legacy memory-review consumers one by one to the main agentic review's generated files, then retiring duplicate legacy publication
  • reachability-working-paper-publication — staging the reachability conjecture as a versioned working-paper package with frozen authoritative appendices, live successor links, a dependency audit, and the remaining definitions, protocols, references, and probability criteria filled before publication approval
  • commonplace-nearest-constructions — characterizing Commonplace through the systems nearest its current human-inclusive theory builder, its path toward less task-specific human input, and its conjectured software-house endpoint
  • agent-operability-second-slice — making installed-project provenance and scaffold skew inspectable, then exercising a non-mutating three-way upgrade plan while preserving compact status and keeping review state opt-in
  • cognitive-architecture-transfer-scan — breadth-first conjecture scan whose promising cross-architecture candidates still require deduplication, selective grounding, and extraction
  • collection-aware-full-improvement-pass — determining whether prose-improvement workflows should route by collection and artifact function rather than imposing the theory-note contract
  • curiosity-prompts — completed Decapod prompt experiment whose exact report still needs relocation to a durable evidence surface before the workshop can close
  • dialectical-sample — illustrative dialectical/evidential collection awaiting an explicit keep, archive, or delete disposition after serving its prototype-checking purpose
  • error-catching — systematizing error-detection techniques, their catch rates, activation gaps, and promotion paths into a durable scheme
  • hanoi-experiment — OpenProse bookkeeping stress test with recorded results and remaining variations
  • review-evidence-and-disposition-hardening — resolving or rejecting the code-grounded review findings about result delivery, evidence identity, acknowledgement, recovery, and review-system contracts
  • skill-creator-distillation — comparing Codex and Claude skill creators as mixed-evidence distillation workflows and deciding what should be extracted
  • skills-vs-instructions — determining when reusable procedures need skill routing and execution policy rather than an ordinary instruction path
  • token-wiki-review — deciding and executing the durable promotion path for the completed Token Wiki analysis
  • full-pass-instruction-coherence-audit — repaired claim-change authority, phase/guard recovery, and closing completion after one instrumented keep exposed a schema-valid final capture with an edit-introduced parsing failure; scenario coverage remains incomplete
  • change-operations-catalogue — a working list of the operations by which Commonplace gets changed, each admitted by an observed instance, with the premises it must read and where they live; used to audit kb/reference/ in both directions under ADR 074. Carries no completeness claim
  • full-pass-recompute-cluster — queued full improvement passes over the six recoverability/economics notes written 2026-08-22/23, in two dependency-ordered batches so a reframe in the first lands before the second reads its premises
  • adr-routing — 71 ADRs, no index, and no instruction that routes a self-improvement run into them; the change loop is the only loop without an instruction, so the decisions that bind a change are consulted by luck. Shape is open: index, instruction, subsystem-keyed routing, or none of these
  • explanatory-theories-deployment-time-learning — testing whether explicit system theories improve candidate search, candidate choice, and evidence acquisition in deployment-time learning, including on-the-spot versus retained theories, SPADE-inspired procedure generation, and an Exo-specific compounding track
  • analyse-agentic-system — promoted the system-first workflow with mandatory proportionate memory/context and epistemic lenses; now owns collection/schema design and source-regeneration migration, including the parked Scroll/context-operation follow-up
  • epistemic-architectures — comparing six systems (Commonplace, Eigenius, ScienceFlow, AI Research OS, a private research-ontology draft, and ARC); ARC failed the system-level participation × containment 2×2 unchanged and moved the working comparison to route-specific target, timing, force, and epistemic-versus-operational authority
  • popperian-maintenance-episode — four worked Popperian-maintenance episodes and the 23-run validation series for the machinery they produced (ADR 066). The series verdict: mode conversion is rare because mode landings require mode-appropriate warrant, and counterexample-shaped defeats route scope and category repairs instead. The genre-drift cohort question is closed and refuted; the maxim reconciliation and the episode record's disposition are what remain
  • natural-language-theory-human-agent-contribution — attributing the human and agent interventions behind the natural-language-theory warrant note, with frozen pre-revision evidence and an occurrence/revision-surface/compounding analysis
  • writing-as-thinking-process-transfer — harvesting the still-unincorporated ideas from the four 2026-08-10 writing/thinking essays into Commonplace process changes under a discriminating-test-before-build rule; backlog covers premise-decomposition review, counterexample-scope FIX routing, value-of-information reading, a stance-reversal operator, and a false-precision anti-gate, plus the two promoted conjectures' open tests
  • continual-harness-governance-experiment — designing a matched test of whether Commonplace-derived control, warrant, recovery, and artifact-lifecycle mechanisms improve reset-free harness adaptation without importing a compounding claim or presuming proposal selection
  • dsw-talk — preparing a 35-minute Data Summit Warsaw practitioner talk: one core hybrid-system claim, four engineering lessons, a triage of KB material into included/compressed/cut, and an evolving visual spine that closes on self-hosting
  • asisas-2026-talk — 10-minute HTML slide deck for the ASISAS 2026 retained-adaptation paper, updated to the KB's natural-language terminology and the two-axis derivation of representational form
  • agent-runtime-design — deriving what an agent runtime must provide, starting with capability requests, scoped grants, and durable suspension for approval, while separating runtime guarantees from CLI, TUI, API, and host-application control surfaces
  • reflective-improvement-divergence — investigating when open-ended improvement search becomes revision drift, oscillation, moving-criterion instability, or operational non-termination, and what episode-closure rules let a reflective system return to object-level work without pretending it has converged
  • self-revision-design-space — explaining, in plain language first, aspect-bounded builder-loop reach: experimental pathways revise different roles and code while leaving different governing machinery supplied, Commonplace partially retains a human–agent redesign path, and the theoretical Gödel machine internalizes broad redesign behind a proof requirement
  • agent-curiosity-and-structural-coherence — testing whether locally acceptable but globally misplaced code and prose arise from weak role-model activation, anomaly-to-subgoal transition, structural candidate search, or global selection rather than treating “lack of taste” as an explanation
  • execution-channel-compatibility — cataloguing how operating system, shell, agent runtime, environment inheritance, and tool availability affect executable instructions; compilation is one option alongside runtime environment propagation, dispatch shims, portable entry points, paired procedures, and standardized execution environments
  • system-contract-consistency — seven audit findings remain open at baseline commit 6660bd2a; I1/I2/I3/V1 form one installed-product program, T1 is transferred to a dedicated owner, and C1/F1/S1 remain resolved
  • tag-contract-convergence — owns the redesign extracted from T1: semantic/root foundation and exact resolver, membership-consumer convergence, canonical heads and installed migration, with source-family cleanup and agent-navigation evidence kept separate
  • description-length-optimization — determining the shortest description allowance that preserves correct read/skip decisions across plausible hits and large scoped slices, then deriving the validator policy from retrieval quality and an explicit pointer-context budget
  • self-improvement-cluster-operationalization — turning the self-improving-systems cluster into methodology that guides Commonplace's own changes: close the theory's ambiguities first, then audit existing instructions and behavioral-authority artifacts (code, type specs, validators, contracts) against it; also decides the authority-path mix (wired, user-invoked, link-mediated)
  • connect-report-mining — mining the 45 connect reports from the last two weeks plus kb/log.md for recurring synthesis/gap patterns no single connect run surfaces
  • chatbot-goal-state — whether the computational-model notes need a second shape besides the goal-fixed tool loop, for conversations where the human's later messages revise the goal itself rather than supplying tool output; benchmark-construction implications are a downstream thread
  • db-native-reflective-system — what a complete DB-native content/type/link/review schema would need for a hypothetical Commonplace-like reflective self-improving system, starting from the freshness store as a skeleton; does not re-litigate Commonplace's own schema-substrate decision
  • theory-methodology-derivation — the two-layer theory↔methodology pattern (derived fast path, fallback to the generator, promotion by matching) and whether "derivation" should restructure the distillation vocabulary; framings from cognitive architectures, inductive bias, and effective theories in physics
  • freshness-module-review — code review of src/commonplace/freshness/; generic acceptance was withdrawn under ADR 065, while latent CAS/normalization asymmetries and a selector that re-hashes each criterion once per note remain
  • extensible-controlled-vocabularies — designing how code-enforced vocabularies become open-ended per installed KB while staying validator-checkable; source genre now has a severity-warn floor on the authoritative ingest, but its recurring-value/lens extension path and source-tier remain open
  • authority-ranking — testing whether source authority is a linear rank at all (partial order, domain-conditional, time-varying, non-additive under independence) and what consumers a ranking function actually has; framework-side companion to the epistack author-dossier casework
  • lineage-mechanisms — designing one derived-artifact lineage vocabulary across multiple storage weights; review keeps its purpose-built DB while generic lineage state stays deferred until a second churning mesh earns it
  • linking-contract-consistency — reconciling stale linking ADRs, collection-local grammars, asymmetric label directions, reciprocal-link procedures, semantic validation, and inbound-link delivery while leaving derivation lineage to the lineage workshop
  • linking-foundations — grounding authored links in argumentation, inferentialism, explanation and mechanism, discourse/relevance theory, and semantic-memory research; separates assertion, reader function, strength, revision consequence, and derived association before further vocabulary decisions
  • 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
  • artifact-freshness-and-referential-checks — building artifact-neutral dependency baselines and reverse selection on the shipped review and full-pass version cases; the second consumer decides what comparison/guard code deserves extraction
  • 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
  • runner-execution-profiles — cataloguing model, effort, runner, isolation, and escalation policy across skills and delegated roles, then defining configurable Codex/Claude execution profiles for faster and cheaper workflows
  • 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
  • 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; the proposal disposal half shipped 2026-07-25 as ADR 056 (extract, then archive out of the frontier as a link sink), leaving note and source-snapshot retirement as the blocking gaps
  • 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

Workflow Namespaces

  • multistage — grouping namespace for skill-managed multistage writing runs; active runs are listed individually above

Complete file listing (generated at build time)