E.4.DPF:4.0.1 - Return suite and guide proposals to their own decisions

Suite constitution and each inclusion or removal are separate decisions under E.4:4.2 and E.4.PFAD. Belonging states collection membership between one DPF product series and the Suite. State field coverage, edition adequacy, dependency or compatibility, maintenance, publication or access, recommendation, and Guide use through their own direct predicates and grounds. A shared carrier, Guide entry, author, or locator may report membership but does not establish it.

An author may propose that a DPF product series join or leave a Suite, or that a Guide entry use one of its results. Keep inclusion and removal as proposals until the Suite decision takes effect. Return those proposals to E.4:4.2 and E.4.PFAD, where the ecosystem purpose, the rule for which product series may belong, inclusion and removal rules, identity through change, later review and retirement, and exposure are decided; state maintenance separately when it obtains. Keep a proposed Guide entry separate until the Guide product’s content or refresh decision selects it. Make and check the entry’s direct claims about DPF results and sources under the patterns that define those claims. A state with one product series or none follows the Suite’s explicit preservation, restoration, review, or retirement rule; a DPF edition does not decide that state from inside itself.

For a dependency, name the dependent and relied-on editions, relied-on content, receiving use, and invalidation or reopen fact. For compatibility, name the edition pair, overlapping use, difference or interface, impact, and reopen condition. Until those facts satisfy E.4.PFR, keep the proposed use, constraint, or question. Suite belonging and Guide navigation report their own collection and navigation claims. The current FPF treats product series and the Suite as continuing collections; the complete A.1 test remains the route for any holon or constructive-part claim.