Commonplace as an instrument

Type: kb/types/note.md · Tags: foundations

Commonplace's immediate application is an agent-operated knowledge base. The KB is not the boundary of the program. It is the first worked case in which the design's theories — about retrieval, representation, review, validation, and self-modification — meet real operating constraints together, rather than being invented in the abstract and checked one at a time.

Everything here is indexed to one objective: more useful and better-warranted knowledge work per unit of human judgment spent. Not automation.

Two things follow from treating the KB as an instrument rather than as the product.

Use tests composition

The components must compose into sustained knowledge work — types, collection contracts, validators, review pairs, freshness baselines, and skills running against each other on a live corpus, not each demonstrated on its own bench. Where they fail to compose, the failure is evidence against the design theories that produced them, not merely a defect ticket.

The traced instance is the tag-readme change. An index head grew too large to support its completeness claim; ADR 026 split the type and made complete an enforced mark, carrying one decision into instruction, schema, validation, and rendering; the validator then rejected artifacts it had previously accepted, and the symbolic check caught a tagged member that the documented rg recipe had missed, forcing the natural-language recipe to be corrected. The commit-by-commit trace and the improvement-loop reading hold the detail; the classification states what it establishes about reflectivity.

What it establishes about composition is narrower. It is one pathway, and use exercises the whole configuration at once and reports one bit about it, so use tests a decomposition only locally. Surviving here licenses replay in this repository. It does not license the rule.

Retained rationale is the part that could travel

The route out of that limit is not more use; it is rationale retained at design time, which is what gives a transfer claim an antecedent to test. Derivation and inheritance give a decomposition's scope claim its starting warrant — warrant, not earning — and the repository carries one worked instance of each.

  • Derived. Representational form generates its three categories from two axes — whether a defined consumer assigns consequences to the artifact, and whether the content sits in a localized unit. Its Derivation section states the axes, marks the fourth cell as unoccupied in this domain rather than impossible, and derives the read/test/probe inspection rule instead of stipulating it per form.
  • Inherited. Reflective system takes causal connection, self-representation, and theory-relativity from Maes 1988 with the Smith 1984 lineage behind it, carried as derived-from edges to the source ingests. Its "Provenance and departures" section separates the purchase from the local extension, naming retrieval-as-causal-connection as Commonplace's own with no source behind it.

Both instances are auditable: a reader can see which parts were bought and which were added here.

What the repository does not have

The rationale surfaces are distributed across workshops, proposals, ADRs, collection contracts, types, validators, and git history, and they do not guarantee end-to-end continuity. Current proposal and ADR contracts require no stable decision identities, no provenance links, and no backlinks from implemented machinery. Later recovery depends on what an author explicitly carried forward or connected.

So the honest statements are these.

  • Commonplace does not retain the rationale behind each mechanism. Two definitions carry a worked provenance record. The rest of the repository's mechanisms carry whatever their authors happened to write down, at whatever fidelity, with no contract requiring more.
  • Disciplined transfer has not been demonstrated. Both instances were authored inside the system that states the claim and assessed by nobody outside it. They show that provenance is recordable and that departures are auditable once recorded — not that recording it produces better designs.
  • Retained-but-unfaithful rationale is worse than absent, and nothing in the repository has yet tested faithfulness by intervention. A rationale that has never been contradicted is not thereby a rationale that holds.

The missing evidence is already named, as the two open TODOs in design rationale management: a worked reuse comparison showing how preserving inherited constraints, local requirements, and free choices changes a later transfer judgment, and one ordinary Commonplace decision traced end to end from originating constraints and alternatives through its chosen surface and any later promotion.

What would change the status

This is a defensible position, not a demonstrated one. It becomes demonstrated on evidence of this shape:

  • Close the two TODOs with outcomes, not records. An end-to-end trace that shows a reader finding the lineage — including across skipped stages — and a reuse comparison that reports whether the retained distinction actually changed a transfer judgment rather than merely being available to it.
  • An outside assessment. Someone not operating this repository reuses a Commonplace decomposition, checks against the retained rationale whether the constraints still bind, and reports whether that check discriminated better than rebuilding and seeing.
  • A faithfulness test by intervention. Vary a stated force and observe whether the decomposition's fit degrades as the rationale predicts. A retained force that survives being varied is the first real evidence that the record is about the design rather than about the author.
  • Composition failures attributed back. More than one operational failure traced to a named design theory, on components not co-designed for the trace. One pathway is not a sample.

Until then, treating the KB as an instrument is a claim about what the application is for, backed by two worked provenance instances and one composition trace — and no more than that.

Relevant Notes: