# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-09T20:36:09Z", "synthesisSha256": "5c5bac1bfd9549d932182afad4c9810489bb4489e8aa96aba4cbd4d5814921f8", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ORG-012", "registryId": "vr.wm-org-012", "name": "Inter-organizational Relationship", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "relationship", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ORG.REL" ], "tags": [ "inter", "organizational", "relationship", "soc.org.rel" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-org-012-inter-organizational-relationship/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-org-012", "model": { "registry_id": "vr.wm-org-012", "model_id": "WM-ORG-012", "name": "Inter-organizational Relationship", "entry_kind": "relationship", "purpose": "Describe attributed, time-qualified organizational relationships without confusing affiliation, supply, consolidation and ownership.", "scope_statement": "A source-qualified relationship aggregate with explicit participants, kind, direction, scope and evidence. Real-world relation state, publisher record state and observer claims remain separate. Multi-party arrangements require retained membership context.", "in_scope": [ "Relationship identity, endpoint roles and qualified kind", "Control-basis references, collaboration and exchange scope", "Temporal assertions, graph constraints, disputes and permitted mappings" ], "out_of_scope": [ "Organization identity, contract execution and ownership-register mastership", "Customer/account and supplier-qualification lifecycles", "Inferring legal authority, beneficial ownership or universal transitivity from a generic link" ], "boundary_notes": [ { "neighbor": "WM-ORG-001 Organization", "distinction": "Reference organization identities; a relationship is not either organization.", "source_refs": [ "SRC-001", "SRC-005" ] }, { "neighbor": "WM-ORG-014 and WM-ORG-015", "distinction": "Customer/account and supplier/partner qualification remain separate lifecycle masters; relationships provide scoped links.", "source_refs": [ "SRC-005" ] }, { "neighbor": "Ownership and accounting consolidation", "distinction": "Qualified relation kinds are not universally equivalent; person beneficial owners are out of endpoint scope.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "neighbor": "Activity and contract", "distinction": "PROV Association qualifies activity-agent provenance, not inter-organizational partnership; contract execution stays delegated.", "source_refs": [ "SRC-005", "SRC-006" ] } ] }, "sources": [ { "id": "SRC-001", "title": "The Organization Ontology", "organization": "W3C", "url": "https://www.w3.org/TR/vocab-org/", "version_or_date": "Recommendation; dated URI pin pending", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-09T20:26:00Z", "relevance": "Selected organizational links and hierarchy clauses; linkedTo does not imply transitivity or legal control." }, { "id": "SRC-002", "title": "Relationship Record CDF documentation", "organization": "GLEIF", "url": "https://www.gleif.org/content/4_lei-data/1_access-and-use-lei-data/4_level-2-data-relationship-record-rr-cdf-2-1-format/rr-cdf_version_2.1-documentation.html", "version_or_date": "RR-CDF 2.1", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-09T20:26:00Z", "relevance": "Introduction, release notes and abstract record content; full XSD constraints not verified." }, { "id": "SRC-003", "title": "Level 2 Data: Who Owns Whom", "organization": "GLEIF", "url": "https://www.gleif.org/en/lei-data/access-and-use-lei-data/level-2-data-who-owns-whom", "version_or_date": "Public explanation inspected 2026-09-09; release date unspecified", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-09T20:26:00Z", "relevance": "Direct and ultimate accounting-consolidating parents; not universal beneficial ownership." }, { "id": "SRC-004", "title": "Beneficial Ownership Data Standard schema reference", "organization": "Open Ownership", "url": "https://standard.openownership.org/en/latest/standard/reference.html", "version_or_date": "BODS 0.4; mutable latest alias requires pinning", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-09T20:26:00Z", "relevance": "Selected relationship components, source and record lifecycle clauses. Persons are outside this organization-endpoint model." }, { "id": "SRC-005", "title": "Open Contracting Data Standard release reference", "organization": "Open Contracting Partnership", "url": "https://standard.open-contracting.org/latest/en/schema/reference/", "version_or_date": "OCDS 1.1.5", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-09T20:26:00Z", "relevance": "Selected parties, organization references and process-qualified roles; not an entire supplier lifecycle." }, { "id": "SRC-006", "title": "PROV-O: The PROV Ontology", "organization": "W3C", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation; dated URI pin pending", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-09T20:26:00Z", "relevance": "Qualified Association describes activity-agent responsibility, not a general partnership predicate." }, { "id": "SRC-007", "title": "Date and Time on the Internet: Timestamps", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339 July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-09T20:26:00Z", "relevance": "Selected sections 5.6-5.8: precise instants with seconds and offset; preserve date-only legal effect separately." } ], "structure": { "bundles": [ { "id": "relation-relationship-identity-and-endpoint-semantics", "name": "Relationship identity and endpoint semantics", "description": "Inter-organizational relationship identity and endpoint semantics.", "rationale": "Keeps relationship-owned assertions separate from endpoint identities and operational masters; a proposed Vercy grouping, not a normative source hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005" ], "layers": [ { "id": "relation-identity", "name": "Source-qualified relationship identity", "description": "Qualified relationship assertion for source-qualified relationship identity. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "relation-identity-record", "name": "Source-qualified relationship identity record", "description": "Qualified relationship assertion for source-qualified relationship identity. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "relation-identity-q01", "text": "Which master namespace and identifier distinguish this relationship from another relationship between the same organizations?", "kind": "identity", "answer_data": [ "relation-identity-identity" ] }, { "id": "relation-identity-q02", "text": "Which versioned kind definition makes it partnership, affiliation, supply, control or another relation, and which near-neighbour kinds are excluded?", "kind": "classification", "answer_data": [ "relation-identity-kind" ] }, { "id": "relation-identity-q03", "text": "Which scope qualifier distinguishes parallel relationships by service, geography, business unit or agreement without overwriting one another?", "kind": "constraint", "answer_data": [ "relation-identity-scope" ] } ], "data_elements": [ { "id": "relation-identity-identity", "name": "identity", "description": "Proposed structured answer group: namespace,id,master. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "relation-identity-kind", "name": "kind", "description": "Proposed structured answer group: scheme,version,code,exclusions. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "relation-identity-scope", "name": "scope", "description": "Proposed structured answer group: dimensions,values,parallelRelationshipRefs. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "relation-identity-artifact", "name": "Source-qualified relationship identity assertion artifact", "description": "Versioned source-qualified relationship identity assertion and authorized evidence references; referenced contracts and organization records retain their masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Issuer-qualified master ID, else Dimension UUID; immutable revision and exact digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "participant-roles", "name": "Participants, direction and multiplicity", "description": "Qualified relationship assertion for participants, direction and multiplicity. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "findings": [ { "id": "participant-roles-record", "name": "Participants, direction and multiplicity record", "description": "Qualified relationship assertion for participants, direction and multiplicity. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "questions": [ { "id": "participant-roles-q01", "text": "Which organization references occupy each endpoint role and which identity resolution remains unknown or disputed?", "kind": "relationship", "answer_data": [ "participant-roles-participants" ] }, { "id": "participant-roles-q02", "text": "Is the relation directional, reciprocal or symmetric under its kind, and what inverse label preserves rather than changes its meaning?", "kind": "relationship", "answer_data": [ "participant-roles-direction" ] }, { "id": "participant-roles-q03", "text": "Is this a bilateral relation or a multi-party arrangement, and what is lost if its membership is exported as pairwise edges?", "kind": "composition", "answer_data": [ "participant-roles-arity" ] } ], "data_elements": [ { "id": "participant-roles-participants", "name": "participants", "description": "Proposed structured answer group: orgRefs,roles,resolution. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "participant-roles-direction", "name": "direction", "description": "Proposed structured answer group: kind,inverse. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "participant-roles-arity", "name": "arity", "description": "Proposed structured answer group: arrangementRef,participantSet,pairwiseLoss. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "participant-roles-artifact", "name": "Participants, direction and multiplicity assertion artifact", "description": "Versioned participants, direction and multiplicity assertion and authorized evidence references; referenced contracts and organization records retain their masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Issuer-qualified master ID, else Dimension UUID; immutable revision and exact digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "relation-relationship-basis-and-domain-extent", "name": "Relationship basis and domain extent", "description": "Inter-organizational relationship basis and domain extent.", "rationale": "Keeps relationship-owned assertions separate from endpoint identities and operational masters; a proposed Vercy grouping, not a normative source hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006" ], "layers": [ { "id": "recognition-basis", "name": "Basis, recognition and authority", "description": "Qualified relationship assertion for basis, recognition and authority. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "findings": [ { "id": "recognition-basis-record", "name": "Basis, recognition and authority record", "description": "Qualified relationship assertion for basis, recognition and authority. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "questions": [ { "id": "recognition-basis-q01", "text": "What evidence establishes the claimed relation rather than merely common branding, a shared address or an unverified marketing statement?", "kind": "evidence", "answer_data": [ "recognition-basis-recognition" ] }, { "id": "recognition-basis-q02", "text": "Who asserts or recognizes it, in which capacity, and does the other party confirm, contest or have no recorded position?", "kind": "authority", "answer_data": [ "recognition-basis-positions" ] }, { "id": "recognition-basis-q03", "text": "Which governing instrument and jurisdiction qualify the assertion without transferring contract ownership or legal adjudication to this record?", "kind": "requirement", "answer_data": [ "recognition-basis-basis" ] } ], "data_elements": [ { "id": "recognition-basis-recognition", "name": "recognition", "description": "Proposed structured answer group: signals,counterexamples,evidenceRefs. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "recognition-basis-positions", "name": "positions", "description": "Proposed structured answer group: claimant,capacity,counterpartyPosition. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "recognition-basis-basis", "name": "basis", "description": "Proposed structured answer group: instrumentRefs,jurisdiction. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "recognition-basis-artifact", "name": "Basis, recognition and authority assertion artifact", "description": "Versioned basis, recognition and authority assertion and authorized evidence references; referenced contracts and organization records retain their masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Issuer-qualified master ID, else Dimension UUID; immutable revision and exact digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "control-interest", "name": "Control and ownership interpretation", "description": "Qualified relationship assertion for control and ownership interpretation. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ], "findings": [ { "id": "control-interest-record", "name": "Control and ownership interpretation record", "description": "Qualified relationship assertion for control and ownership interpretation. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ], "questions": [ { "id": "control-interest-q01", "text": "Does the relation concern accounting consolidation, equity, votes, other control or beneficial interest, and which definition applies?", "kind": "classification", "answer_data": [ "control-interest-controlbasis" ] }, { "id": "control-interest-q02", "text": "What share, range, denominator, class, date and uncertainty qualify a quantitative interest instead of an unqualified percentage?", "kind": "measurement", "answer_data": [ "control-interest-interest" ] }, { "id": "control-interest-q03", "text": "Is direct or indirect control explicitly evidenced, which intermediate records support it, and which inference rules are prohibited?", "kind": "relationship", "answer_data": [ "control-interest-chain" ] } ], "data_elements": [ { "id": "control-interest-controlbasis", "name": "controlBasis", "description": "Proposed structured answer group: type,definition,accountingStandard. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "control-interest-interest", "name": "interest", "description": "Proposed structured answer group: value,min,max,denominator,class,asOf,uncertainty. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "control-interest-chain", "name": "chain", "description": "Proposed structured answer group: directness,components, derivationRule,prohibitedInferences. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "control-interest-artifact", "name": "Control and ownership interpretation assertion artifact", "description": "Versioned control and ownership interpretation assertion and authorized evidence references; referenced contracts and organization records retain their masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Issuer-qualified master ID, else Dimension UUID; immutable revision and exact digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "relation-collaboration-and-exchange-boundaries", "name": "Collaboration and exchange boundaries", "description": "Inter-organizational collaboration and exchange boundaries.", "rationale": "Keeps relationship-owned assertions separate from endpoint identities and operational masters; a proposed Vercy grouping, not a normative source hierarchy.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "layers": [ { "id": "collaboration-scope", "name": "Partnership purpose and responsibilities", "description": "Qualified relationship assertion for partnership purpose and responsibilities. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-006" ], "findings": [ { "id": "collaboration-scope-record", "name": "Partnership purpose and responsibilities record", "description": "Qualified relationship assertion for partnership purpose and responsibilities. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-006" ], "questions": [ { "id": "collaboration-scope-q01", "text": "What jointly stated purpose and activity scope belong to this collaboration?", "kind": "definition", "answer_data": [ "collaboration-scope-purpose" ] }, { "id": "collaboration-scope-q02", "text": "Which responsibilities are attributed to each party and where are their governing mandates mastered?", "kind": "authority", "answer_data": [ "collaboration-scope-responsibilities" ] }, { "id": "collaboration-scope-q03", "text": "What limits distinguish the collaboration from a newly formed legal entity or permission for an agent to bind either party?", "kind": "constraint", "answer_data": [ "collaboration-scope-boundary" ] } ], "data_elements": [ { "id": "collaboration-scope-purpose", "name": "purpose", "description": "Proposed structured answer group: statement,scope,evidence. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "collaboration-scope-responsibilities", "name": "responsibilities", "description": "Proposed structured answer group: party,role, mandateRef. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "collaboration-scope-boundary", "name": "boundary", "description": "Proposed structured answer group: entityFormationRef,excludedAuthorities. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] } ], "artifacts": [ { "id": "collaboration-scope-artifact", "name": "Partnership purpose and responsibilities assertion artifact", "description": "Versioned partnership purpose and responsibilities assertion and authorized evidence references; referenced contracts and organization records retain their masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Issuer-qualified master ID, else Dimension UUID; immutable revision and exact digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "exchange-link", "name": "Supply and service linkage", "description": "Qualified relationship assertion for supply and service linkage. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-005" ], "findings": [ { "id": "exchange-link-record", "name": "Supply and service linkage record", "description": "Qualified relationship assertion for supply and service linkage. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "exchange-link-q01", "text": "Which party supplies and which receives what defined service or product scope, without importing orders, delivery events or payments here?", "kind": "relationship", "answer_data": [ "exchange-link-exchange" ] }, { "id": "exchange-link-q02", "text": "Is the linkage prospective, awarded, observed or terminated, and what process-qualified evidence establishes that state?", "kind": "state", "answer_data": [ "exchange-link-commercialassertion" ] }, { "id": "exchange-link-q03", "text": "Which customer/account or supplier-qualification models master the detailed commercial lifecycle and which fields must not be duplicated here?", "kind": "ownership", "answer_data": [ "exchange-link-delegation" ] } ], "data_elements": [ { "id": "exchange-link-exchange", "name": "exchange", "description": "Proposed structured answer group: provider,recipient,scopeRefs. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "exchange-link-commercialassertion", "name": "commercialAssertion", "description": "Proposed structured answer group: stage,evidenceRef,processRef. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "exchange-link-delegation", "name": "delegation", "description": "Proposed structured answer group: modelRefs,masterFields,excludedFields. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "exchange-link-artifact", "name": "Supply and service linkage assertion artifact", "description": "Versioned supply and service linkage assertion and authorized evidence references; referenced contracts and organization records retain their masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Issuer-qualified master ID, else Dimension UUID; immutable revision and exact digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "relation-time-lifecycle-and-graph-interpretation", "name": "Time, lifecycle and graph interpretation", "description": "Inter-organizational time, lifecycle and graph interpretation.", "rationale": "Keeps relationship-owned assertions separate from endpoint identities and operational masters; a proposed Vercy grouping, not a normative source hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007" ], "layers": [ { "id": "relationship-time", "name": "Effective interval and record history", "description": "Qualified relationship assertion for effective interval and record history. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "findings": [ { "id": "relationship-time-record", "name": "Effective interval and record history record", "description": "Qualified relationship assertion for effective interval and record history. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "questions": [ { "id": "relationship-time-q01", "text": "When did the relationship take effect and cease, at what precision, and are interval endpoints known, estimated or open?", "kind": "temporal", "answer_data": [ "relationship-time-validtime" ] }, { "id": "relationship-time-q02", "text": "When was the assertion observed, recorded and published, distinct from its effective interval, and which revision supersedes it?", "kind": "provenance", "answer_data": [ "relationship-time-knowledgetime" ] }, { "id": "relationship-time-q03", "text": "Does closure mean real-world termination, publisher record retirement or correction of erroneous data, and how is that distinction retained?", "kind": "lifecycle", "answer_data": [ "relationship-time-closure" ] } ], "data_elements": [ { "id": "relationship-time-validtime", "name": "validTime", "description": "Proposed structured answer group: start,end,precision,uncertainty. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "relationship-time-knowledgetime", "name": "knowledgeTime", "description": "Proposed structured answer group: observedAt,recordedAt,publishedAt,supersedes. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "relationship-time-closure", "name": "closure", "description": "Proposed structured answer group: meaning,reason,evidence. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "relationship-time-artifact", "name": "Effective interval and record history assertion artifact", "description": "Versioned effective interval and record history assertion and authorized evidence references; referenced contracts and organization records retain their masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Issuer-qualified master ID, else Dimension UUID; immutable revision and exact digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "graph-interpretation", "name": "Graph derivation and structural constraints", "description": "Qualified relationship assertion for graph derivation and structural constraints. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "findings": [ { "id": "graph-interpretation-record", "name": "Graph derivation and structural constraints record", "description": "Qualified relationship assertion for graph derivation and structural constraints. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "questions": [ { "id": "graph-interpretation-q01", "text": "Which kind-specific constraints permit or forbid self-links, cycles and multiple parents without imposing one universal organization tree?", "kind": "constraint", "answer_data": [ "graph-interpretation-graphrules" ] }, { "id": "graph-interpretation-q02", "text": "Which direct records, time slice and rule generated an indirect relation, and can the derived edge be reproduced separately from asserted data?", "kind": "provenance", "answer_data": [ "graph-interpretation-derivation" ] }, { "id": "graph-interpretation-q03", "text": "What ambiguity or information loss arises from merging conflicting, incomplete or differently scoped relationship graphs?", "kind": "quality", "answer_data": [ "graph-interpretation-graphloss" ] } ], "data_elements": [ { "id": "graph-interpretation-graphrules", "name": "graphRules", "description": "Proposed structured answer group: profile,cardinality,cyclePolicy,selfLinkPolicy. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "graph-interpretation-derivation", "name": "derivation", "description": "Proposed structured answer group: inputRefs,asOf,ruleVersion,outputKind. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "graph-interpretation-graphloss", "name": "graphLoss", "description": "Proposed structured answer group: gaps,conflicts,scope. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "graph-interpretation-artifact", "name": "Graph derivation and structural constraints assertion artifact", "description": "Versioned graph derivation and structural constraints assertion and authorized evidence references; referenced contracts and organization records retain their masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Issuer-qualified master ID, else Dimension UUID; immutable revision and exact digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "relation-evidence-dispute-and-stewardship", "name": "Evidence, dispute and stewardship", "description": "Inter-organizational evidence, dispute and stewardship.", "rationale": "Keeps relationship-owned assertions separate from endpoint identities and operational masters; a proposed Vercy grouping, not a normative source hierarchy.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "assertion-evidence", "name": "Evidence quality and counterclaims", "description": "Qualified relationship assertion for evidence quality and counterclaims. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-004", "SRC-006" ], "findings": [ { "id": "assertion-evidence-record", "name": "Evidence quality and counterclaims record", "description": "Qualified relationship assertion for evidence quality and counterclaims. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "assertion-evidence-q01", "text": "Which attributable source, exact record and retrieval context support each relationship assertion, and what validation has actually occurred?", "kind": "evidence", "answer_data": [ "assertion-evidence-evidence" ] }, { "id": "assertion-evidence-q02", "text": "Which contradictory assertions coexist and who may resolve their conflict under the Dimension policy rather than overwrite inconvenient evidence?", "kind": "decision", "answer_data": [ "assertion-evidence-dispute" ] }, { "id": "assertion-evidence-q03", "text": "Does missing data mean unknown, withheld, not reported, expired or explicit non-existence within a defined search scope?", "kind": "exception", "answer_data": [ "assertion-evidence-absence" ] } ], "data_elements": [ { "id": "assertion-evidence-evidence", "name": "evidence", "description": "Proposed structured answer group: source,recordRef,retrievedAt,validation. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "assertion-evidence-dispute", "name": "dispute", "description": "Proposed structured answer group: claims,resolutionAuthority,status. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "assertion-evidence-absence", "name": "absence", "description": "Proposed structured answer group: reason,coverageScope,searchTime. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "assertion-evidence-artifact", "name": "Evidence quality and counterclaims assertion artifact", "description": "Versioned evidence quality and counterclaims assertion and authorized evidence references; referenced contracts and organization records retain their masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Issuer-qualified master ID, else Dimension UUID; immutable revision and exact digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "relationship-stewardship", "name": "Mastership, freshness and permitted disclosure", "description": "Qualified relationship assertion for mastership, freshness and permitted disclosure. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "relationship-stewardship-record", "name": "Mastership, freshness and permitted disclosure record", "description": "Qualified relationship assertion for mastership, freshness and permitted disclosure. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "relationship-stewardship-q01", "text": "Which system and role master this relationship record and when is review due?", "kind": "ownership", "answer_data": [ "relationship-stewardship-stewardship" ] }, { "id": "relationship-stewardship-q02", "text": "Which fields or endpoints are confidential, redacted or publicly reusable under a stated access policy and source license?", "kind": "access", "answer_data": [ "relationship-stewardship-disclosure" ] }, { "id": "relationship-stewardship-q03", "text": "How does a redacted projection preserve the distinction between withheld and absent information while retaining an authorized evidence trail?", "kind": "privacy", "answer_data": [ "relationship-stewardship-projection" ] } ], "data_elements": [ { "id": "relationship-stewardship-stewardship", "name": "stewardship", "description": "Proposed structured answer group: master,steward,reviewDue. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "relationship-stewardship-disclosure", "name": "disclosure", "description": "Proposed structured answer group: fieldClasses, policyRef,licenseRef. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "relationship-stewardship-projection", "name": "projection", "description": "Proposed structured answer group: redactions,reasonCodes,auditRef. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "relationship-stewardship-artifact", "name": "Mastership, freshness and permitted disclosure assertion artifact", "description": "Versioned mastership, freshness and permitted disclosure assertion and authorized evidence references; referenced contracts and organization records retain their masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Issuer-qualified master ID, else Dimension UUID; immutable revision and exact digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "relation-exchange-and-operational-acceptance", "name": "Exchange and operational acceptance", "description": "Inter-organizational exchange and operational acceptance.", "rationale": "Keeps relationship-owned assertions separate from endpoint identities and operational masters; a proposed Vercy grouping, not a normative source hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "external-mapping", "name": "Versioned external mappings", "description": "Qualified relationship assertion for versioned external mappings. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005" ], "findings": [ { "id": "external-mapping-record", "name": "Versioned external mappings record", "description": "Qualified relationship assertion for versioned external mappings. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005" ], "questions": [ { "id": "external-mapping-q01", "text": "Which exact relationship kinds map to ORG, GLEIF RR-CDF, BODS or OCDS, and which merely have broader or narrower correspondence?", "kind": "interoperability", "answer_data": [ "external-mapping-mapping" ] }, { "id": "external-mapping-q02", "text": "What qualifiers, time precision, multi-party structure or assertion status would be lost in each export?", "kind": "interoperability", "answer_data": [ "external-mapping-losses" ] }, { "id": "external-mapping-q03", "text": "Which pinned schema/profile and round-trip fixtures demonstrate accepted mappings rather than an unsupported conformance claim?", "kind": "validation", "answer_data": [ "external-mapping-acceptance" ] } ], "data_elements": [ { "id": "external-mapping-mapping", "name": "mapping", "description": "Proposed structured answer group: sourcePath,targetTerm,relationType,version. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005" ] }, { "id": "external-mapping-losses", "name": "losses", "description": "Proposed structured answer group: fields,meaning,requiredWarnings. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005" ] }, { "id": "external-mapping-acceptance", "name": "acceptance", "description": "Proposed structured answer group: schemaDigest,fixtures,result. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "external-mapping-artifact", "name": "Versioned external mappings assertion artifact", "description": "Versioned versioned external mappings assertion and authorized evidence references; referenced contracts and organization records retain their masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Issuer-qualified master ID, else Dimension UUID; immutable revision and exact digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "maintenance-acceptance", "name": "Safe relationship maintenance operations", "description": "Qualified relationship assertion for safe relationship maintenance operations. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "findings": [ { "id": "maintenance-acceptance-record", "name": "Safe relationship maintenance operations record", "description": "Qualified relationship assertion for safe relationship maintenance operations. Retain source scope and do not infer legal or commercial authority from its mere existence.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "questions": [ { "id": "maintenance-acceptance-q01", "text": "Which policy permits an agent to record, revise, dispute or retire the local assertion without creating or ending the real-world relationship?", "kind": "authority", "answer_data": [ "maintenance-acceptance-operationauthority" ] }, { "id": "maintenance-acceptance-q02", "text": "Which expected revision and graph checks must pass before an append, and what conflict response preserves concurrent evidence?", "kind": "validation", "answer_data": [ "maintenance-acceptance-preconditions" ] }, { "id": "maintenance-acceptance-q03", "text": "What post-write checks and compensating revision restore correctness without deleting provenance or silently widening disclosure?", "kind": "process", "answer_data": [ "maintenance-acceptance-recovery" ] } ], "data_elements": [ { "id": "maintenance-acceptance-operationauthority", "name": "operationAuthority", "description": "Proposed structured answer group: operation,policy,delegation,excludedEffects. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "maintenance-acceptance-preconditions", "name": "preconditions", "description": "Proposed structured answer group: expectedHead,graphChecks,onConflict. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "maintenance-acceptance-recovery", "name": "recovery", "description": "Proposed structured answer group: postChecks, compensationRef,provenancePreservation. Preserve attributed unknowns; nested executable schema and profile constraints remain a hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "maintenance-acceptance-artifact", "name": "Safe relationship maintenance operations assertion artifact", "description": "Versioned safe relationship maintenance operations assertion and authorized evidence references; referenced contracts and organization records retain their masters.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Issuer-qualified master ID, else Dimension UUID; immutable revision and exact digest separately. Timestamp alone is not identity.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "resolve-relationship", "name": "Resolve qualified relationship", "description": "Compare identities and scopes without merging parallel relations.", "inputs": [ "Master IDs", "Endpoint references", "Kind and scope" ], "outputs": [ "Match, candidates or explicit unknown" ], "preconditions": [ "Read permission and kind definition" ], "effects": [ "Read-only; identity ambiguity returns candidates, never automatic same-as" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "inspect-relationship-graph", "name": "Inspect qualified graph", "description": "Traverse asserted or explicitly derived relationships at a declared time.", "inputs": [ "Start organization", "Kinds", "Time slice", "Allowed rule version" ], "outputs": [ "Evidence-bearing paths and unknown gaps" ], "preconditions": [ "Authorized endpoints and reviewed kind-specific graph rules" ], "effects": [ "Read-only; unsupported transitivity or cycles yield warnings/rejection" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "record-relationship-assertion", "name": "Record attributed assertion", "description": "Append evidence-backed claim without creating a real-world agreement.", "inputs": [ "Claimant and capacity", "Relationship kind/scope", "Evidence refs", "Expected head" ], "outputs": [ "New immutable local assertion or conflict report" ], "preconditions": [ "Contributor delegation", "Resolved master scope", "Schema and graph checks" ], "effects": [ "Local append only; no signatures, payments or grants; failed checks leave head unchanged" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "revise-relationship-lifecycle", "name": "Append lifecycle revision", "description": "Separate effective termination, correction and record retirement.", "inputs": [ "Prior revision", "Change reason and evidence", "Effective/recorded time" ], "outputs": [ "Successor revision and lineage" ], "preconditions": [ "Write authority", "Expected head and retention check" ], "effects": [ "Append with compensating revision for mistakes; never erase provenance or terminate a contract" ], "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "record-relationship-dispute", "name": "Register counterclaim", "description": "Preserve incompatible positions for authorized review.", "inputs": [ "Contested assertion", "Counterevidence", "Reviewer-policy reference" ], "outputs": [ "Attributed contested set and review status" ], "preconditions": [ "Permitted evidence access", "No automated truth ranking by recency alone" ], "effects": [ "Append dispute; no endpoint coercion or automatic adverse decision" ], "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "project-relationship", "name": "Export permitted projection", "description": "Apply versioned vocabulary mapping with declared losses.", "inputs": [ "Authorized fields", "Target schema/profile", "Mapping fixtures" ], "outputs": [ "Projection and loss report or refusal" ], "preconditions": [ "Disclosure authority", "Verified target compatibility" ], "effects": [ "Export only scoped data; unsupported arity/meaning produces refusal; publication needs explicit authority" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005" ] } ], "composition": [ { "target": "WM-ORG-001", "relation": "REFERENCE", "purpose": "Proposed endpoint-identity reference, not a frozen approved ledger edge.", "required": true, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "WM-ORG-014", "relation": "REFERENCE", "purpose": "Proposed customer/account lifecycle delegation where relevant.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "WM-ORG-015", "relation": "REFERENCE", "purpose": "Proposed supplier qualification delegation where relevant.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "https://www.w3.org/TR/vocab-org/", "relation": "ALIGN", "purpose": "Candidate generic links; relationship kind semantics require a profile.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "https://standard.openownership.org/en/latest/standard/reference.html", "relation": "ALIGN", "purpose": "Candidate organization-interest subset only, with explicit endpoint and component loss.", "required": false, "source_refs": [ "SRC-004" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the relationship-data owner and steward.", "Identify organization, contract, ownership and commercial masters.", "Bind delegation, access, dispute and retention policies before writes." ], "namespace_guidance": "Use a master-qualified relationship ID distinct from its endpoint tuple, type, direction and revisions; never merge parallel scopes by names.", "registry_links": [ "Organization registry", "Relationship registry", "Evidence and assertion revision registry", "Model and policy registry" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve source definition, endpoint roles, scope and valid interval.", "No default equivalence of consolidation, equity, votes, affiliation or supply; no default graph closure." ], "patch_rules": [ "Use namespaced extensions pinned to the base digest with pre/post validation.", "Append corrections under expected-head check, retaining evidence and counterclaims." ], "compatibility_rules": [ "Kind, direction, arity or control-basis changes require explicit migration and loss report.", "Do not coerce date-only effective values into invented precise timestamps." ] }, "artifact_rules": { "identity_priority": [ "Authoritative relationship master identifier", "Governed issuer-qualified URI", "Dimension-generated UUID with namespace" ], "timestamp_rule": "RFC 3339 with seconds and explicit offset or Z for precise recording/observation instants; retain date-only effective precision separately.", "serial_naming_rule": "Relationship artifact-kind prefix, escaped stable identifier and immutable revision; time is optional display metadata.", "integrity_rule": "Verify exact-byte digests and revision references; hashes prove neither truth nor commercial authority." }, "policies": [ "Relationship assertion does not authorize transactions, contract signatures or legal control decisions.", "Do not infer missing, withheld or unreported relationships as proven non-existence.", "Only kind-specific reviewed graph rules may derive links; retain inputs and time slice.", "Conflicting attributed assertions coexist until an authorized resolution." ], "crud": { "read": [ "Read Dimension policy, kind definition, endpoint roles, source scope, time and assurance before using a relationship." ], "create": [ "Create only an authorized attributed assertion; preserve uncertain participant identity and require a distinct relationship ID." ], "update": [ "Append with expected-head and kind-specific graph checks; keep real-world change separate from record correction." ], "delete": [ "Apply retention/legal-hold policy and authorized tombstones; never terminate contracts or delete endpoint organizations as a side effect." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Sets federation and delegation boundaries." ] }, { "name": "Relationship steward", "responsibilities": [ "Owns kind, endpoint and scope interpretation." ] }, { "name": "Assertion contributor", "responsibilities": [ "Adds attributable claims within authorized scope." ] }, { "name": "Reviewer", "responsibilities": [ "Assesses conflicting evidence and proposed graph mappings." ] }, { "name": "Custodian", "responsibilities": [ "Maintains access-filtered projections and retention." ] } ], "access": { "default_rule": "Deny unless the owning Dimension grants purpose-specific access.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Explicit recorded, time-limited delegation only; public endpoint names do not make private relationship evidence public." ], "audit_requirements": [ "Record actor, scope, source revision, conflict decision and disclosure without tokens or private source copies." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Dimension identity, delegation and access policy", "Pinned relationship model and kind profile", "Endpoint/master references, effective time and evidence", "Safe append, dispute, mapping, extension and retirement checks" ] } }, "coverage": { "claim": "Bounded proposed inter-organizational relationship contract with twelve records and thirty-six questions; no independent corroboration, universal legal semantics or executed adapter conformance.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Qualified ID and parallel relationship scope." }, { "dimension": "classification", "status": "covered", "notes": "Versioned kind, exclusions and control basis." }, { "dimension": "direct properties", "status": "covered", "notes": "Direction, roles, arity, scope and qualified interest." }, { "dimension": "recognition", "status": "covered", "notes": "Attributed evidence and misleading shared-name/address signals." }, { "dimension": "capabilities", "status": "covered", "notes": "Six proposed relationship-record operations, not real-world commercial authority." }, { "dimension": "lifecycle", "status": "covered", "notes": "Real-world state versus publisher retirement and corrections." }, { "dimension": "temporal", "status": "covered", "notes": "Effective interval, precision, observation and recording." }, { "dimension": "relationships", "status": "covered", "notes": "Referenced endpoints and commercial masters." }, { "dimension": "provenance", "status": "covered", "notes": "Assertion source and graph derivation are explicit." }, { "dimension": "ownership", "status": "covered", "notes": "Relationship-data steward distinct from endpoint or equity owner." }, { "dimension": "access", "status": "covered", "notes": "Purpose/field restrictions and redaction reasons." }, { "dimension": "retention", "status": "covered", "notes": "Policy-bound tombstones preserve provenance." }, { "dimension": "interoperability", "status": "covered", "notes": "Kind-qualified mappings and loss declarations." }, { "dimension": "Physical geometry/material", "status": "not-applicable", "notes": "Relational object; physical endpoint properties remain delegated." }, { "dimension": "Independent review and executable acceptance", "status": "gap", "notes": "External attempts timed out; nested schemas and round-trip fixtures are not implemented." }, { "dimension": "validation", "status": "gap", "notes": "Question/answer traceability and profile checks are specified; executable nested schemas and round-trip/graph fixtures are deferred." } ], "known_omissions": [ "Claude and Grok each timed out on the sole bounded attempt; Codex-only reviewable-draft, no independent corroboration.", "Selected clauses only; exact dated source pins, source licenses and complete normative applicability remain to be verified.", "Full RR-CDF XSD fields, BODS/OCDS constraints and real round-trip fixtures have not been validated.", "No executable nested answer schema, identity resolver, graph rule engine or commercial operation is delivered.", "Jurisdiction-specific partnership, control, reporting-exception and disclosure law remain adopter-owned profile work.", "Multi-party and cyclic graph fixtures, relation-ledger approval and independent review remain open." ], "conflicts": [], "regional_assumptions": [ "Generic relationship is not a universal legal category. Accounting consolidation and beneficial ownership must retain their source definitions and jurisdictions." ], "adversarial_checks": [ "Reject arbitrary linkedTo transitivity.", "Reject shared branding as legal control.", "Reject publisher record closure as real-world termination.", "Reject absence or non-disclosure as a negative fact.", "Reject pairwise flattening of multi-party arrangements without loss.", "Reject PROV activity association as equivalent to partnership.", "Reject scope-free percentages or indirect graph-derived ownership.", "Reject local record update as power to bind an organization." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "relationship", "status": "accepted", "rationale": "One source-qualified relationship with explicit participants, direction, scope, time and assertions. Endpoint identities, ownership and commercial lifecycles remain referenced." }, "decisions": [ { "concept": "Relationship identity and graph", "disposition": "accepted with limitations", "rationale": "Parallel scopes, direct versus derived edges and kind-specific constraints prevent universal hierarchy assumptions." }, { "concept": "Control, interest and partnership", "disposition": "accepted with limitations", "rationale": "Consolidation, ownership, supply and affiliation retain source definitions and cannot be inferred as equivalent." }, { "concept": "Time and evidence", "disposition": "accepted", "rationale": "Publisher record closure differs from real-world termination; counterclaims and missing/withheld values are explicit." }, { "concept": "Operations and composition", "disposition": "accepted with limitations", "rationale": "Record-level operations confer no commercial authority; model references remain proposed and loss-aware." }, { "concept": "Source and executable conformance", "disposition": "deferred", "rationale": "Selected primary-source clauses inform design; exact pins, nested schemas and round-trip fixtures remain open." }, { "concept": "Independent review", "disposition": "accepted with mandatory hold", "rationale": "Both external attempts timed out; frozen Codex self-audit is not independent review." } ], "publicationHolds": [ "Claude and Grok each timed out once. Codex-only result and self-review remain reviewable-draft, never canonical.", "Source release pins, licenses, full RR-CDF XSD and BODS/OCDS normative constraints are not completely verified.", "No executable nested answer schema, identity resolver, graph-rule engine or real round-trip fixtures delivered.", "Jurisdiction-specific partnership, control and disclosure law remain adopter-owned profile work; no legal conclusions.", "Composition edges are proposed; multi-party/cyclic graph fixtures and independent review remain pending.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Independent external review and precise source/version/license pins.", "Executable loss-aware mapping and graph fixtures.", "Jurisdiction-specific relationship-kind profiles and approved typed composition." ] }, "statistics": { "sources": 7, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }