Proposals

Finished but unadopted designs for the Commonplace system. A proposal describes a design object — the problem, the option space, the forces, the free choices — without claiming the system works this way or deciding that it should.

This directory is the frontier: every file in it is a live, undecided design, so listing it answers "what is still open" without a filter. Decided proposals are in archive/.

This README is navigation only; it states no rules (ADR 084). What binds a proposal is in two places:

Multi-repository analysis

Strategy and measurement

  • Reusable commitment support across kinds of knowledge work — Commonplace's strategy as a testable conjecture in configure(G, K_P) form: support built for theory building generalizes to other kinds of knowledge work at lower total cost than per-kind tools; three options for how G comes to exist, and the one comparison that would support or defeat it.
  • Cost-per-yield records for routine controllers — give each routine search controller a record of yield and cost that states the context regime it ran in, so controllers in unattended pipelines can be compared on cost as well as yield.

Lifecycle at a glance

Workshop (kb/work/, active exploration, closes) → proposal here (finished, undecided, waits) → ADR (decided and implemented) — or retirement, when a later decision forecloses it — or withdrawal, when its problem or trigger lapses with no decision. Partial adoption keeps a proposal here with only its undecided part. Procedures:

Decision records: ADR 028 (this directory), ADR 056 (archiving), ADR 084 (where the rules live).


Complete file listing (generated at build time)