The Assembled Verb: repertoire, assembly, and the authorship of a verb

Domain operations already compute, and programs already sequence and coordinate them: in two well-regarded reference systems, the authors' own test suites still exercise their domains once store, bus and test double are removed. This paper is about what neither fact supplies. Executing a sequence consumes capabilities; it does not thereby produce one — before the run there are three capabilities, and after the run there are the same three. The paper reports an arrangement in which assembly constitutes the composition itself as a verb of a subject — one recorded definition whose content is the operations — and measures the difference that makes: performed twice with different arguments, the journal holds one definition and two invocations, the second stating nothing about the verb's constitution. Its recorded constitution is distinguishable by a criterion any record can be asked — how many of the constituting statements does the record contain, and does replaying the record alone bring the outcome about again? — measured across an event-sourced coordinator, durable execution on a third-party engine, a trace, and the constituted verb: only the last both contains and re-performs, and what separates the strongest rival is how much stays ambient in code. Command/query modality is attributed at assembly, per performance, rather than inherited: one body, held fixed, leaves no history exercised as a query and is journaled, replayable, performed as a command. A census of the corpus's 72 named artifacts, under published population and coding rules, shows that in neither system did the plane appear of its own accord; no wider population is claimed. Sixteen neighbour families are conceded by name, and what none of them was found to hold together is the conjunction: a subject-owned record of a definition and its exercises, constituted from repertoires the subject does not own, with modality — including what counts as the subject's history — attributed at the plane of assembly. A prototype of a few hundred lines realizes the same conjunction on a third-party engine, and the record's growth, replay time and throughput are measured against the direct baseline. The paper is analytic in Gregor's (2006, Type I) sense: it prescribes nothing, and its distinctions are stated as propositions over a core operational calculus, with the labs as conformance checks. Assembly turns the use of capabilities into a capability of a subject — and once the composition has a place of its own, continuity no longer has to be authored into its constituents.