C.2.P:4.2.0 - Cross-Side Fields That Must Stay Split

These fields are current episteme-publication precision vocabulary for DRR, architecture, and pattern-drafting work. They exist to prevent one sentence from mixing FPF-side use-boundary, project-side records, actual work or action, method selection, carrier access, and authority records. They are local recovery aids, not FPF kinds, not record kinds, and not a universal record ontology. Each field closes only by naming the FPF kind named by value, relation record, relation phrase, project-side FPF kind and reference named by value, or explicit non-use disposition that is current in the sentence. The same local-aid rule applies to neighboring field names such as sourceRelationClass, explanationSourceRelationClass, comparativeRelationClass, representationValidityUseBoundaryValue, allowedUse, misuseRisk, and worldContactPolicy: they help record a local recovery or reader-use boundary, but they do not become kinds. These local fields do not instantiate evidence, gate, assurance, work, commitment, speech act, decision, release, authority, representation kind, world-contact kind, or policy kind. Read allowedUse as a local reader-fit field under declaredUseBoundary, not as permission, evidence relation, or authority.

Term	Current interpretation	Must not mean
`FPF` as episteme	The whole `FPF` is a claim-bearing episteme with publications, parts, patterns, pattern sections, `DRR`s, and companion publications and documents named for source, evidence, architecture, or review use.	A file, repository, taxonomy, pattern-language metaphor, or packet-local summary by default.
FPF pattern	A named FPF pattern: a reusable episteme species that gives action guidance for a problem situation. It is applied in a current problem situation.	Any recurring arrangement, procedure, method call, route, cluster label, checklist, or document named only as a citation or source-finding pointer.
pattern section	Either a part of the pattern episteme or a bounded `PublicationUnit` of that pattern publication, depending on sentence function. State which one matters when the distinction carries a claim.	Independent pattern, file location, generic locus, or record with named authority-reference relation.
accepted campaign `DRR`	A campaign decision source that states accepted content decisions for one campaign.	A pattern, current-authority summary, open-ended plan, review log, or replacement for pattern text.
`relationClaimSlice`	Empty, or a local note that `A.6.P` relation precision is current for one sentence. It must name the relation problem being handled: relation, comparison, dependency, support, sameness, grounding, mapping, endpoint claim, or cross-context bridge claim. The recovery then names `RelationKind`, `QualifiedRelationRecord`, relation phrase, candidate-set note, or bridge card when current, with typed endpoints, slots, qualifiers, and scope.	Dictionary replacement, one new umbrella kind, a bare `RelationKind` standing in for a relation record, a generic relation slot, support relation by default, or a list left as the final answer.
`declaredUseBoundary`	The declared use boundary and blocked use outside that boundary when the sentence says what declared use boundary applies to a use, act, claim, or reliance. Use A.6.B when the boundary claim needs L-, A-, D-, and E-claim separation.	Generic supported use, permission-by-appearance, or visual cue or readability cue treated as use-boundary.
`projectSideFPFRef`	The project-side FPF kind and reference named by value when a publication, display, cue, or explanation is treated as a project-side source for work, evidence, gate, constraint, adjudication, decision, commitment, method, action invitation, assurance, or engineering justification. The field points to that kind and reference; use the relevant FPF pattern for the relation and its checks.	One slot accepting records, actions, methods, carriers, evidence, gates, decisions, assurance, and engineering justification interchangeably.
`rejectedOverread`	A local field naming the tempting interpretation, evidence, gate, work, permission, approval, commitment, release, safety-proof, engineering-justification, or pattern-entry interpretation that must not be granted by resemblance alone. It is valid only with the recovered relation or subject-specific source, scheme, scope, practice, or use that blocks it. It is not `U.Kind`, not a record kind, not a review-finding kind, and not a moralized defect class.	A general risk slogan, review finding, moralized “bad use”, vague misuse label, or reusable FPF kind.
`useBoundaryTargetKind`, `useBoundaryTargetRef`	Source-local helper fields. Prefer `declaredUseBoundary`; if these fields appear in material being repaired, they name the kind and reference inside `declaredUseBoundary`, not an `A.6.P` relation slot.	A generic `supported use`, document capability, “claim outside the declared boundary”, review permission, or untyped pattern assignment.