Proposals Directory

Type: types/generated-index.md

← Parent

Subdirectories

Files

  • A reader-facing banner for user verification (design-proposal) - Proposal: surface committed user verification at the point of reading through a standardized Markdown banner without turning absence into a review or truth verdict
  • Ablation baselines for the declared objective (design-proposal) - Proposal: measure the declared objective — useful and warranted work per unit of human judgment — by running matched repository tasks under ablated conditions (no curated theory, no review, episodes only, stronger bare model)
  • Artifact function as a routing field (design-proposal) - Proposal: whether an artifact_function declaration should expose a document's intended whole-artifact job for writing and review routing without asserting atomicity
  • Automated note refinement as a search over a fixed source bundle (design-proposal) - Proposal: build the automated note-refinement loop on a source bundle that emits a set of notes, not a single identity-stable note — reframing non-convergence (split, drift, kill) as search outcomes
  • Backlink surfacing (design-proposal) - Proposal: surface inbound links through build-time web rendering for humans and on-demand inversion for agents while allowing useful reciprocal links, not mandatory mirroring
  • Bidirectional codification as a comparative test (design-proposal) - Proposal: promote bidirectional codification from design guidance to a comparative conjecture, tested by evolving the same task stream under natural-language-only, symbolic-only, one-way promotion, and bidirectional codify-and-relax regimes
  • Calibrating semantic gates against labelled fixtures (design-proposal) - Proposal: require non-leaking known-case regression before a semantic gate can advance, and reserve live detection-rate claims for separately sampled field calibration
  • Channel-compiled instruction artifacts (design-proposal) - Proposal: resolve execution channel at install time so an agent reads one literal procedure, extending build-time generation from paths to shell and command form
  • Checked inline blocks for shared instruction text (design-proposal) - Proposal: reuse natural-language authoring mechanics in specialized writer prompts through literal inlining backed by deterministic source-to-copy checks
  • Collection-as-artifact freshness (design-proposal) - Proposal: register collection-maintenance targets with collection-text inputs for casebook-wide staleness without per-file dependency edges
  • Decisions bind their consumers through site back-pointers (design-proposal) - Proposal: make a recorded decision reach the operations it constrains by having each ADR declare the artifacts it binds and each bound artifact carry a checked back-pointer, rather than a hand-maintained decision index
  • Deterministic write-context assembly (design-proposal) - Proposal: whether code should assemble a target's fixed authoring context while keeping named input roles closed rather than opening a generic provider mechanism
  • Factored dependency pairs for review freshness (design-proposal) - Proposal: keep review dependencies factored as two-input pairs where that shape fits; type and collection pairs and cohort ack are shipped while a review target with more than two inputs remains
  • Gate learning from accepted edits (design-proposal) - Proposal: learn review gates from accepted note edits, with candidate mining, usefulness tracking, lifecycle promotion, and budgeted loading. Atomic gates shipped; learning has not
  • Generalized validation invalidation and imperative extension (design-proposal) - Proposal: generalize validator invalidation or imperative type extension only after explicit selectors and local mark cases prove reusable machinery
  • Keyword tags without heads (design-proposal) - Proposal: a second, weaker kind of tag — a keyword with no head, no page, and no marks, for scoped search only — declared per collection; set aside by ADR 089 on YAGNI grounds until search-only tagging shows a need
  • Model partition registry (design-proposal) - Proposal: introduce a model partition registry for review validation, aliases, and runner defaults without making the registry the review identity
  • Normalized autonomy and revision comparison fields (design-proposal) - Proposal: normalize autonomy and revision findings for cross-system comparison after source-based reviews establish useful distinctions
  • Periodic connect-report mining (design-proposal) - Proposal: mine connect reports on a recurring cadence as a bulk-operation pipeline, automating the noticing-to-candidate triage step connect and kb/log.md leave unattended
  • Repair dispositions for defeated claims are an epistemic policy with an option space (design-proposal) - Proposal: the undecided remainder of repair-policy design after ADR 066 — declaring repair policy in an installation's local collection contract, and freshness-store drift tracking for idealization pricing attestations
  • Review configuration object (design-proposal) - Proposal: give commonplace.review a ReviewConfig for review scan roots, gate and artifact locations, and database path with project overrides, without introducing a global ProjectConfig
  • Routine bilateral isolation for literature assessment (design-proposal) - Proposal: decide whether prospective matched evidence should promote bilateral isolation from a conditional diagnostic to a routine literature-assessment control
  • Structured-output codec for the review protocol (design-proposal) - Proposal: make review output a pluggable codec, with sentinel markdown today and schema-validated structured output when harnesses expose it
  • Tag maintenance and derived browsing (design-proposal) - Proposal: test temporary topic groupings and reviewed tag-maintenance suggestions before changing Commonplace’s canonical tag structure.
  • Trajectory-aware evaluation of transforming agent workflows (design-proposal) - Proposal: compare blinded output-only and trajectory-aware judges on transforming agent workflows before adding trajectory evaluation to closure
  • Write-time vocabulary collision controls (design-proposal) - Proposal: mechanical controls for the one-term-one-sense invariant — reserved-term registry, slot-escape lint, coinage collision screen, naming-review gate, and clausal-binding link check