#Concept-Set Table Construction

F.7 · Stable · Part F - The Unification Suite (U-Suite): Concept Sets, SenseCells, and System-Role Kinds and Assignments

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

“Put exact local meanings and already established relations side by side; let the table display the argument, never create it.”

Status. Architectural pattern. Depends on. E.10.D1 Recovering What “Context” Means in Use; F.0.1 Source-Local Meaning Recovery; F.1 Question-Relative Source Selection; F.2 Term Harvesting; F.3 Source-Local Sense Clustering; F.17 for optional exact cells; F.5 Naming Discipline; F.9 for actual semantic relations and their separate bounded-use claims. Coordinates with. F.4 SystemRoleKindDescription; F.6 SystemRoleAssignment and Performed-Work Attribution Check; direct Part C patterns for the compared values; C.16 for characteristics; A.6.9 when umbrella sameness wording must be repaired before a relation is asserted. Aliases (informative). Concept-Set table; comparison grid; Giants’ table.

Intent. Give a reader one compact surface for comparing exact source-local claims, optional F.17 cells, and any relations that already obtain between them. The table also shows the stated comparison or receiving use, direction, losses, evidence, and counterexamples. It makes a distributed argument readable without turning row membership into sameness or permission.

#Keywords

• exact local claim
• optional SchemeSenseCell
• comparison surface
• obtaining relation
• direction
• loss
• evidence
• receiving use.

#Relations

#Content

#Intent & applicability

Intent. Give a reader one compact surface for comparing exact source-local claims, optional F.17 cells, and any relations that already obtain between them. The table also shows the stated comparison or receiving use, direction, losses, evidence, and counterexamples. It makes a distributed argument readable without turning row membership into sameness or permission.

Use this when. Two or more selected sources must be compared for one named question, teaching contrast, designation choice, or receiving use, and prose alone scatters the relevant distinctions.

Do not use this when. One local claim is enough, or no receiving comparison is named. A table is optional. It creates no value, kind, relation, classification, assignment, evidence use, reliance, verdict, or authorisation.

#Problem frame

Cross-source comparison commonly fails through:

1. Silent equivalence: similar labels are treated as one meaning.
2. Loss denial: an actual relation is shown without direction or limitation.
3. Name inflation: a new umbrella label is coined merely because several entries share a row.
4. Cognitive scatter: source meanings, relations, evidence, and the receiving question are separated across documents.

#Forces

#Core idea (didactic)

A Concept-Set row is a didactic grouping for one stated comparison or use. It contains:

• the exact sources and editions;
• each source-local claim, or its F.17 SchemeSenseCell when durable addressability is useful;
• every already obtaining relation that matters here, with direction and declared loss;
• the separate conclusion about the named receiving comparison or use;
• the evidence or direct pattern that supports each substantive claim;
• a counterexample or boundary showing where the comparison stops.

The word set names the entries collected for display. It does not assert that they are one value. A row may show an identity, overlap, ordering, incompatibility, disjointness, or no relation at all, but only because that claim is established outside the layout. F.9 is used only when the actual relation is between distinct local meanings. For every other relation, cite the pattern that defines, constrains, or tests it.

#Minimal vocabulary

• Local entry — an exact LocalSenseClaim or optional F.17 SchemeSenseCell, with its source and edition and effective scheme.
• Obtaining relation — a relation already supported under its direct pattern; it is not inferred from co-placement.
• Direction — which participant is source and which is target when the relation is asymmetric.
• Loss or limit — what the relation or receiving use does not preserve.
• Receiving-use conclusion — the separate claim that judges whether and how the entries and relations may be used for one named purpose.
• Contrast row — a row that teaches a difference or an unresolved comparison and expressly asserts no sameness.
• Characteristic — a comparandum defined by its direct characteristic pattern; a table may display measured or target values but does not define the characteristic.

#The table

Use the smallest columns that make the current argument recoverable:

For a teaching contrast, the relation column may say none asserted and the conclusion may say keep distinct. For an F.9 relation, show its declared relation kind, direction, CL if that relation actually defines one, and loss. Do not compute a row-wide CL or replace the separate bounded-use claim with a table label.

Reading rules:

1. Entries stay local. A cell cites the source’s expression and claim; it is not a translation supplied by the table.
2. Relations stay direct. For each relation, cite the pattern that defines, constrains, or tests it and the evidence supporting the claim.
3. Use stays separate. “These may be compared for this report” is a claim with its own basis, not a property of the row.
4. Unknown stays unknown. A blank or unresolved relation is not an invitation to infer similarity.
5. Loss stays visible. If the limit needs more than one line, link to the underlying relation or evidence rather than compressing it away.

The nickname Giants’ table recalls that comparison relies on prior source work. It signals humility toward those sources, not authority supplied by the table.

#Conceptual construction

• Start from a question. State the comparison or receiving use before selecting entries.
• Bring exact local meanings. Use F.0.1, F.2, F.3, and F.17 only as needed.
• Bring relations, do not manufacture them. Cite the direct pattern and evidence for each relation that matters.
• State the receiving-use conclusion separately. Say what the current comparison permits, with its basis and limits.
• Keep the row small. Usually two to four entries are enough; add another only when it changes the answer.
• Use contrast honestly. When no adequate relation is established, show the difference rather than forcing a unification.

#Invariants

1. Exact entries. Every filled source-local cell identifies the exact source and edition and claim, or an exact F.17 cell.
2. No row-created relation. Co-placement, matching labels, or a shared FPF designation establishes nothing about the entries.
3. Direct relation basis. Every stated relation cites its direct pattern and available evidence; F.9 is conditional, not universal.
4. Separate receiving use. Any conclusion about comparison, substitution, reporting, or reuse is stated and supported separately.
5. Direction, time stance, and loss. Asymmetric relations show direction; any design-time, run-time, or other temporal difference that changes the comparison is explicit; every material limitation remains visible.
6. No automatic closure. Relations are not completed pairwise or transitively merely to fill a row.
7. No universal row type. A senseFamily label is not required and cannot substitute for an intensional account of what is being compared.
8. Parsimony. Keep only entries and columns that change the current answer.
9. Didactic bound. Split a row that a careful reader cannot understand in about thirty seconds.

#Micro-illustrations

The examples show table shapes. Every positive relation still requires its own evidence in an actual use.

#(a) Class-order comparison

#(b) Measurement comparison

#(c) Contrast: process

#Anti-patterns & remedies

#Worked examples

#Actor wording across BPMN and PROV

#Runtime occurrence comparison

Performed-Work attribution remains an A.15.1 and F.6 claim about actual Work and system-role assignment. The table supplies neither.

#Measured value and target

#Class inclusion and FCA order

A contrast row may show OWL class inclusion, FPF subtype, and FCA concept order together while stating that FCA order is not class inclusion. A positive relation between the first two is still a separate claim with its own semantics and evidence.

#Role trigger word

Show NIST RBAC role as a permission grouping and a local system-role-kind claim as a kind whose instances are Systems. Mark them distinct subjects. Use E.10.ROLE to recover other uses such as relation participation or signature position; do not assign them one senseFamily merely because the spelling matches.

#Safe reasoning moves

1. Name the comparison. What question or receiving use makes the row worth having?
2. Recover each entry. Cite its exact source, scheme, expression, and local claim.
3. List only obtaining relations. For each, state direction when relevant, the pattern that defines, constrains, or tests it, the supporting evidence, the loss, and any temporal difference that changes the comparison.
4. Judge the use separately. Explain what the named use may conclude and why.
5. Expose absence. When no relation is established, say so and use a contrast row.
6. Resist closure. Do not invent missing pairwise or transitive relations.
7. Extend cautiously. Add a source only when its claim or relation changes the answer; re-evaluate the use conclusion.
8. Keep evidence visible. A table cell never replaces the evidence-use or reliance relation.

#Relations

Builds on:

• Use F.1 for the exact source cut and receiving question, and use F.2 and F.3 for exact expressions and source-local claims.
• Use F.17 only when durable local-meaning addresses are needed.
• Use F.5 for selected designations without making them the values being named.
• Use F.9 to define and test a relation between exact local meanings and to state the separate bounded-use claim when that is the actual relation family. A table creates none of these facts.

Constrains:

• F.4 may cite a table for reader navigation, but the direct kind description and C.3 membership criterion remain the basis for a local system-role-kind claim.
• F.6 may reuse a designation from the table; the row supplies neither classification, assignment, Work, nor performed-work attribution.

Used by. Part C patterns may use the table as a didactic comparison surface. B.3 may rely only on exact evidence and obtaining relations, never on row position or a computed row score.

#Migration notes

1. Relation changes. Update the exact relation cell and re-evaluate only the receiving-use conclusions that depended on it.
2. New source. Do not auto-expand rows; add it only if it changes the stated comparison.
3. Local claim splits. Replace the old entry with the relevant child claim or split the comparison.
4. Use widens. Re-evaluate the new use directly; a former row label grants no promotion.
5. Designation changes. Update F.5 wording without changing source-local entries or relations.
6. Edition changes. Recover the successor claim and recheck affected relations; preserve the earlier source identity where historical claims remain relevant.

#Acceptance tests

#Static conformance

• SCR-F7-S01 (exact entries). Every local entry identifies an exact claim or F.17 cell and its source and edition.
• SCR-F7-S02 (no row-created fact). No relation or permission is inferred from co-placement, label similarity, or layout.
• SCR-F7-S03 (relation basis). Every positive relation cites the pattern that defines, constrains, or tests it, states direction where relevant, and cites its evidence.
• SCR-F7-S04 (receiving use). Every practical use conclusion is separate from the row and has its own basis.
• SCR-F7-S05 (loss disclosure). Material limitations and counterexamples remain visible.
• SCR-F7-S06 (parsimony). Every extra entry changes the current comparison or use.

#Regression

• RSCR-F7-E01 (relation drift). A changed relation triggers re-evaluation of dependent use conclusions, not a global row score.
• RSCR-F7-E02 (sense split). A split local claim leaves no ambiguous cell reference.
• RSCR-F7-E03 (use integrity). No consumer treats a row label as licence outside the stated conclusion.
• RSCR-F7-E04 (no stealth growth). New entries create no silent relation, closure, or widened use.

#Didactic distillation

“A Concept-Set table is a comparison surface. Put the exact source-local claims in it, then list only relations that have already been established, with direction and loss. State separately what one named comparison or use may conclude and why. A shared row, a shared label, or a minimum score proves nothing. If no relation is known, show a contrast. The table makes the reasoning easier to read; it never supplies the reasoning.”

#F.7:End

---

Last Updated: 2026-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)