PM-FLT-0070

A Component model MUST compose imported Object models by filling proposition positions that those models left empty. A Component MUST NOT modify, weaken or replace a Filter defined in an imported model, and an imported model MUST remain byte-identical under composition.

Non-normative. The mechanism is concrete in the description and worth stating plainly, because it is more specific than "refinement" on its own. The Filter Has Instantiated Job Application selected is declared in the Job Application Object model with only its Object position filled. The Recruitment Management Component model then supplies the Subject and predicate for that same Filter. Nothing in the Object model changes; the composition lives entirely in the parent.

Refinement is therefore always a strengthening. Filling the Subject and predicate adds a conjunct, so a composed Filter is satisfied by a subset of what satisfied the original — "the new Job Application cannot exist by itself within the Recruitment Component. It needs a Created Candidate as Subject related by the predicate has Job Application" (PAT:us9378071b2#para-2103).

This resolves the collision recorded against the kernel design: the kernel proposed refinement-only Filter extension and the blog appeared to say a Component replaces constituent behaviour. The patent supports the kernel. The blog sentence is marketing compression of the same mechanism, not a second design.

The blog's own figures say the same thing, and say it more clearly than its prose. Two of the three Filter tables are the same seven Filters before and after composition. In IMG:filter-and-operations-separated-models the Operation cells of rows r6 and r7 are empty and the Filter names are bare state names. In IMG:filter-and-operations-united-in-the-entry-managhement those cells are filled — and everything the Entry Management Component contributes is drawn in red, while everything inherited from the Object models stays black.

No black cell differs between the two tables. Composition is purely additive, in the figure, cell by cell. The Model column for every extended row reads the literal string "Extended in Entry Model" — the blog's own figure calls it extended while the blog's prose calls it replaced. Prefer the figure: it is the more specific artefact, and it agrees with the patent.

The engineering consequence is the one the withdrawn PM-FLT-0050 argued for: an Object model verified alone stays valid once imported, so conformance tests compose and impact analysis is tractable.

---