A.10:4.6b - Local evidence-use classifier and RelianceDisposition for source-bearing carrier or display reliance

A.10:4.6b - Local evidence-use classifier and `RelianceDisposition` for source-bearing carrier or display reliance

Use this subsection when a visible carrier, publication face, selected source U.Episteme ref, exact EpistemePublicationRelation occurrence ref when availability is material, source relation ref, or display is being relied on for a named claim or act. First recover the claim kind, the pattern or source rule that defines or tests the claim, the source/provenance path, and the bounded use. Broad words such as source, metric, confidence, conformant, safe, ready, certified, approval, or permission are recovery prompts, not relation names.

This is a local reliance-use classifier, not a Core evidence-kind ontology. Use only the row that decides the attempted use. The path represents exact direct relations and the RelianceDisposition records one bounded A.10 judgment; neither becomes a general evidence or authority relation. Affordability: ordinary orientation or source-finding can stop here; bounded reliance states one evidence use and the currentness window, unsupported-use boundary, and stop or reopen condition that apply to it. If a direct domain rule requires assurance, state the exact assurance claim and then use B.3. Plain wording remains ordinary unless it changes one of the named source, evidence, gate, assurance, Work, decision, or control claims.

Cheap stop: if the bounded claim, carrier, evidence-provenance path, and bounded evidence use are recoverable, with the currentness, unsupported-use boundary, and stop or reopen condition applicable to that use, and there is no actual assurance claim, gate relation, Work relation, control-bearing relation, or release relation, stay in A.10. Do not open B.3, A.21, B.2.5, or a broad evidence pack merely because the carrier or display looks official, quantitative, generated, credentialed, or safety-related.

Common wrong first classification: a visible carrier, selected source U.Episteme ref, publication-form or carrier ref, exact EpistemePublicationRelation occurrence ref, source relation ref, or display is approval, permission, safety, or readiness. First honest entry: recover the A.10 evidence-provenance path for one bounded claim or use; approval, permission, safety, readiness, gate passage, and work authority must be established separately under the pattern that defines or tests each claim.

Plain disposition palette: RelianceDisposition=pass means proceed only inside the bounded evidence use; degrade means use only a narrower or reversible version; abstain means do not decide yet; reopen means a changed or contested evidence relation defeated the previous classification; evidence-needed names missing evidence at the decision point; assurance-needed says a separately stated assurance claim is required before this attempted use can proceed; blocked-current-use blocks the attempt until its evidence-provenance path or source relation changes.

Source-looking evidence use or attempted use	First A.10 action	Escalation trigger	Forbidden overread
Ordinary source-backed report, record, citation, observation, model card, datasheet, data card, or publication excerpt	Name the claim, carrier, producer or Method trace when relied on, evidence-provenance path, and bounded evidence use. Add currentness, a locally plausible unsupported use, and a stop or reopen condition when they change reliance.	Open B.3 only when an actual named assurance claim is current; open A.21 for a relied-on gate decision, A.15 or A.15.1 for Work, or another pattern only when that relation is actually claimed.	Evidence presence as approval, gate passage, assurance, release permission, Work authority, control authority, or safety acceptance.
Confidence, calibration, prediction interval, abstention reason, or selective-action cue	Name the act and the assumptions of the selected inference or calibration method. Retain its calibration population and exchangeability when that method requires them, and the window, shift, applicability, and stop condition that bound this evidence use. Use `pass` or `degrade` only for that use; exclude a locally plausible unsupported wider use when the distinction matters.	Open C.27 or G.11 when timing, expiry, refresh, distribution shift, monitoring, or applicability changes the act; open B.3 only for an actual named assurance claim.	Confidence as global permission, trust, readiness, safety, release reliance, or engineering justification.
Generated explanation, generated summary, or didactic reconstruction	Keep the rendering in `E.17.EFP` as explanation or source-finding unless each relied-on operative claim has an `A.10` evidence-provenance path or another source relation that carries or exposes the source basis for the operative claim.	Apply `A.10`, `B.3`, `A.21`, `A.15`, or the pattern that defines or tests the operative claim being relied on.	Explanation wording as evidence, assurance, approval, gate passage, work occurrence, or permission.
Conformance label, `CV.Status`, benchmark result, score, semantic-fidelity marker, or CV-looking publication near release	Recover the declared relation: measurement or marker relation, `A.20` step-local CV status, `A.21` gate check, `E.19` admission/refresh review result, `E.21` pattern-quality evaluation result, `C.16` characterization, or external-rule source named by value. A score label alone selects neither E.19 nor E.21.	Open `A.21` only when a named gate applies its profile rule to the effective check-application results and returns a `GateDecisionResult`; open `B.3` only when an assurance claim is being made.	Conformance or score as value, adequacy, release confidence, work occurrence, safety, trust, or gate passage outside the declared relation.
Provenance, authenticity, C2PA-like credential, SLSA-like attestation, build record, or status-register display	State the bounded origin, history, build, or currentness claim being evidenced and the source relation carrying it. Retain the method/production trace, holder, status, verifier rule, and relying-context facts required by that claim or verification regime.	Open the record or relation that carries truth, permission, safety, release, gate passage, work occurrence, or assurance only when that relation is being claimed by value.	Provenance, authenticity, or status-currentness as truth, safety, approval, permission, release, gate passage, or assurance.
Contest, redress request, challenge, appeal, or conflicting source relation	Name the contested claim, evidence carrier, source-order or currentness issue, affected use or harm, available challenge or redress relation, allowed evidence, possible disposition change, outcome route, and reopen trigger. Add a review-responsibility relation or missing governor only when the claim assigns future review Work.	Open neighboring system-role, assignment-state, commitment, gate, control, assurance, Work, or representation patterns only when those effects are claimed by value.	Appeal-channel presence, challenge form, or redress workflow presence as truth, compliance proof, social-effect acceptance, completed redress, gate passage, or work authorization.

For A.10 use, RelianceDisposition is a local disposition over the evidence-provenance path and the bounded reliance use. Outside a table column already headed RelianceDisposition, write the qualified form RelianceDisposition=... and bind it to the named bounded evidence use, with currentness and window, an unsupported-use boundary, and a reopen or stop condition when applicable; it is not CV.Status, GateDecisionResult, selector result, or ProblemCard@Context state.

Observed-effect or consequence evidence supports what happened or is credibly recorded. If the claim says that the source caused, prevented, would have changed, or causally contributed to the effect, use C.28 for that causal question while retaining its A.10 evidence path and any separately required Work or assurance relation. A normative responsibility or allocation claim uses its own direct rule; the phrase ‘responsible for’ must be resolved from the source claim before selecting either branch.

If a proxy marker, benchmark, confidence value, dashboard metric, or score becomes the primary driver for action, release, resource allocation, people status, team status, or P2W priority, check whether the claim being made also raises an E.13 proxy-to-objective question. Do not open E.13 for every metric; open it only when the proxy is being used as the target or decision driver.

Use C.26.1 when publication, observation, or another interaction changes the represented state while its output is being used as if it were a passive read, export, comparison, or decision input. First identify what the interaction changed and which use of the output must change. This is the probe-coupled question for a dashboard, warning, label, or public status display; ordinary influence without the false passive-read use does not activate it.

`RelianceDisposition`	A.10 classification	Minimum A.10 statement
`RelianceDisposition=pass`	The evidence relation named by value is present and current for the named use, evidence of the required kind is present, the source relation is current enough for that use, and the evidenced use is bounded.	State the evidenced claim, act, work occurrence, review claim, or P2W carry-through use and its evidence-provenance path. Add the applicable window and any locally plausible unsupported use that must be excluded.
`RelianceDisposition=degrade`	The source relation carries only a narrower claim, smaller audience, reversible local act, lower assurance input, or shorter window.	State the narrowed bounded evidence use, the proposed or locally plausible wider use it excludes, and the applicable stop condition.
`RelianceDisposition=abstain`	Evidence is insufficient, stale, out-of-context, uncalibrated, conflicted, or not tied to the claimed relation, while immediate rejection is not justified.	State the claim not decided and the missing evidence or relation needed before use.
`RelianceDisposition=reopen`	A contest, changed representation, changed selected entity, stale source, expired window, changed profile, conflicting source, retargeting, or new evidence defeats the previous evidence-provenance path.	State the source or relation to reopen and the previous use that is no longer evidenced.
`RelianceDisposition=evidence-needed`	The visible carrier, selected source `U.Episteme` ref, exact publication-occurrence ref when availability is material, source relation ref, or display may matter, but evidence of the required kind or the source-currentness relation is absent.	State the missing evidence kind, the pattern or source rule that defines or tests it, and the decision point so delay does not become indefinite.
`RelianceDisposition=assurance-needed`	A direct domain rule or receiving decision requires a separately stated assurance claim before the attempted use may proceed, and the current A.10 basis alone cannot supply it.	State the required assurance claim and its direct domain basis. Apply B.3 only after that claim is current; until then block or narrow the attempted use.
`RelianceDisposition=blocked-current-use`	No current evidence-provenance path carries the evidence relation needed for the attempted act, work, claim, gate, release, assurance, review, control-bearing feedback, or P2W use.	State the blocked use and the neighboring pattern or project record required before a new attempt.

Minimum contest relation with possible redress: a contest relation exists when the affected party can identify the disputed claim or source, affected use or harm, an available challenge, review, redress, communication, source, publication, register, access, or contact relation, evidence or argument allowed in challenge, possible disposition change, outcome route, and reopen trigger. A system-role label, assignment, feedback channel, complaint form, or appeal label without those recoverable values is not enough to change the disposition. Responsibility for future review Work is a separate claim.

Affected-party contestable minimum: even when raw evidence stays restricted, the contesting party must be able to see enough of the claim, source class, disposition, affected use, available challenge or contact route, and allowed challenge evidence to challenge the result. Privacy, security, or privilege can narrow disclosure; they cannot erase the challengeable minimum while still claiming contest or redress.

False-negative reliance guard: a blocked, abstained, or evidence-needed use is not final if challenge evidence, missing affected-party evidence, changed source relation, changed selected source U.Episteme edition, changed EpistemePublicationRelation occurrence when availability is material, changed publication form, changed evidence carrier, changed representation, or redress can materially change the disposition. If refusal is based on missing evidence, name the missing evidence kind and decision point rather than closing the dispute by vagueness.

Sensitive evidence boundary: use scoped, hashed, redacted, or access-controlled evidence refs when raw carriers would expose personal data, secrets, tokens, privileged logs, tenant identifiers, incident details, security-sensitive traces, or unnecessary identities. A redacted path must still preserve enough recoverability for the relied-on claim, disposition, and contest relation.

Worked source-overread slices:

Slice	A.10 usable classification	Unsupported lift
Software supply-chain attestation is cited near a release conversation.	The attestation may evidence its named bounded origin, build-method, or production-trace claim. Recover the verifier-rule, holder, and currentness facts that this claim or its verification/use regime requires.	Runtime safety, release approval, gate passage, or assurance unless `B.3`, `A.21`, or another relation that carries the asserted use is established for that use.
A verified provenance credential, watermark, or authenticity mark appears on a publication face.	The mark may evidence where the carrier, signature, assertion, or manifest came from under the verifier regime.	Truth of the represented world-state, safety, permission, or adequacy by provenance alone.
A confidence interval or calibration result is used for one reversible act.	State the act, context, calibration condition, and bounded evidence use, with the applicable window, unsupported-use boundary, and stop condition.	Global readiness, trust, safety, release reliance, or engineering justification.
A generated explanation or summary says a result is reliable.	Treat the rendering as source-finding or explanation until the operative claim has an `A.10` evidence-provenance path or another source relation that carries or exposes the source basis for the operative claim.	Evidence, approval, gate passage, work occurrence, or assurance by fluent wording.
Contest or redress is claimed after a source relation, selected source `U.Episteme`, exact publication occurrence, publication form, or evidence carrier is challenged.	State the disputed claim, affected use or harm, available challenge or redress relation, allowed challenge evidence, possible disposition change, outcome route, and reopen trigger. Add future-review responsibility only when that stronger claim is current.	Claim truth, compliance proof, completed redress, or social-effect acceptance by appeal-channel presence.
A harmed party gives challenge evidence that could change the disposition, but the receiving System answers “evidence insufficient” without naming the missing evidence kind or decision point.	Treat the refusal as `RelianceDisposition=reopen` or invalid `RelianceDisposition=evidence-needed`; name the missing evidence kind, decision point, available challenge route, and possible disposition change.	Closed refusal, completed redress, or `RelianceDisposition=blocked-current-use` by vague insufficiency.