G.6:4 - Solution — cite independently governed objects and relations
Create an EvidenceGraph only after the relied-on claim or bounded use and its supporting objects have been recovered. The graph is a declarative, addressable representation. Each node record cites one independently governed object; each asserted edge record cites one independently established direct relation. PathId, PathSliceId, and the provenance ledger add citation and refresh locality, not world-side facts.
G.6:4.1 - Subject-pattern map
| Represented claim or object | Subject pattern before G.6 represents it |
|---|---|
| Reusable method, generic participants, parameters, effects, and conditions | A.3.1 for the exact U.Method; A.3.2 for its U.MethodDescription |
| Independently admitted dated Work and its exact actual performer refs; optional obtaining F.6 relation and assignment occurrence refs when the path expressly consumes attribution; enactment, resources, and direct participation or binding facts | A.13 for each exact actual performer and A.15.1 for independent Work admission; F.6 and A.2.1 only when the path represents precise assignment-bound attribution; the exact direct participation or resource relation; and A.6.1 for operation-application bindings |
| Production or inception of an entity or episteme | one exact local A.15.PROD claim when its entry condition is met, or a direct subject predicate under its own pattern |
| Measurement result and its measurement-specific basis | C.16 |
| Acceptance-clause application or other runtime evaluation result | G.4 or the exact formal, conformance, diagnostic, causal, comparison, selection, gate, or decision governor |
| Work-resource aggregation result | B.1.6 |
| Durable episteme that states a local result | C.2.1; it remains distinct from the domain result |
| Outcome, later action, acceptance, gate passage, permission, or decision | its exact work and domain governor, including C.11 or A.21 when applicable |
| Source publication, carrier, copy, extraction, or publication occurrence | E.17 for a source-backed face and source return; E.24.PUB for an obtaining publication occurrence; the direct rule for each copy, extraction or source relation |
| Representation correspondence | C.29 |
| Bridge, congruence, loss, or cross-context transfer | F.9 |
| Transformation-flow structure distinct from performed work | E.18 and E.18.2 |
| First evidence/status use, provenance and bounded reliance, currentness, or assurance | A.2.4, A.10, G.11, or B.3 respectively |
G.6 does not substitute for any row. If the subject pattern or relation cannot be recovered, the path records an unresolved gap and cannot present that edge as obtaining.
Do not add a local U.EvidenceRole or turn proof, measurement, benchmark, source, or status labels into system-role kinds. For any claim that a producer, verifier, laboratory, issuer, or maintainer participates, recover the exact direct relation, the participants it declares, and the place each actual participant fills. Other nearby facts—for example, a local system-role kind, assignment, Work occurrence, responsibility, authority, or permission—are separate and may be cited only when they independently obtain; none establishes participation. Do not infer that a passive laboratory or produced entity performs Work merely because the path cites it.
Work recovery and compact citation. Before G.6 represents dated U.Work, its subject account must already recover each exact actual performer through A.13 and admit that Work independently under A.15.1. Include an assignment occurrence and obtaining F.6 relation only when the graph path or receiving use expressly consumes precise assignment-bound attribution; any present attribution must use the same obtaining A.13 assignment. If a required Work or performer ref is absent, record a Work gap. If an expressly consumed F.6 ref is absent or unresolved, retain the Work node and record an attribution gap rather than suppressing the Work. G.6 neither re-admits the Work nor retests assignment species, occurrence identity, holder, classification, predicate duration, or interval coverage. Merely listing an assignment beside Work establishes no relation between them.
G.6:4.2 - EvidenceGraph as a representation
An EvidenceGraph is a typed directed graph used for provenance citation and replay. It may project a dependency-closed slice of independently governed objects and relations. It is not a holarchy, work plan, method, transformation flow, result algebra, or proof that its contents obtain.
Minimal graph fields:
EvidenceGraph:
EvidenceGraphId
ReliedOnClaimOrBoundedUseRef
BoundedContext
ReferencePlane
RepresentedNodeRecords
RepresentedRelationEdgeRecords
TimeWindowOrPolicy
SourceCurrentnessRefs
BridgeOrLossRefs
EditionOrPolicyRefs
GraphPathAddressingRule
C29RepresentationRefs
A node record is a projection, not a new universal object kind:
RepresentedNodeRecord:
GraphNodeId
RepresentedObjectRef
ObjectKindAsGoverned
SubjectPatternLocator
ContextEditionOrTimeQualification?
RepresentationRef
The node set may cite exact Work occurrences and their A.13-qualified actual performer Systems. It may also cite local system-role kinds, assignment occurrences whose identities the path uses, obtaining F.6 relations when precise attribution is expressly consumed, direct participation and binding facts, produced entities, subject results, result epistemes, outcomes, sources, carriers, currentness results, reliance dispositions, and later Work. Every cited Work occurrence uses the independently established performer and A.15.1 Work refs described in §4.1; F.6 refs are optional and never discover the performer. Co-listing creates no relation among these objects.
An asserted edge is also a projection:
RepresentedRelationEdgeRecord:
GraphEdgeId
DirectRelationRef
DirectRelationKindRef
ActualParticipantRefs
SubjectPatternLocator
ObtainingClaimRef
ContextEditionOrTimeQualification?
RepresentationRef
Before the edge enters a relied-on path, the exact direct relation must already be established under its governor. The participant refs in the edge must match that relation; adjacency, direction, shared identifiers, timestamps, source order, or visual layout cannot supply them. RepresentationRef points outward to the applicable C.29 correspondence when that correspondence is current.
G.6 defines no fallback core edge vocabulary. Legacy or display labels such as verifiedBy, validatedBy, measuredBy, producedByWork, derivedFrom, usesMethodDescription, citesSource, or evidences are navigation prompts only. Replace each with the exact formal, measurement, work, production, publication, representation, provenance, temporal, status-use, premise, reference, argument, or other direct relation before asserting the edge as obtaining.
G.6:4.3 - PathId and PathSliceId
A PathId identifies one claim-local path inside an EvidenceGraph. A PathSliceId identifies the same path under a declared time window, reference plane, bounded context, edition, bridge, policy, or selected object/relation subset.
Use this compact record:
PathCitationRecord:
ReliedOnClaimOrBoundedUseRef
EvidenceGraphRef
PathId
PathSliceId
BoundedContext
ReferencePlane
RepresentedObjectRefs
RepresentedDirectRelationRefs
SubjectPatternLocators
SourcePublicationAndCarrierRefs
C29RepresentationRefs
TimeWindowOrFreshnessPolicy
SourceCurrentnessRefs
BridgeOrLossRefs
EditionOrPolicyRefs
DownstreamWorkRef?
ExactDownstreamUseRelationRef?
A10RelianceDispositionRef?
NotCarried
UnresolvedRelationGaps
ReopenTrigger
NotCarried names the stronger claim or use at issue that the path does not establish. Recover the exact premise, reference, operation-argument, decision-use, or other direct relation for actual downstream use. If the use asserts dated U.Work, cite its independently admitted A.15.1 Work ref and A.13-qualified performer refs. Add attribution refs only when the use expressly consumes precise assignment-bound attribution. Path availability or citation alone does not establish that use.
G.6:4.4 - Provenance ledger
A ProvenanceLedger is a citable replay index over PathCitationRecord entries. It is not a work-progress log, result registry, review-comment log, process-status log, or ontic source.
ProvenanceLedger:
LedgerId
EvidenceGraphRef
PathCitationRecords
RepresentedObjectIndex
RepresentedDirectRelationIndex
SourceOrderPolicy
CurrentnessPolicy
PrivacyOrDisclosureBoundary
RefreshScopeRule
The ledger may cite work, participants, produced entities, domain results, result epistemes, outcomes, sources, transformations, representation correspondences, provenance, and later uses. A row establishes none of them. Use a ledger when several downstream consumers need the same path family; do not create one merely because a local A.10 account is easy to write.
G.6:4.5 - Refresh and source return
Reopen the smallest affected PathId, PathSliceId, node projection, or relation-edge projection when any cited object, direct relation, governor, source, bridge, representation correspondence, edition, policy, time window, currentness result, or reliance boundary changes.
If the direct relation no longer obtains or its proof becomes unavailable, remove it from the relied-on path or mark the exact unresolved gap. Do not preserve the edge from graph history, infer a replacement relation, rerun unrelated paths, or certify a new downstream result through refresh alone.
G.6:4.6 - Declarative representation discipline
EvidenceGraph, PathId, PathSliceId, and ProvenanceLedger tell a reader which already governed account is being cited. They do not tell a worker what to do and they do not reconstruct missing world-side facts.
| Current phrase or artifact | Required recovery before G.6 representation |
|---|---|
| method, protocol, algorithm, clause, or policy | exact reusable declaration; when the path cites dated Work, recover it separately under §4.1; when it cites actual operation bindings, recover them under A.6.1 |
| work trace, run, test, audit, measurement, or evaluation | independently admitted dated Work ref and A.13-qualified actual performer refs under §4.1; enacted Method, resources, exact direct participation facts, and A.6.1 binding facts remain separate; expose an assignment occurrence and obtaining F.6 relation only when the path expressly consumes precise assignment-bound attribution |
| produced carrier, model, report, or episteme | exact produced entity and either its subject-specific direct production relation, when the subject pattern declares one, or the one local A.15.PROD production-work or inception claim that the current use needs |
| reading, score, verdict, estimate, aggregate, diagnosis, or outcome | exact domain result and direct governor; distinct C.2.1 episteme when durably stated |
| publication, view, export, or graph rendering | exact source relation, E.17 source-backed face, E.24.PUB publication occurrence, and C.29 representation correspondence when each is current |
| evidence, provenance, currentness, reliance, or assurance | A.2.4/A.10, G.11, and B.3 under their separate entry conditions |
| later acceptance, gate, release, or decision | its local result and exact later-use relation under their direct rules; dated Work admitted under §4.1 when that occurrence is asserted |
G.6:4.7 - Extension wiring without core drift
Selector, benchmark, assurance, refresh, or telemetry patterns may require additional pins in PathCitationRecord. They may cite PathId or PathSliceId, but they do not mint a universal edge, result, evidence, or criterion-participant relation. Any added graph record still names the exact represented object or direct relation and its governor.
G.5 may cite a path for selector explanation, G.9 for benchmark replication, G.11 for local refresh, and B.3 for an assurance input. Their selection, benchmark, currentness, and assurance results remain their own.