Adr Directory

Type: kb/types/index.md

← Parent

• 002-inline-global-types-in-writing-guide (adr) - Decision to inline note and structured-claim templates into WRITING.md so the agent gets type structure and writing conventions in a single hop — eliminates one read for the two most common note types
• 003-connect-skill-discovery-strategy (adr) - Design options and scaling strategy for how the connect skill discovers candidate connections — index-first with semantic search backup, and what changes when the KB grows
• 004-Replace areas with tags (adr) - Replaces the areas frontmatter field with freeform tags and restructures index pages to have both curated and generated sections, decoupling navigation from comparative reading
• 005-quality-check-placement (adr) - Where quality checks belong — WRITING.md, validate, the experimental review system, or recurring tasks — based on cost, false-positive tolerance, and whether the check gates note creation
• 006-two-tree-installation-layout (adr) - Decision to split installed projects into two directory trees — user content in kb/, framework in commonplace/ — with operational artifacts copied to kb/ for fast agent access and methodology kept in commonplace/ as fallback
• 007-reports-directory-for-generated-snapshots (adr) - Decision to create kb/reports/ for generated, regenerable analytical snapshots — distinct from workshop (temporal work-in-flight) and notes (durable claims)
• 008-Stdlib-only core scripts (adr) - Core scripts use only Python stdlib by defining a strict frontmatter grammar that a regex parser handles completely
• 009-Link relationship semantics (adr) - Adopts a fixed vocabulary of link relationship types (extends, grounds, contradicts, enables, exemplifies) borrowed from arscontexta and adapted for agent navigation under bounded context
• 010-review state should move to sqlite once reviews leave git and accumulate operational metadata (adr) - Accepts SQLite as the canonical store for review state once review artifacts are removed from git and start carrying selector and ack metadata rather than just human-readable prose
• 011-Notes must be accessible to external readers (adr) - GitHub Pages commits the KB to external readers who lack CLAUDE.md context — KB vocabulary needs inline glosses and definition links on first mention
• 012-types-for-structure-traits-for-review (adr) - Types define structural requirements checked by validation; traits route semantic review gates; the traits-only semantic boundary is amended by ADR-038/041, which make both contracts conformance gates
• 013-skills-first-delivery-with-core-local-type-split (adr) - Historical decision to move skills to top-level sources, keep KB Goals always-loaded, split types into core and local, and use dynamic type discovery for practitioner-defined types
• 014-scripts-as-python-package-one-tree-model (adr) - Decision to ship operational scripts as an installable Python package (llm-commonplace), replace the two-tree layout with a one-tree init model, and use scaffold symlinks for zero-duplication seeding
• 015-standardize-authored-type-definitions-on-json-schema (adr) - Accepted decision to replace the custom type-profile DSL with authored JSON Schema over a parsed note document model
• 016-custom-types-use-template-instruction-pairs (adr) - Accepted decision that specialized and practitioner-defined types use separate template and instructions files; the former WRITING.md loading assumption is superseded by ADR-017
• 017-collection-md-is-the-register-convention-boundary (adr) - Accepted decision to use collection-level COLLECTION.md files as the register convention boundary while keeping types structural and allowing mixed-register collections
• 018-Types are path references to instruction docs (adr) - Replaces enum type names and three-file type bundles with path references to one authoring contract plus a sibling schema, removing discovery ambiguity and special-case write routing
• 019-Collection-owned link vocabulary with per-destination outbound rules (adr) - Each COLLECTION.md owns its outbound-linking rules per destination collection, selecting from a shared authoring catalogue; the connect and write skills read COLLECTION.md directly, and the compiled register-by-register topology is retired
• 020-Link vocabulary: add contrasts and mechanism; declare directional asymmetry (adr) - Adds contrasts and mechanism to the theoretical-register default template on corpus evidence, and declares the directional-asymmetry principle that governs how the theoretical vocabulary is authored and read.
• 021-Ship library content under kb/commonplace (adr) - Ship Commonplace library content under kb/commonplace/ so user collections at kb/notes/, kb/reference/, kb/instructions/ stay user-owned while the shipped library sits alongside as a read-only dependency.
• 022-active-vocabulary-and-write-path-first-mentions (adr) - Accepted decision to define active vocabulary in AGENTS.md while making first-mention glossing a cp-skill-write authoring behavior
• 023-Quote-anchored citations for code-grounded reviews (adr) - Permits reviewed-commit-pinned verbatim quote anchors in code-grounded reviews; write time resolves quotes against the checkout while standing validation checks only retained shape
• 024-Schema severity is per-constraint, fail by default (adr) - Moves schema finding severity from instance-path inference to each constraint, failing by default with explicit warn opt-downs and optional stable rule identifiers
• 025-Complete generated indexes are build-time only; agents read curated heads plus scoped rg (adr) - Complete generated listings move to ProperDocs build time; agents discover through curated heads plus scoped path-and-description searches with a 50–250-character soft description warning
• 026-Split index into a committed tag-readme type with enforced marks (adr) - Creates the committed tag-readme type with byte-weight gates and validator-derived complete/covered_by marks, separating meaning, enforcement, and maintenance across their operative surfaces
• 027-Package scaffold assets without source-tree symlinks (adr) - Replaces source-tree scaffold symlinks with explicit Hatch wheel force-includes plus source-checkout fallback resolution for Commonplace packaged scaffold assets
• 028-Design proposals live in kb/reference/proposals; ADRs record implemented decisions only (adr) - Routes unadopted system designs to kb/reference/proposals, reserves ADRs for implemented decisions, and splits YAGNI gaps from transferable theoretical insights
• 029-Review execution unified on (note, gate) pairs (adr) - Review execution is unified on note-gate pairs; note and gate packing share one protocol, while partial salvage was later removed
• 030-Harness-facing seams: batch prepare/ingest endpoints and runner adapters (adr) - Superseded historical decision: batch prepare/ingest endpoints and runner adapters were replaced by queued jobs and parent-dispatched workers
• 031-Review state uses invocation-owned review pairs (adr) - Superseded historical decision: review state moved to invocation-owned note-gate pairs, later simplified into current all-or-nothing review jobs and review pairs
• 032-Review freshness uses DB snapshots, not Git (adr) - Review freshness is based on SQLite-owned note and gate snapshots, separated from Git and from review execution; the model-side review key is a frozen model_partition
• 033-Honest review state behind a versioned migration substrate (adr) - Superseded historical decision: honest queued/running review state and a general migration substrate were reduced to queued/completed/failed jobs; a later release added one narrow v4→v5 migration
• 034-Queued review jobs and execution provenance (adr) - Superseded historical decision: queued review jobs stored freshness identity separately from nullable parent-dispatch provenance before finalization-time provenance replaced claim/running
• 035-Review jobs finalize all-or-nothing with derived artifacts (adr) - Review jobs use derived artifact paths, finalization-time provenance, strict per-kind result parsing, and all-or-nothing acceptance
• 036-Review acceptance is current state, not append-only history (adr) - Review acceptance stores only the current accepted baseline per note/gate/model key and prunes superseded review evidence inline
• 037-Promote skills into runtime surfaces by copying (adr) - Replaces symlink and Windows-junction skill projections with real copied directories in commonplace-init, migrating legacy links to copies on re-init
• 038-Type-conformance reviews use the type spec as the gate (adr) - Type-conformance review pairs put the note's type spec on the gate side of the existing (note, gate) freshness key, so a type edit stales exactly its cohort with no new storage semantics
• 039-Tool visibility is package-owned and git is never invoked (adr) - Replaces per-path git check-ignore visibility and git-mv relocation with a package-owned name-based visibility contract; commonplace commands never invoke the git binary
• 040-scripts/ is the accumulation substrate for ad hoc tooling (adr) - scripts/ is named the committed home for reusable ad hoc tooling, distinct from throwaway python3 heredocs and the installed package, with a cleanup norm and a promotion signal
• 041-Collection-conformance reviews use COLLECTION.md as the gate (adr) - Collection-conformance pairs put the note's COLLECTION.md on the gate side of the existing (note, gate) freshness key, matching the enforcement type contracts got in ADR 038
• 042-Register becomes a default profile under open-ended text contracts (adr) - Register retires as a closed taxonomy; COLLECTION.md must declare a text contract, and theoretical/descriptive/prescriptive persist as named default profiles in an open, worked-case-gated library
• 043-Review state separates completion, outcomes, and freshness baselines (adr) - Review schema v7 separates job grouping, pair completion, verdict outcomes, execution failure, and snapshot-pinned freshness baselines under one cross-surface vocabulary
• 044-User verification replaces global note status (adr) - Ordinary notes drop the fused global lifecycle enum and expose only optional committed human verification, while specialized local statuses remain type-owned
• 045-Source genre is a single open field on the snapshot (adr) - Source genre becomes one required open-vocabulary genre field on the snapshot; the ingest-report drops and rejects source_type, and snapshot tags return to optional topical duty
• 046-Verbatim quotes are validated against their cited source (adr) - commonplace-validate resolves every verbatim-marked quotation against the source it links; a false verbatim claim fails, and unresolved warns only where the convention is demonstrably in use
• 047-Type specifications use normal deterministic validation (adr) - Type-spec documents run through ordinary note validation, with a type-owned referential rule resolving their declared schemas; the former workspace sweep is removed
• 048-Imperative type rules dispatch by canonical path (adr) - Imperative deterministic type rules dispatch by canonical path-valued type identity, preventing same-named local types from inheriting framework rules
• 049-Validator resolution returns scope and loads types directly (adr) - Validation target resolution now returns paths with explicit collection scope, while type resolution and type-spec checks share direct definition loading
• 050-Validation runs share parsed artifacts and collection indexes (adr) - Validation is evaluated by a library-owned run that parses target artifacts once and shares collection indexes across anchored checks
• 051-Full-pass packets own guarded captures and resolutions (adr) - Full-pass packets retain guarded start-state captures and authoritative asynchronous disposition resolution
• 052-General freshness store, review-first migration (adr) - General artifact freshness lives in commonplace-store.sqlite; review is the first target adapter over file-text inputs and review-pair targets
• 053-Retire distillation without a successor term (adr) - Distillation is retired with no successor term: theory lives in the two-layer structure note, lineage labels carry the derived/abstracted boundary, the discovery lifecycle owns ampliative traffic
• 054-Add adapted-from and operationalized-from lineage relations (adr) - Adds adapted-from and operationalized-from lineage relations, amending ADR 053's no-successor-term decision with the composite operation it left unnamed
• 055-Explanatory-reach replaces bare reach as the technical term (adr) - The Deutsch-derived quality property is carried corpus-wide by the rare compound explanatory-reach; bare reach returns to ordinary English, with two note retitles and one brainstorming rename
• 056-Adopted and retired proposals archive out of the frontier (adr) - Adopted and retired proposals move to a link-sink archive after extraction; provenance becomes a title tag, so ADRs from 2026-07-25 must carry a Considered alternatives section
• 057-Articles use an editorial profile and excluded drafts (adr) - Articles use a promoted editorial profile, keep drafts under a site-excluded collection subtree, and publish immutable dated bodies through ProperDocs
• 058-Directional identifiers use the source as subject (adr) - Adopts source-as-subject grammar for directional link identifiers and replaces evidence with evidenced-by and is-evidence-for
• 059-External is a reserved outbound destination (adr) - External is a reserved outbound destination that a source collection must explicitly authorize, without making the open web a collection or a connect-search surface
• 060-Rationale becomes rests-on and off-pattern grounds are reclassified (adr) - Replaces rationale with source-as-subject rests-on, reclassifies every off-pattern grounds edge, and gives the global type surface collection-owned link authorization
• ADR 021 appendix: Option E path audit (note) - ADR 021 appendix auditing hardcoded kb/ paths in shipped content and showing why the kb/commonplace namespace preserves more links than cp-prefixed collections
• ADR 021 appendix: shipped-content namespacing design space (note) - ADR 021 appendix enumerating shipped-content namespace options, read-only conventions, path translation, skill-root resolution, and collection scaffolding