A.2.4 - Episteme Evidence-Use and Status-Use Relations
A.2.4 - Episteme Evidence-Use and Status-Use Relations Type: Boundary and relation-use pattern Status: Stable Normativity: Normative…
Search words, quoted phrases, and exact IDs across the current corpus.
By default, all meaningful words must match the same source passage, in its text or titles. Matching ignores letter case. Ordinary word queries skip common English function words such as the, and and or; quotes keep a phrase, and uppercase operators control matching.
| Example | What it does |
|---|---|
controlled variation | Requires both meaningful words; their order may differ. |
"controlled variation" | Requires adjacent words in that order. |
SYSE.24:4 | Prioritizes the exact named section. Pattern IDs also work. |
engineering OR management | Matches either alternative. Write OR and AND in uppercase. |
engineering AND (research OR management) | Requires engineering together with either grouped alternative. |
engineering -management | Excludes passages that match management. |
title:"controlled variation"body:"controlled variation" | Restricts the phrase to section/publication titles, or to source text. A field prefix applies to the following term or phrase. |
"controlled variation"~1 | Allows one intervening word in the phrase. |
"controlled vari"* | Requires adjacent words, with the last word as a prefix. |
engineering^2 OR management | Gives engineering matches more ranking weight. |
The Publication, Suite and Type filters narrow the same query. Results are source passages, not generated answers. Search does not translate, expand synonyms or automatically correct spelling. For a task expressed in another language, try English terms and read the context. Press / to focus the search field.
A.2.4 - Episteme Evidence-Use and Status-Use Relations Type: Boundary and relation-use pattern Status: Stable Normativity: Normative…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
Do not create or use source spelling U.EvidenceRole as a durable FPF kind. Do not place an episteme in U.SystemRoleAssignment merely because it is used as evidence, source, standard, requirement, definition, explanation, publication, status bearer, or…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
ProofResult-12 is a C.2.1 episteme stating an entailment under GraphTheory_v3.1. Dated checker work, its method, theory and proof bindings, and the formal entailment result are recovered under their subject patterns. A.2.4 classifies the episteme as…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
A.2.4:3 - Forces Force Tension this pattern resolves Episteme identity versus episteme use The same episteme can be used for several claims while retaining its identity. Compact evidence statement versus full evidence graph Users need a small evidence-use…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
An episteme may be used for several claims or governed statuses. State each evidence-use or status-use relation separately. The classification points outward to, and never replaces, performed Work, the domain-local result, the C.2.1 result episteme,…
In A.2 - System-Role Kinds and Assignments
Use a local U.Kind when U.System candidates need one stable, assignable, work-facing membership distinction. Recover the kind through the candidate domain, operative condition, useful member/non-member boundary, and continuity rule. Keep practice or source…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
A simulation-output episteme is classified for one bounded C.28 claim. C.28 retains simulationResultRef, model assumptions, validation, the causal-use support result, supported use, and unsupported use. A.2.4 cannot relabel the episteme as…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
A.2.4:6 - Bias-Annotation An evidence or status label can prompt readers to assume that the needed relation already obtains. Recover the episteme and its evidence-use or status-use relation before relying on that label. Apply the direct source, causal, or…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
An A.2.4 assertion answers only: which episteme is classified for which evidence-use or status-use, under which effective source scheme when interpretation matters, with which ClaimScope, polarity or status value, and window. When source production,…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
… or causal-use relations. The cost is explicit relation recovery. A phrase such as "evidence role", "status role", "standard role", "proof role", or "benchmark role" no longer closes the claim. The user needs to recover which episteme, claim, scope, status,…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
A.2.4 does not fill a missing direct governor with a generic status, evidence, work-result, or evaluation-result relation…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
Lower an attempted A.2.4 use when the episteme is known but the target claim, scope, polarity, status value, time window, or provenance constraints are not recoverable. The lowered result may be source-finding, orientation, an evidence-needed note, a…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
A.2.4:11 - Relations Builds on: A.2 for exact local system-role kinds, A.2.1 for U.SystemRoleAssignment, A.6.5 for SlotSpec discipline, and C.2.1 for episteme identity and its distinct constitution, empirical-grounding, and edition relations. Coordinates…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
ProofResult-12 is a C.2.1 episteme stating an entailment under GraphTheory_v3.1. Dated checker work, its method, theory and proof bindings, and the formal entailment result are recovered under their subject patterns. A.2.4 classifies the episteme as…
In A.2.4 - Episteme Evidence-Use and Status-Use Relations
… claim. In separate evaluation work, an evaluator applies the G.4 clause through A.6.1 bindings and obtains unknown; a different C.2.1 episteme states that verdict. A.10/G.6 preserve provenance, G.11 currentness, and in later C.11 decision work, a…