# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T01:26:35Z", "synthesisSha256": "6dec828608b321023a5496ad17cc217cd90b7e4768668d1b260c6dc71dfca765", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ORG-006", "registryId": "vr.wm-org-006", "name": "Membership", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "relationship", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ORG.MEM" ], "tags": [ "membership", "soc.org.mem" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-org-006-membership/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-org-006", "model": { "registry_id": "vr.wm-org-006", "model_id": "WM-ORG-006", "name": "Membership", "entry_kind": "relationship", "purpose": "Represent one governed, qualified relationship between a member agent and an organization or group, including admission, roles, validity, standing, terms, lifecycle, evidence and privacy without depending on storage or interface format.", "scope_statement": "Owns membership relationship identity, member and organization bindings, governing scheme and type, admission basis and decision effect, role bindings, validity and standing, term references, renewal, suspension, reinstatement and ending events, party assertions, proof projections, privacy and interoperability while external systems own agents, organizations, roles, posts, activities, policies, payments, subscriptions, credentials, access grants, decisions and evidence objects.", "in_scope": [ "Membership identity, member and organization or group references, membership scheme, type, classification and non-equivalence boundaries", "Application, nomination, eligibility, authority, admission, role bindings, validity, standing, renewal, suspension, reinstatement, resignation, termination and revocation", "Terms, duties, fee and benefit references, assertions, evidence, attestations, directories, privacy, retention, disputes, provenance and exchange" ], "out_of_scope": [ "Employment, office-holding, citizenship, licensing, subscription, participation, affiliation and access-entitlement master lifecycles", "Member, organization, group, role, post, activity, project, policy, payment, credential, access-grant, decision and evidence master records", "Universal eligibility, admission, disciplinary, due-process, fee, privacy or retention rules, or automatic authority for an agent to admit, suspend, revoke or disclose membership" ], "boundary_notes": [ { "neighbor": "Employment", "distinction": "Employment is a work relationship with labour-status, term and assignment semantics; Membership is governed belonging under a membership scheme and never imports employment classification or lifecycle.", "source_refs": [ "SRC-001", "SRC-006" ] }, { "neighbor": "Role, Post and Office", "distinction": "A role is a reusable concept, a post or office can exist independently and a membership role binding states what role a member holds through this relationship and when.", "source_refs": [ "SRC-001", "SRC-007" ] }, { "neighbor": "Participation and Affiliation", "distinction": "Participation is involvement in an activity and affiliation can be informal or broadly asserted; canonical Membership requires a qualified scheme, parties, basis, standing and provenance.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "Subscription, Payment and Benefit", "distinction": "Recurring service and financial records may be conditions or consequences of membership but retain separate identity, state and execution.", "source_refs": [ "SRC-004" ] }, { "neighbor": "Credential and Directory Entry", "distinction": "A credential, badge, roster or listing is an issuer-controlled proof or projection whose status may diverge from the authoritative membership relationship.", "source_refs": [ "SRC-001", "SRC-005" ] }, { "neighbor": "Access Entitlement and Policy", "distinction": "Membership may be an input to permission decisions, but policy rules, grants, evaluation and enforcement remain external and membership never guarantees access.", "source_refs": [ "SRC-004", "SRC-008" ] } ] }, "sources": [ { "id": "SRC-001", "title": "The Organization Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-org/", "version_or_date": "W3C Recommendation, 16 January 2014", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:20:00Z", "relevance": "Defines org:Membership as a qualified n-ary relationship among an agent, organization and role, supports duration, and distinguishes membership from a post that may exist without a holder." }, { "id": "SRC-002", "title": "Time Ontology in OWL", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/owl-time/", "version_or_date": "W3C Recommendation, 19 October 2017; current 15 November 2022 edition", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:20:00Z", "relevance": "Provides instants, intervals, durations and temporal relations for membership validity, role bindings, decisions and non-contiguous periods." }, { "id": "SRC-003", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation, 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:20:00Z", "relevance": "Provides entities, activities, agents, attribution, delegation, revision and qualified influence for admission, lifecycle, evidence and correction provenance." }, { "id": "SRC-004", "title": "ODRL Information Model 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "W3C Recommendation, 15 February 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:20:00Z", "relevance": "Provides policy, permission, prohibition, duty, party, action and constraint concepts for referenced membership terms without making policy evaluation part of the relationship." }, { "id": "SRC-005", "title": "Verifiable Credentials Data Model v2.0", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vc-data-model-2.0/", "version_or_date": "W3C Recommendation, 15 May 2025", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:20:00Z", "relevance": "Provides issuer, credential subject, validity, status, schema, terms of use and evidence for optional portable membership attestations; the credential remains evidence, not the membership." }, { "id": "SRC-006", "title": "LegalRuleML Core Specification Version 1.0", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/os/legalruleml-core-spec-v1.0-os.html", "version_or_date": "OASIS Standard, 30 August 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:20:00Z", "relevance": "Provides authority, jurisdiction, role and legal-rule metadata patterns for memberships constituted by law, charter, bylaws, resolution or other governed instruments." }, { "id": "SRC-007", "title": "SKOS Simple Knowledge Organization System Reference", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/skos-reference/", "version_or_date": "W3C Recommendation, 18 August 2009", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:20:00Z", "relevance": "Provides stable concept schemes, identifiers, labels, notations, hierarchies and mappings for membership types, roles, standing and reason vocabularies." }, { "id": "SRC-008", "title": "General Data Protection Regulation", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/reg/2016/679/oj", "version_or_date": "Regulation (EU) 2016/679, 27 April 2016", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:20:00Z", "relevance": "Provides an EU privacy profile for purpose limitation, minimization, accuracy, retention, security, access and rectification where membership data concerns a natural person." }, { "id": "SRC-009", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "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-06T01:20:00Z", "relevance": "Defines interoperable timestamps with seconds and explicit UTC relation for admission, lifecycle, assertion and knowledge times." } ], "structure": { "bundles": [ { "id": "relationship-identity-parties-and-scheme", "name": "Relationship identity, parties and scheme", "description": "Identifies one membership and the member, organization or group and governing membership scheme.", "rationale": "A direct memberOf edge is insufficient when role, validity, basis and standing must be qualified and independently governed.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ], "layers": [ { "id": "membership-master-identity", "name": "Membership master identity", "description": "Stable relationship identity, source systems, aliases and successor lineage.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "authoritative-membership-identifier-and-master-system", "name": "Authoritative membership identifier and master system", "description": "The stable relationship identifier, issuer, namespace, master system, local keys and resolution status.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "authoritative-membership-identifier-and-master-system-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for authoritative membership identifier and master system?", "kind": "identity", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "authoritative-membership-identifier-and-master-system-q02", "text": "Which member, organization, authority, source and evidence establishes authoritative membership identifier and master system, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "authoritative-membership-identifier-and-master-system-q03", "text": "How may authoritative membership identifier and master system be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "authoritative-membership-identifier-and-master-system-data", "name": "Authoritative membership identifier and master system data", "description": "Structured, source-qualified answer data for authoritative membership identifier and master system.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "authoritative-membership-identifier-and-master-system-record", "name": "Authoritative membership identifier and master system record", "description": "Versioned evidence-bearing record for authoritative membership identifier and master system with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus authoritative-membership-identifier-and-master-system assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "duplicate-merge-split-reissue-and-successor-lineage", "name": "Duplicate, merge, split, reissue and successor lineage", "description": "Reconciliation and successor rules that preserve cited identities and prior assertions.", "source_refs": [ "SRC-003" ], "questions": [ { "id": "duplicate-merge-split-reissue-and-successor-lineage-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for duplicate, merge, split, reissue and successor lineage?", "kind": "lifecycle", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "duplicate-merge-split-reissue-and-successor-lineage-q02", "text": "Which member, organization, authority, source and evidence establishes duplicate, merge, split, reissue and successor lineage, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "duplicate-merge-split-reissue-and-successor-lineage-q03", "text": "How may duplicate, merge, split, reissue and successor lineage be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "duplicate-merge-split-reissue-and-successor-lineage-data", "name": "Duplicate, merge, split, reissue and successor lineage data", "description": "Structured, source-qualified answer data for duplicate, merge, split, reissue and successor lineage.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "duplicate-merge-split-reissue-and-successor-lineage-record", "name": "Duplicate, merge, split, reissue and successor lineage record", "description": "Versioned evidence-bearing record for duplicate, merge, split, reissue and successor lineage with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus duplicate-merge-split-reissue-and-successor-lineage assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "parties-type-and-governing-scheme", "name": "Parties, type and governing scheme", "description": "Member and organization bindings plus profile-qualified classification.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "findings": [ { "id": "member-agent-and-organization-or-group-bindings", "name": "Member agent and organization or group bindings", "description": "Typed references to the member agent and admitting organization or governed group with identity authority and intervals.", "source_refs": [ "SRC-001" ], "questions": [ { "id": "member-agent-and-organization-or-group-bindings-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for member agent and organization or group bindings?", "kind": "relationship", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "member-agent-and-organization-or-group-bindings-q02", "text": "Which member, organization, authority, source and evidence establishes member agent and organization or group bindings, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "member-agent-and-organization-or-group-bindings-q03", "text": "How may member agent and organization or group bindings be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "member-agent-and-organization-or-group-bindings-data", "name": "Member agent and organization or group bindings data", "description": "Structured, source-qualified answer data for member agent and organization or group bindings.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001" ] } ], "artifacts": [ { "id": "member-agent-and-organization-or-group-bindings-record", "name": "Member agent and organization or group bindings record", "description": "Versioned evidence-bearing record for member agent and organization or group bindings with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus member-agent-and-organization-or-group-bindings assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-001" ] } ], "inline_only_rationale": null }, { "id": "membership-type-profile-classification-and-scheme-version", "name": "Membership type, profile, classification and scheme version", "description": "Versioned type and profile concepts, scheme authority, applicability and class-distinguishing criteria.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "questions": [ { "id": "membership-type-profile-classification-and-scheme-version-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for membership type, profile, classification and scheme version?", "kind": "classification", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "membership-type-profile-classification-and-scheme-version-q02", "text": "Which member, organization, authority, source and evidence establishes membership type, profile, classification and scheme version, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "membership-type-profile-classification-and-scheme-version-q03", "text": "How may membership type, profile, classification and scheme version be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "membership-type-profile-classification-and-scheme-version-data", "name": "Membership type, profile, classification and scheme version data", "description": "Structured, source-qualified answer data for membership type, profile, classification and scheme version.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "membership-type-profile-classification-and-scheme-version-record", "name": "Membership type, profile, classification and scheme version record", "description": "Versioned evidence-bearing record for membership type, profile, classification and scheme version with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus membership-type-profile-classification-and-scheme-version assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "admission-eligibility-and-authority", "name": "Admission, eligibility and authority", "description": "Explains how membership is proposed, evaluated and admitted under a governing basis.", "rationale": "Membership existence and standing require attributable authority and evidence, not directory presence, payment or self-assertion alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ], "layers": [ { "id": "application-nomination-and-eligibility", "name": "Application, nomination and eligibility", "description": "External request, sponsorship and eligibility assertions linked to this relationship.", "source_refs": [ "SRC-003", "SRC-006" ], "findings": [ { "id": "application-nomination-invitation-and-sponsor-reference", "name": "Application, nomination, invitation and sponsor reference", "description": "References the initiating request or act, nominator, sponsor, requested class, time and provenance.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "application-nomination-invitation-and-sponsor-reference-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for application, nomination, invitation and sponsor reference?", "kind": "provenance", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "application-nomination-invitation-and-sponsor-reference-q02", "text": "Which member, organization, authority, source and evidence establishes application, nomination, invitation and sponsor reference, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "application-nomination-invitation-and-sponsor-reference-q03", "text": "How may application, nomination, invitation and sponsor reference be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "application-nomination-invitation-and-sponsor-reference-data", "name": "Application, nomination, invitation and sponsor reference data", "description": "Structured, source-qualified answer data for application, nomination, invitation and sponsor reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "application-nomination-invitation-and-sponsor-reference-record", "name": "Application, nomination, invitation and sponsor reference record", "description": "Versioned evidence-bearing record for application, nomination, invitation and sponsor reference with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus application-nomination-invitation-and-sponsor-reference assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "eligibility-criteria-evidence-exception-and-expiry", "name": "Eligibility criteria, evidence, exception and expiry", "description": "Versioned criteria, evidence, evaluator, exception authority, decision scope and freshness without importing assessments.", "source_refs": [ "SRC-006", "SRC-007" ], "questions": [ { "id": "eligibility-criteria-evidence-exception-and-expiry-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for eligibility criteria, evidence, exception and expiry?", "kind": "validation", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "eligibility-criteria-evidence-exception-and-expiry-q02", "text": "Which member, organization, authority, source and evidence establishes eligibility criteria, evidence, exception and expiry, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "eligibility-criteria-evidence-exception-and-expiry-q03", "text": "How may eligibility criteria, evidence, exception and expiry be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "eligibility-criteria-evidence-exception-and-expiry-data", "name": "Eligibility criteria, evidence, exception and expiry data", "description": "Structured, source-qualified answer data for eligibility criteria, evidence, exception and expiry.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "eligibility-criteria-evidence-exception-and-expiry-record", "name": "Eligibility criteria, evidence, exception and expiry record", "description": "Versioned evidence-bearing record for eligibility criteria, evidence, exception and expiry with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus eligibility-criteria-evidence-exception-and-expiry assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "decision-basis-and-effective-admission", "name": "Decision, basis and effective admission", "description": "The accountable admission or rejection and its relationship effect.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ], "findings": [ { "id": "governing-charter-bylaw-rule-resolution-or-agreement", "name": "Governing charter, bylaw, rule, resolution or agreement", "description": "Typed references to the constitutive or contractual basis, authority, jurisdiction, version and precedence scope.", "source_refs": [ "SRC-006" ], "questions": [ { "id": "governing-charter-bylaw-rule-resolution-or-agreement-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for governing charter, bylaw, rule, resolution or agreement?", "kind": "authority", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "governing-charter-bylaw-rule-resolution-or-agreement-q02", "text": "Which member, organization, authority, source and evidence establishes governing charter, bylaw, rule, resolution or agreement, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "governing-charter-bylaw-rule-resolution-or-agreement-q03", "text": "How may governing charter, bylaw, rule, resolution or agreement be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "governing-charter-bylaw-rule-resolution-or-agreement-data", "name": "Governing charter, bylaw, rule, resolution or agreement data", "description": "Structured, source-qualified answer data for governing charter, bylaw, rule, resolution or agreement.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-006" ] } ], "artifacts": [ { "id": "governing-charter-bylaw-rule-resolution-or-agreement-record", "name": "Governing charter, bylaw, rule, resolution or agreement record", "description": "Versioned evidence-bearing record for governing charter, bylaw, rule, resolution or agreement with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus governing-charter-bylaw-rule-resolution-or-agreement assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "admission-rejection-decision-conditions-and-effective-time", "name": "Admission or rejection decision, conditions and effective time", "description": "Decision maker, authority, reason, conditions, appeal state and distinct decision, effective and knowledge times.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ], "questions": [ { "id": "admission-rejection-decision-conditions-and-effective-time-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for admission or rejection decision, conditions and effective time?", "kind": "decision", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "admission-rejection-decision-conditions-and-effective-time-q02", "text": "Which member, organization, authority, source and evidence establishes admission or rejection decision, conditions and effective time, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "admission-rejection-decision-conditions-and-effective-time-q03", "text": "How may admission or rejection decision, conditions and effective time be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "admission-rejection-decision-conditions-and-effective-time-data", "name": "Admission or rejection decision, conditions and effective time data", "description": "Structured, source-qualified answer data for admission or rejection decision, conditions and effective time.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ] } ], "artifacts": [ { "id": "admission-rejection-decision-conditions-and-effective-time-record", "name": "Admission or rejection decision, conditions and effective time record", "description": "Versioned evidence-bearing record for admission or rejection decision, conditions and effective time with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus admission-rejection-decision-conditions-and-effective-time assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "roles-scope-and-participation-context", "name": "Roles, scope and participation context", "description": "Qualifies which roles are held through membership and where they apply.", "rationale": "A membership can carry several role bindings, while posts, duties and activities retain independent identity and lifecycle.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007" ], "layers": [ { "id": "role-and-post-binding", "name": "Role and post binding", "description": "Membership roles, scopes and optional post references with their own intervals.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "findings": [ { "id": "role-concept-scope-unit-and-validity", "name": "Role concept, scope, unit and validity", "description": "Versioned role reference, organizational or domain scope, effective interval and profile-specific cardinality.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "questions": [ { "id": "role-concept-scope-unit-and-validity-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for role concept, scope, unit and validity?", "kind": "relationship", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "role-concept-scope-unit-and-validity-q02", "text": "Which member, organization, authority, source and evidence establishes role concept, scope, unit and validity, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "role-concept-scope-unit-and-validity-q03", "text": "How may role concept, scope, unit and validity be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "role-concept-scope-unit-and-validity-data", "name": "Role concept, scope, unit and validity data", "description": "Structured, source-qualified answer data for role concept, scope, unit and validity.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "role-concept-scope-unit-and-validity-record", "name": "Role concept, scope, unit and validity record", "description": "Versioned evidence-bearing record for role concept, scope, unit and validity with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus role-concept-scope-unit-and-validity assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "role-held-through-membership-versus-independent-post", "name": "Role held through membership versus independent post", "description": "Distinguishes a member's role binding from an independently existing post that can be vacant or held by another route.", "source_refs": [ "SRC-001" ], "questions": [ { "id": "role-held-through-membership-versus-independent-post-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for role held through membership versus independent post?", "kind": "classification", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "role-held-through-membership-versus-independent-post-q02", "text": "Which member, organization, authority, source and evidence establishes role held through membership versus independent post, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "role-held-through-membership-versus-independent-post-q03", "text": "How may role held through membership versus independent post be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "role-held-through-membership-versus-independent-post-data", "name": "Role held through membership versus independent post data", "description": "Structured, source-qualified answer data for role held through membership versus independent post.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] } ], "artifacts": [ { "id": "role-held-through-membership-versus-independent-post-record", "name": "Role held through membership versus independent post record", "description": "Versioned evidence-bearing record for role held through membership versus independent post with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus role-held-through-membership-versus-independent-post assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-001" ] } ], "inline_only_rationale": null } ] }, { "id": "participation-affiliation-and-non-equivalence", "name": "Participation, affiliation and non-equivalence", "description": "References activities and adjacent relationships without conflating them with membership.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "findings": [ { "id": "participation-activity-project-and-contribution-references", "name": "Participation, activity, project and contribution references", "description": "Time-qualified links to externally mastered activities, projects and contributions associated with membership.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "participation-activity-project-and-contribution-references-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for participation, activity, project and contribution references?", "kind": "relationship", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "participation-activity-project-and-contribution-references-q02", "text": "Which member, organization, authority, source and evidence establishes participation, activity, project and contribution references, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "participation-activity-project-and-contribution-references-q03", "text": "How may participation, activity, project and contribution references be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "participation-activity-project-and-contribution-references-data", "name": "Participation, activity, project and contribution references data", "description": "Structured, source-qualified answer data for participation, activity, project and contribution references.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "participation-activity-project-and-contribution-references-record", "name": "Participation, activity, project and contribution references record", "description": "Versioned evidence-bearing record for participation, activity, project and contribution references with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus participation-activity-project-and-contribution-references assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "employment-office-subscription-citizenship-licence-and-access-boundary", "name": "Employment, office, subscription, citizenship, licence and access boundary", "description": "Typed non-equivalence and optional relationship links that prevent inference of membership from neighboring statuses.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "questions": [ { "id": "employment-office-subscription-citizenship-licence-and-access-boundary-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for employment, office, subscription, citizenship, licence and access boundary?", "kind": "interoperability", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "employment-office-subscription-citizenship-licence-and-access-boundary-q02", "text": "Which member, organization, authority, source and evidence establishes employment, office, subscription, citizenship, licence and access boundary, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "employment-office-subscription-citizenship-licence-and-access-boundary-q03", "text": "How may employment, office, subscription, citizenship, licence and access boundary be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "employment-office-subscription-citizenship-licence-and-access-boundary-data", "name": "Employment, office, subscription, citizenship, licence and access boundary data", "description": "Structured, source-qualified answer data for employment, office, subscription, citizenship, licence and access boundary.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "employment-office-subscription-citizenship-licence-and-access-boundary-record", "name": "Employment, office, subscription, citizenship, licence and access boundary record", "description": "Versioned evidence-bearing record for employment, office, subscription, citizenship, licence and access boundary with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus employment-office-subscription-citizenship-licence-and-access-boundary assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "standing-validity-and-lifecycle", "name": "Standing, validity and lifecycle", "description": "Represents current and historic membership condition, intervals and governed transitions.", "rationale": "Standing, rights and duties may change independently, and suspension or expiry must not erase relationship identity or prior validity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-009" ], "layers": [ { "id": "validity-state-and-observation", "name": "Validity, state and observation", "description": "Relationship validity intervals, asserted standing and observed freshness.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ], "findings": [ { "id": "proposed-pending-active-suspended-ended-rejected-and-revoked-state", "name": "Proposed, pending, active, suspended, ended, rejected and revoked state", "description": "Profile-qualified relationship state, source, authority, valid interval, confidence and explicit unknown status.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "proposed-pending-active-suspended-ended-rejected-and-revoked-state-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for proposed, pending, active, suspended, ended, rejected and revoked state?", "kind": "state", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "proposed-pending-active-suspended-ended-rejected-and-revoked-state-q02", "text": "Which member, organization, authority, source and evidence establishes proposed, pending, active, suspended, ended, rejected and revoked state, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "proposed-pending-active-suspended-ended-rejected-and-revoked-state-q03", "text": "How may proposed, pending, active, suspended, ended, rejected and revoked state be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "proposed-pending-active-suspended-ended-rejected-and-revoked-state-data", "name": "Proposed, pending, active, suspended, ended, rejected and revoked state data", "description": "Structured, source-qualified answer data for proposed, pending, active, suspended, ended, rejected and revoked state.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "proposed-pending-active-suspended-ended-rejected-and-revoked-state-record", "name": "Proposed, pending, active, suspended, ended, rejected and revoked state record", "description": "Versioned evidence-bearing record for proposed, pending, active, suspended, ended, rejected and revoked state with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus proposed-pending-active-suspended-ended-rejected-and-revoked-state assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "valid-decision-event-observation-and-knowledge-time", "name": "Valid, decision, event, observation and knowledge time", "description": "Separate time axes and intervals for relationship effect, decisions, events, observations and when assertions became known.", "source_refs": [ "SRC-002", "SRC-003", "SRC-009" ], "questions": [ { "id": "valid-decision-event-observation-and-knowledge-time-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for valid, decision, event, observation and knowledge time?", "kind": "temporal", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "valid-decision-event-observation-and-knowledge-time-q02", "text": "Which member, organization, authority, source and evidence establishes valid, decision, event, observation and knowledge time, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "valid-decision-event-observation-and-knowledge-time-q03", "text": "How may valid, decision, event, observation and knowledge time be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "valid-decision-event-observation-and-knowledge-time-data", "name": "Valid, decision, event, observation and knowledge time data", "description": "Structured, source-qualified answer data for valid, decision, event, observation and knowledge time.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-009" ] } ], "artifacts": [ { "id": "valid-decision-event-observation-and-knowledge-time-record", "name": "Valid, decision, event, observation and knowledge time record", "description": "Versioned evidence-bearing record for valid, decision, event, observation and knowledge time with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus valid-decision-event-observation-and-knowledge-time assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-002", "SRC-003", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "renewal-suspension-and-reinstatement", "name": "Renewal, suspension and reinstatement", "description": "Non-terminal changes and their effect on role, right and duty bindings.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "renewal-extension-revalidation-and-lapse", "name": "Renewal, extension, revalidation and lapse", "description": "Renewal basis, decision, changed conditions, new validity, grace period and lapse effect with predecessor lineage.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ], "questions": [ { "id": "renewal-extension-revalidation-and-lapse-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for renewal, extension, revalidation and lapse?", "kind": "lifecycle", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "renewal-extension-revalidation-and-lapse-q02", "text": "Which member, organization, authority, source and evidence establishes renewal, extension, revalidation and lapse, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "renewal-extension-revalidation-and-lapse-q03", "text": "How may renewal, extension, revalidation and lapse be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "renewal-extension-revalidation-and-lapse-data", "name": "Renewal, extension, revalidation and lapse data", "description": "Structured, source-qualified answer data for renewal, extension, revalidation and lapse.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "renewal-extension-revalidation-and-lapse-record", "name": "Renewal, extension, revalidation and lapse record", "description": "Versioned evidence-bearing record for renewal, extension, revalidation and lapse with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus renewal-extension-revalidation-and-lapse assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "suspension-restriction-reinstatement-and-restored-standing", "name": "Suspension, restriction, reinstatement and restored standing", "description": "Authority, reason, due process, affected rights and duties, review date, remedy and reinstatement effect.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "suspension-restriction-reinstatement-and-restored-standing-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for suspension, restriction, reinstatement and restored standing?", "kind": "process", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "suspension-restriction-reinstatement-and-restored-standing-q02", "text": "Which member, organization, authority, source and evidence establishes suspension, restriction, reinstatement and restored standing, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "suspension-restriction-reinstatement-and-restored-standing-q03", "text": "How may suspension, restriction, reinstatement and restored standing be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "suspension-restriction-reinstatement-and-restored-standing-data", "name": "Suspension, restriction, reinstatement and restored standing data", "description": "Structured, source-qualified answer data for suspension, restriction, reinstatement and restored standing.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "suspension-restriction-reinstatement-and-restored-standing-record", "name": "Suspension, restriction, reinstatement and restored standing record", "description": "Versioned evidence-bearing record for suspension, restriction, reinstatement and restored standing with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus suspension-restriction-reinstatement-and-restored-standing assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "resignation-termination-and-revocation", "name": "Resignation, termination and revocation", "description": "Terminal or successor events, reasons, challenge and surviving history.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "resignation-expiry-termination-removal-and-revocation-basis", "name": "Resignation, expiry, termination, removal and revocation basis", "description": "Initiating actor, basis, authority, notice, effective time, stated reason and distinction among voluntary, automatic and adverse endings.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "resignation-expiry-termination-removal-and-revocation-basis-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for resignation, expiry, termination, removal and revocation basis?", "kind": "lifecycle", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "resignation-expiry-termination-removal-and-revocation-basis-q02", "text": "Which member, organization, authority, source and evidence establishes resignation, expiry, termination, removal and revocation basis, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "resignation-expiry-termination-removal-and-revocation-basis-q03", "text": "How may resignation, expiry, termination, removal and revocation basis be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "resignation-expiry-termination-removal-and-revocation-basis-data", "name": "Resignation, expiry, termination, removal and revocation basis data", "description": "Structured, source-qualified answer data for resignation, expiry, termination, removal and revocation basis.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "resignation-expiry-termination-removal-and-revocation-basis-record", "name": "Resignation, expiry, termination, removal and revocation basis record", "description": "Versioned evidence-bearing record for resignation, expiry, termination, removal and revocation basis with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus resignation-expiry-termination-removal-and-revocation-basis assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "challenge-appeal-remedy-successor-and-tombstone", "name": "Challenge, appeal, remedy, successor and tombstone", "description": "Contest status, review authority, decision and remedy, reinstatement or successor identity and durable minimum tombstone.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "challenge-appeal-remedy-successor-and-tombstone-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for challenge, appeal, remedy, successor and tombstone?", "kind": "decision", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "challenge-appeal-remedy-successor-and-tombstone-q02", "text": "Which member, organization, authority, source and evidence establishes challenge, appeal, remedy, successor and tombstone, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "challenge-appeal-remedy-successor-and-tombstone-q03", "text": "How may challenge, appeal, remedy, successor and tombstone be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "challenge-appeal-remedy-successor-and-tombstone-data", "name": "Challenge, appeal, remedy, successor and tombstone data", "description": "Structured, source-qualified answer data for challenge, appeal, remedy, successor and tombstone.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "challenge-appeal-remedy-successor-and-tombstone-record", "name": "Challenge, appeal, remedy, successor and tombstone record", "description": "Versioned evidence-bearing record for challenge, appeal, remedy, successor and tombstone with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus challenge-appeal-remedy-successor-and-tombstone assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "terms-duties-fees-and-benefits", "name": "Terms, duties, fees and benefits", "description": "Links governed terms and economic or non-economic consequences without importing policy, payment or entitlement execution.", "rationale": "Membership may create referenced obligations, fees and benefits, but the relationship is not itself a policy engine, subscription, account or access grant.", "source_refs": [ "SRC-004", "SRC-006" ], "layers": [ { "id": "terms-rights-duties-and-constraints", "name": "Terms, rights, duties and constraints", "description": "Versioned rule and policy bindings that qualify membership.", "source_refs": [ "SRC-004", "SRC-006" ], "findings": [ { "id": "term-version-precedence-acceptance-and-amendment", "name": "Term version, precedence, acceptance and amendment", "description": "Applicable term sources, version, precedence, party notice or acceptance, effective time and immutable amendment lineage.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "term-version-precedence-acceptance-and-amendment-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for term version, precedence, acceptance and amendment?", "kind": "constraint", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "term-version-precedence-acceptance-and-amendment-q02", "text": "Which member, organization, authority, source and evidence establishes term version, precedence, acceptance and amendment, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "term-version-precedence-acceptance-and-amendment-q03", "text": "How may term version, precedence, acceptance and amendment be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "term-version-precedence-acceptance-and-amendment-data", "name": "Term version, precedence, acceptance and amendment data", "description": "Structured, source-qualified answer data for term version, precedence, acceptance and amendment.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "term-version-precedence-acceptance-and-amendment-record", "name": "Term version, precedence, acceptance and amendment record", "description": "Versioned evidence-bearing record for term version, precedence, acceptance and amendment with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus term-version-precedence-acceptance-and-amendment assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "permission-prohibition-duty-and-compliance-reference", "name": "Permission, prohibition, duty and compliance reference", "description": "ODRL or profile-specific policy links with assigner, assignee, target, action, constraint and external evaluation evidence.", "source_refs": [ "SRC-004" ], "questions": [ { "id": "permission-prohibition-duty-and-compliance-reference-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for permission, prohibition, duty and compliance reference?", "kind": "relationship", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "permission-prohibition-duty-and-compliance-reference-q02", "text": "Which member, organization, authority, source and evidence establishes permission, prohibition, duty and compliance reference, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "permission-prohibition-duty-and-compliance-reference-q03", "text": "How may permission, prohibition, duty and compliance reference be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "permission-prohibition-duty-and-compliance-reference-data", "name": "Permission, prohibition, duty and compliance reference data", "description": "Structured, source-qualified answer data for permission, prohibition, duty and compliance reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] } ], "artifacts": [ { "id": "permission-prohibition-duty-and-compliance-reference-record", "name": "Permission, prohibition, duty and compliance reference record", "description": "Versioned evidence-bearing record for permission, prohibition, duty and compliance reference with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus permission-prohibition-duty-and-compliance-reference assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "fee-benefit-and-entitlement-references", "name": "Fee, benefit and entitlement references", "description": "Economic and service consequences and their independent records.", "source_refs": [ "SRC-004" ], "findings": [ { "id": "fee-assessment-invoice-payment-waiver-and-arrears-reference", "name": "Fee assessment, invoice, payment, waiver and arrears reference", "description": "Links externally mastered fee and payment records and states why they do or do not affect membership standing.", "source_refs": [ "SRC-004" ], "questions": [ { "id": "fee-assessment-invoice-payment-waiver-and-arrears-reference-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for fee assessment, invoice, payment, waiver and arrears reference?", "kind": "relationship", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "fee-assessment-invoice-payment-waiver-and-arrears-reference-q02", "text": "Which member, organization, authority, source and evidence establishes fee assessment, invoice, payment, waiver and arrears reference, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "fee-assessment-invoice-payment-waiver-and-arrears-reference-q03", "text": "How may fee assessment, invoice, payment, waiver and arrears reference be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "fee-assessment-invoice-payment-waiver-and-arrears-reference-data", "name": "Fee assessment, invoice, payment, waiver and arrears reference data", "description": "Structured, source-qualified answer data for fee assessment, invoice, payment, waiver and arrears reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] } ], "artifacts": [ { "id": "fee-assessment-invoice-payment-waiver-and-arrears-reference-record", "name": "Fee assessment, invoice, payment, waiver and arrears reference record", "description": "Versioned evidence-bearing record for fee assessment, invoice, payment, waiver and arrears reference with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus fee-assessment-invoice-payment-waiver-and-arrears-reference assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "benefit-service-resource-and-access-entitlement-reference", "name": "Benefit, service, resource and access-entitlement reference", "description": "Links externally mastered benefits and grants with scope, validity and governing term without treating access as membership proof.", "source_refs": [ "SRC-004" ], "questions": [ { "id": "benefit-service-resource-and-access-entitlement-reference-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for benefit, service, resource and access-entitlement reference?", "kind": "relationship", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "benefit-service-resource-and-access-entitlement-reference-q02", "text": "Which member, organization, authority, source and evidence establishes benefit, service, resource and access-entitlement reference, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "benefit-service-resource-and-access-entitlement-reference-q03", "text": "How may benefit, service, resource and access-entitlement reference be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "benefit-service-resource-and-access-entitlement-reference-data", "name": "Benefit, service, resource and access-entitlement reference data", "description": "Structured, source-qualified answer data for benefit, service, resource and access-entitlement reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] } ], "artifacts": [ { "id": "benefit-service-resource-and-access-entitlement-reference-record", "name": "Benefit, service, resource and access-entitlement reference record", "description": "Versioned evidence-bearing record for benefit, service, resource and access-entitlement reference with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus benefit-service-resource-and-access-entitlement-reference assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "evidence-privacy-dispute-and-trust", "name": "Evidence, privacy, dispute and trust", "description": "Maintains assertions, attestations, conflicts and privacy-safe projections.", "rationale": "Membership may be private or contested; identifiers, status services and aggregate counts can leak its existence even when payload fields are hidden.", "source_refs": [ "SRC-003", "SRC-005", "SRC-008" ], "layers": [ { "id": "assertions-evidence-and-quality", "name": "Assertions, evidence and quality", "description": "Attributable source statements, observations and reconciliation.", "source_refs": [ "SRC-003", "SRC-005" ], "findings": [ { "id": "member-organization-sponsor-issuer-and-authority-assertions", "name": "Member, organization, sponsor, issuer and authority assertions", "description": "Parallel statements with actor, role, basis, valid and knowledge time, confidence, acknowledgement and contest status.", "source_refs": [ "SRC-003", "SRC-005" ], "questions": [ { "id": "member-organization-sponsor-issuer-and-authority-assertions-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for member, organization, sponsor, issuer and authority assertions?", "kind": "provenance", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "member-organization-sponsor-issuer-and-authority-assertions-q02", "text": "Which member, organization, authority, source and evidence establishes member, organization, sponsor, issuer and authority assertions, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "member-organization-sponsor-issuer-and-authority-assertions-q03", "text": "How may member, organization, sponsor, issuer and authority assertions be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "member-organization-sponsor-issuer-and-authority-assertions-data", "name": "Member, organization, sponsor, issuer and authority assertions data", "description": "Structured, source-qualified answer data for member, organization, sponsor, issuer and authority assertions.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "member-organization-sponsor-issuer-and-authority-assertions-record", "name": "Member, organization, sponsor, issuer and authority assertions record", "description": "Versioned evidence-bearing record for member, organization, sponsor, issuer and authority assertions with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus member-organization-sponsor-issuer-and-authority-assertions assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null }, { "id": "evidence-attestation-freshness-quality-and-reconciliation", "name": "Evidence, attestation, freshness, quality and reconciliation", "description": "Source records, method, issuer, digest, status observation, freshness, conflict and explicit reconciliation result.", "source_refs": [ "SRC-003", "SRC-005" ], "questions": [ { "id": "evidence-attestation-freshness-quality-and-reconciliation-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for evidence, attestation, freshness, quality and reconciliation?", "kind": "quality", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "evidence-attestation-freshness-quality-and-reconciliation-q02", "text": "Which member, organization, authority, source and evidence establishes evidence, attestation, freshness, quality and reconciliation, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "evidence-attestation-freshness-quality-and-reconciliation-q03", "text": "How may evidence, attestation, freshness, quality and reconciliation be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "evidence-attestation-freshness-quality-and-reconciliation-data", "name": "Evidence, attestation, freshness, quality and reconciliation data", "description": "Structured, source-qualified answer data for evidence, attestation, freshness, quality and reconciliation.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "evidence-attestation-freshness-quality-and-reconciliation-record", "name": "Evidence, attestation, freshness, quality and reconciliation record", "description": "Versioned evidence-bearing record for evidence, attestation, freshness, quality and reconciliation with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus evidence-attestation-freshness-quality-and-reconciliation assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "credential-directory-and-proof-projections", "name": "Credential, directory and proof projections", "description": "Portable and discoverable representations that remain separate from the source relationship.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "findings": [ { "id": "verifiable-membership-credential-and-status-reference", "name": "Verifiable membership credential and status reference", "description": "Issuer, subject, schema, validity, evidence, status and terms-of-use references plus privacy and correlation profile.", "source_refs": [ "SRC-005", "SRC-008" ], "questions": [ { "id": "verifiable-membership-credential-and-status-reference-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for verifiable membership credential and status reference?", "kind": "evidence", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "verifiable-membership-credential-and-status-reference-q02", "text": "Which member, organization, authority, source and evidence establishes verifiable membership credential and status reference, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "verifiable-membership-credential-and-status-reference-q03", "text": "How may verifiable membership credential and status reference be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "verifiable-membership-credential-and-status-reference-data", "name": "Verifiable membership credential and status reference data", "description": "Structured, source-qualified answer data for verifiable membership credential and status reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "verifiable-membership-credential-and-status-reference-record", "name": "Verifiable membership credential and status reference record", "description": "Versioned evidence-bearing record for verifiable membership credential and status reference with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus verifiable-membership-credential-and-status-reference assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "directory-listing-badge-roster-and-minimal-verification", "name": "Directory listing, badge, roster and minimal verification", "description": "Purpose-specific projections, exposed fields, audience, freshness, revocation behavior and non-authoritative status.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "questions": [ { "id": "directory-listing-badge-roster-and-minimal-verification-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for directory listing, badge, roster and minimal verification?", "kind": "access", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "directory-listing-badge-roster-and-minimal-verification-q02", "text": "Which member, organization, authority, source and evidence establishes directory listing, badge, roster and minimal verification, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "directory-listing-badge-roster-and-minimal-verification-q03", "text": "How may directory listing, badge, roster and minimal verification be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "directory-listing-badge-roster-and-minimal-verification-data", "name": "Directory listing, badge, roster and minimal verification data", "description": "Structured, source-qualified answer data for directory listing, badge, roster and minimal verification.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "directory-listing-badge-roster-and-minimal-verification-record", "name": "Directory listing, badge, roster and minimal verification record", "description": "Versioned evidence-bearing record for directory listing, badge, roster and minimal verification with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus directory-listing-badge-roster-and-minimal-verification assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "privacy-access-correction-and-retention", "name": "Privacy, access, correction and retention", "description": "Field-sensitive disclosure and durable lawful history.", "source_refs": [ "SRC-003", "SRC-008" ], "findings": [ { "id": "existence-role-date-standing-and-evidence-disclosure", "name": "Existence, role, date, standing and evidence disclosure", "description": "Separately classifies the sensitivity, purpose, audience and masking rules for each fact and inference surface.", "source_refs": [ "SRC-005", "SRC-008" ], "questions": [ { "id": "existence-role-date-standing-and-evidence-disclosure-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for existence, role, date, standing and evidence disclosure?", "kind": "privacy", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "existence-role-date-standing-and-evidence-disclosure-q02", "text": "Which member, organization, authority, source and evidence establishes existence, role, date, standing and evidence disclosure, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "existence-role-date-standing-and-evidence-disclosure-q03", "text": "How may existence, role, date, standing and evidence disclosure be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "existence-role-date-standing-and-evidence-disclosure-data", "name": "Existence, role, date, standing and evidence disclosure data", "description": "Structured, source-qualified answer data for existence, role, date, standing and evidence disclosure.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "existence-role-date-standing-and-evidence-disclosure-record", "name": "Existence, role, date, standing and evidence disclosure record", "description": "Versioned evidence-bearing record for existence, role, date, standing and evidence disclosure with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus existence-role-date-standing-and-evidence-disclosure assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "access-correction-restriction-retention-legal-hold-and-deletion", "name": "Access, correction, restriction, retention, legal hold and deletion", "description": "Member and organization rights, steward duties, disputed fields, per-artifact retention and tombstone behavior.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "access-correction-restriction-retention-legal-hold-and-deletion-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for access, correction, restriction, retention, legal hold and deletion?", "kind": "retention", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "access-correction-restriction-retention-legal-hold-and-deletion-q02", "text": "Which member, organization, authority, source and evidence establishes access, correction, restriction, retention, legal hold and deletion, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "access-correction-restriction-retention-legal-hold-and-deletion-q03", "text": "How may access, correction, restriction, retention, legal hold and deletion be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "access-correction-restriction-retention-legal-hold-and-deletion-data", "name": "Access, correction, restriction, retention, legal hold and deletion data", "description": "Structured, source-qualified answer data for access, correction, restriction, retention, legal hold and deletion.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "access-correction-restriction-retention-legal-hold-and-deletion-record", "name": "Access, correction, restriction, retention, legal hold and deletion record", "description": "Versioned evidence-bearing record for access, correction, restriction, retention, legal hold and deletion with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus access-correction-restriction-retention-legal-hold-and-deletion assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "interoperability-governance-and-agent-operations", "name": "Interoperability, governance and agent operations", "description": "Controls classifications, mappings, validation and safe automated action.", "rationale": "Exchange must preserve qualified relation identity, roles, time, authority, disagreement and privacy rather than reducing membership to a boolean edge.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-009" ], "layers": [ { "id": "classification-and-profile-projections", "name": "Classification and profile projections", "description": "Versioned type, role, state and reason vocabularies and mappings.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "findings": [ { "id": "membership-role-standing-and-reason-concept-schemes", "name": "Membership, role, standing and reason concept schemes", "description": "Pinned concept identifiers, labels, scope notes, hierarchy, authority, version and mapping confidence.", "source_refs": [ "SRC-007" ], "questions": [ { "id": "membership-role-standing-and-reason-concept-schemes-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for membership, role, standing and reason concept schemes?", "kind": "classification", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "membership-role-standing-and-reason-concept-schemes-q02", "text": "Which member, organization, authority, source and evidence establishes membership, role, standing and reason concept schemes, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "membership-role-standing-and-reason-concept-schemes-q03", "text": "How may membership, role, standing and reason concept schemes be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "membership-role-standing-and-reason-concept-schemes-data", "name": "Membership, role, standing and reason concept schemes data", "description": "Structured, source-qualified answer data for membership, role, standing and reason concept schemes.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-007" ] } ], "artifacts": [ { "id": "membership-role-standing-and-reason-concept-schemes-record", "name": "Membership, role, standing and reason concept schemes record", "description": "Versioned evidence-bearing record for membership, role, standing and reason concept schemes with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus membership-role-standing-and-reason-concept-schemes assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "w3c-org-credential-policy-and-domain-profile-mappings", "name": "W3C ORG, credential, policy and domain-profile mappings", "description": "Source and target versions, mapping scope, transformed or omitted data, validation and non-round-trip declarations.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "questions": [ { "id": "w3c-org-credential-policy-and-domain-profile-mappings-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for w3c org, credential, policy and domain-profile mappings?", "kind": "interoperability", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "w3c-org-credential-policy-and-domain-profile-mappings-q02", "text": "Which member, organization, authority, source and evidence establishes w3c org, credential, policy and domain-profile mappings, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "w3c-org-credential-policy-and-domain-profile-mappings-q03", "text": "How may w3c org, credential, policy and domain-profile mappings be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "w3c-org-credential-policy-and-domain-profile-mappings-data", "name": "W3C ORG, credential, policy and domain-profile mappings data", "description": "Structured, source-qualified answer data for w3c org, credential, policy and domain-profile mappings.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "w3c-org-credential-policy-and-domain-profile-mappings-record", "name": "W3C ORG, credential, policy and domain-profile mappings record", "description": "Versioned evidence-bearing record for w3c org, credential, policy and domain-profile mappings with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus w3c-org-credential-policy-and-domain-profile-mappings assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "agent-control-and-safe-operation", "name": "Agent control and safe operation", "description": "Authorized operations, invariants, rollback and audit.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-009" ], "findings": [ { "id": "agent-operation-authority-purpose-and-confirmation-class", "name": "Agent operation authority, purpose and confirmation class", "description": "Classifies read, create, admit, suspend, reinstate, terminate, disclose and delete operations as autonomous, propose, confirm or forbidden.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "questions": [ { "id": "agent-operation-authority-purpose-and-confirmation-class-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for agent operation authority, purpose and confirmation class?", "kind": "security", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "agent-operation-authority-purpose-and-confirmation-class-q02", "text": "Which member, organization, authority, source and evidence establishes agent operation authority, purpose and confirmation class, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "agent-operation-authority-purpose-and-confirmation-class-q03", "text": "How may agent operation authority, purpose and confirmation class be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "agent-operation-authority-purpose-and-confirmation-class-data", "name": "Agent operation authority, purpose and confirmation class data", "description": "Structured, source-qualified answer data for agent operation authority, purpose and confirmation class.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "agent-operation-authority-purpose-and-confirmation-class-record", "name": "Agent operation authority, purpose and confirmation class record", "description": "Versioned evidence-bearing record for agent operation authority, purpose and confirmation class with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus agent-operation-authority-purpose-and-confirmation-class assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "prewrite-postwrite-validation-conflict-and-recovery", "name": "Pre-write and post-write validation, conflict and recovery", "description": "Identity, party, authority, time, state-transition, policy, privacy, concurrency and rollback checks with immutable audit evidence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-009" ], "questions": [ { "id": "prewrite-postwrite-validation-conflict-and-recovery-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for pre-write and post-write validation, conflict and recovery?", "kind": "validation", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "prewrite-postwrite-validation-conflict-and-recovery-q02", "text": "Which member, organization, authority, source and evidence establishes pre-write and post-write validation, conflict and recovery, at what event, valid and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting actor", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "prewrite-postwrite-validation-conflict-and-recovery-q03", "text": "How may pre-write and post-write validation, conflict and recovery be validated, challenged, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge and correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "prewrite-postwrite-validation-conflict-and-recovery-data", "name": "Pre-write and post-write validation, conflict and recovery data", "description": "Structured, source-qualified answer data for pre-write and post-write validation, conflict and recovery.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-009" ] } ], "artifacts": [ { "id": "prewrite-postwrite-validation-conflict-and-recovery-record", "name": "Pre-write and post-write validation, conflict and recovery record", "description": "Versioned evidence-bearing record for pre-write and post-write validation, conflict and recovery with authority, event, valid and knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Membership identifier plus prewrite-postwrite-validation-conflict-and-recovery assertion or event identifier; mutable party names, dates, directory keys and file hashes never identify the relationship.", "source_refs": [ "SRC-002", "SRC-003", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "propose-membership", "name": "Propose membership", "description": "Create a proposed relationship with stable identity, parties, scheme, requested type and explicit unknowns.", "inputs": [ "member reference", "organization reference", "membership profile", "source" ], "outputs": [ "proposed membership revision" ], "preconditions": [ "actor has proposal authority", "duplicate check completed" ], "effects": [ "new relationship identity and provenance are recorded" ], "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "evaluate-eligibility", "name": "Evaluate eligibility", "description": "Record an attributable eligibility assessment and exceptions without importing the assessment process.", "inputs": [ "membership", "criteria version", "evidence", "evaluator" ], "outputs": [ "eligibility assertion" ], "preconditions": [ "criteria and authority are pinned" ], "effects": [ "result, uncertainty, expiry and evidence become queryable" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "record-admission-decision", "name": "Record admission decision", "description": "Append authorized admission or rejection with conditions, effect and appeal state.", "inputs": [ "membership", "decision reference", "authority" ], "outputs": [ "decision and lifecycle event" ], "preconditions": [ "party identities and governing basis validate" ], "effects": [ "relationship state changes at declared effective time without erasing proposal history" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-009" ] }, { "id": "bind-role", "name": "Bind role", "description": "Add, change or end a role binding with scope and validity while preserving membership identity.", "inputs": [ "membership", "role reference", "scope", "interval" ], "outputs": [ "role-binding revision" ], "preconditions": [ "profile permits the role and cardinality" ], "effects": [ "role history remains immutable and current projection is recomputed" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "bind-terms", "name": "Bind terms", "description": "Attach a versioned external term or policy with precedence and applicability.", "inputs": [ "membership", "term source", "scope and precedence" ], "outputs": [ "term binding revision" ], "preconditions": [ "term source resolves and authority is known" ], "effects": [ "permissions, prohibitions and duties remain externally evaluable" ], "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "renew-membership", "name": "Renew membership", "description": "Append renewal, extension or revalidation with changed conditions and a new interval.", "inputs": [ "membership", "renewal basis", "decision" ], "outputs": [ "renewal event" ], "preconditions": [ "current state and renewal authority permit change" ], "effects": [ "predecessor validity and changed terms remain citable" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "suspend-or-reinstate", "name": "Suspend or reinstate", "description": "Record temporary restriction or restored standing and its effect on roles, rights and duties.", "inputs": [ "membership", "authority", "reason", "effect map" ], "outputs": [ "suspension or reinstatement event" ], "preconditions": [ "due process and state transition validate" ], "effects": [ "affected bindings and review date are explicit" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "end-membership", "name": "End membership", "description": "Record resignation, expiry, termination, removal or revocation with basis, notice, challenge and successor.", "inputs": [ "membership", "ending basis", "authority or member act" ], "outputs": [ "ending event" ], "preconditions": [ "profile permits transition and actor has authority" ], "effects": [ "membership enters ended or contested state without cascading deletion" ], "source_refs": [ "SRC-003", "SRC-006" ] }, { "id": "reconcile-assertions", "name": "Reconcile assertions", "description": "Compare member, organization, issuer and authority assertions and append agreement, disagreement or unresolved state.", "inputs": [ "assertion set", "evidence", "reconciliation policy" ], "outputs": [ "reconciliation record" ], "preconditions": [ "sources and authority scopes are known" ], "effects": [ "no source is silently overwritten and conflict remains queryable" ], "source_refs": [ "SRC-003", "SRC-005" ] }, { "id": "issue-membership-attestation", "name": "Issue membership attestation", "description": "Create or link a portable proof without treating the credential as the source relationship.", "inputs": [ "membership revision", "issuer", "credential profile" ], "outputs": [ "digest-pinned attestation reference" ], "preconditions": [ "issuer authority, privacy and minimum disclosure validate" ], "effects": [ "credential status and source digest are linked and auditable" ], "source_refs": [ "SRC-005", "SRC-008" ] }, { "id": "issue-minimal-membership-view", "name": "Issue minimal membership view", "description": "Create a purpose-bound directory, roster or verification projection.", "inputs": [ "membership", "requester and purpose", "field policy" ], "outputs": [ "expiring projection" ], "preconditions": [ "authority and minimum-necessary fields validate" ], "effects": [ "existence, role, dates, standing and evidence are disclosed independently" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "project-membership-profile", "name": "Project membership profile", "description": "Transform a validated revision into W3C ORG, credential, policy or domain profile with declared loss.", "inputs": [ "membership revision", "target profile" ], "outputs": [ "validated exchange projection" ], "preconditions": [ "source and target versions are pinned" ], "effects": [ "mapping lineage, omissions and round-trip limits are recorded" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007" ] } ], "composition": [ { "target": "Agent, Organization, Group, Role, Post, Activity, Policy, Payment, Subscription, Credential, Access, Decision and Evidence models", "relation": "REFERENCE", "purpose": "Connect governed membership context while retaining external identity, authority and lifecycle.", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] }, { "target": "W3C Organization Ontology", "relation": "ALIGN", "purpose": "Project qualified member, organization, role and duration relationships while preserving the narrower Vercy boundary.", "required": true, "source_refs": [ "SRC-001" ] }, { "target": "OWL-Time and RFC 3339", "relation": "ALIGN", "purpose": "Represent intervals and relations and serialize event timestamps with seconds and explicit UTC offset.", "required": true, "source_refs": [ "SRC-002", "SRC-009" ] }, { "target": "ODRL Information Model 2.2", "relation": "ALIGN", "purpose": "Reference membership-related permissions, prohibitions, duties and constraints without importing policy evaluation.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "Verifiable Credentials Data Model 2.0", "relation": "ALIGN", "purpose": "Issue portable membership attestations that remain evidence projections with separate issuer, validity and status.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "LegalRuleML and SKOS", "relation": "ALIGN", "purpose": "Qualify authority, jurisdiction and rule metadata and version membership, role, standing and reason concepts.", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, membership registrar, member-rights steward and namespace", "Agent, organization, role, post, activity, policy, payment, credential, access, evidence and lifecycle-event registries", "Master-system mappings for member, organization, membership, role binding, decision and attestation identifiers", "Membership-scheme, eligibility, due-process, privacy, retention, federation and autonomous-agent policies" ], "namespace_guidance": "Mint membership and assertion identifiers in the adopting Dimension namespace only when no authoritative master identifier exists; preserve agents, organizations, roles, posts, activities, payments, credentials, access grants, policies, evidence and decisions as typed references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local membership, role-binding, standing, decision, attestation, access and provenance registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative membership identifier, issuer and governing scheme, never by member-organization pair, role, directory key, badge, credential, payment, date or hash alone.", "Keep membership, employment, office, participation, subscription, citizenship, licence, credential, payment and access-entitlement lifecycles distinct." ], "patch_rules": [ "Additive extensions declare target bundle, layer or finding, membership scheme and domain profile, source, authority, privacy, due-process and interoperability impact.", "Identity, party, role, standing or lifecycle-semantics changes require a successor version, bitemporal migration map, rollback path and continued resolution of prior records." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when membership identity, parties, role scope, validity, authority, disagreement, access and lifecycle meaning remain intact.", "W3C ORG, credential, policy, directory and domain projections pin source and target versions and disclose transformed, omitted, aggregated or non-round-trippable values." ] }, "artifact_rules": { "identity_priority": [ "Authoritative membership master-system identifier qualified by issuer and membership scheme.", "Governed globally resolvable membership IRI with explicit member and organization references.", "Adopting-Dimension UUID or ULID when no authoritative external identifier exists." ], "timestamp_rule": "Record event timestamps in RFC 3339 with seconds and an explicit UTC offset or Z; keep event, decision, effective, observation, knowledge, issuance and ingestion times distinct.", "serial_naming_rule": "Name serial artifacts as {membership-id}--{artifact-kind}--{assertion-or-event-id}; never use party names, a directory key, role, date, credential identifier, filename or hash alone as membership identity.", "integrity_rule": "Store digest, media type, byte length, issuer, source and profile versions, authority, valid and knowledge times, provenance, assurance, licence and access marking for every retained serial artifact." }, "policies": [ "The adopting Dimension declares who may propose, evaluate, admit, bind roles, renew, suspend, reinstate, end, attest, disclose, correct, retain and tombstone membership records.", "A direct memberOf edge, directory listing, badge, payment, credential or access grant is evidence or projection and never alone establishes a current qualified membership.", "Member and organization assertions remain separately attributable; organizational stewardship never grants unilateral authority to erase member-side evidence, lawful correction, appeal, portability or retention rights.", "Agents, organizations, roles, posts, activities, projects, policies, payments, subscriptions, credentials and access grants remain in their owning systems and are referenced.", "Automated agents may read, validate, reconcile and append low-risk observations within policy; admission, adverse restriction, revocation, wider disclosure and destructive retirement require accountable authority." ], "crud": { "read": [ "Resolve active Dimension, purpose, role, membership scheme, requested valid and knowledge time, evidence freshness and access scope; return the minimum permitted projection without leaking private membership existence." ], "create": [ "Create stable membership identity, member and organization references, governing scheme, source provenance and explicit unknowns before admission, role or term bindings." ], "update": [ "Append an assertion, event or successor revision with actor, authority, reason, RFC 3339 time, evidence and before-and-after validation; never overwrite a cited assertion, decision or event." ], "delete": [ "Apply charter, member-rights, legal-hold, dispute, credential-status and retention policy; prefer ended state or tombstone, preserve identity and history, and never cascade into referenced parties, roles, payments, policies or evidence." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, delegation, access, retention and federation rules." ] }, { "name": "Member or member-authorized steward", "responsibilities": [ "Attest member-side facts, exercise access and correction rights, acknowledge terms and preserve contested assertions." ] }, { "name": "Organization or group authority", "responsibilities": [ "Own membership scheme, admission and standing authority within charter or mandate." ] }, { "name": "Membership registrar", "responsibilities": [ "Maintain identifiers, party bindings, roles, validity, standing and lifecycle records without importing external masters." ] }, { "name": "Sponsor, nominator or approver", "responsibilities": [ "Provide attributable proposal, sponsorship or decision evidence within delegated scope." ] }, { "name": "Appeal or review authority", "responsibilities": [ "Review eligibility, suspension, removal, revocation and correction disputes independently where policy requires." ] }, { "name": "Privacy and access steward", "responsibilities": [ "Apply purpose limitation, existence privacy, minimum disclosure, correction, retention and security rules." ] }, { "name": "Independent auditor", "responsibilities": [ "Review authority, transitions, attestations, disclosures and provenance without rewriting source evidence." ] } ], "access": { "default_rule": "Deny mutation and disclosure of membership existence, role, standing, reason or evidence unless active Dimension, membership scheme, role, purpose and field policy grant it; expose the minimum necessary projection.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Statutory, judicial, safeguarding or emergency access must cite authority, be purpose-bound, attributable and reviewable, and must not erase original assertions, disputes, decisions or audit evidence." ], "audit_requirements": [ "Log actor, agent, role, purpose, membership and party identities, action, policy and scheme profile, RFC 3339 timestamp with offset, affected scope, requested and effective authority, evidence and outcome." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read the nearest Dimension-owner AGENTS.md, membership mastership, scheme, member-rights, privacy, correction, retention, appeal and federation policies.", "Read this model AGENTS.md, pinned spec.yaml and required agent, organization, role, post, policy, payment, credential, access, evidence and decision model instructions before mutation or disclosure." ] } }, "coverage": { "claim": "A source-grounded reviewable draft of one qualified Membership relationship across W3C organization, time, provenance, policy, credential and knowledge-organization standards, OASIS legal-rule metadata, an EU privacy profile and RFC 3339, without a claim of universal domain, jurisdiction, eligibility, due-process, directory or certified crosswalk completeness.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Stable membership identity, issuer, aliases, duplicates and successor lineage are explicit." }, { "dimension": "classification and definition", "status": "covered", "notes": "Qualified membership is separated from employment, office, participation, subscription, citizenship, licence and access." }, { "dimension": "direct relational properties", "status": "covered", "notes": "Member, organization, scheme, type, roles, scope, validity, standing and basis are first-class; physical properties are not applicable." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Admission, authority, evidence, standing observation, confusing neighboring relations, confidence and freshness are covered." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Propose, evaluate, admit, bind, renew, suspend, reinstate, end, reconcile, attest and project operations are governed." }, { "dimension": "composition", "status": "covered", "notes": "Roles, posts, activities, policies, payments, credentials and access grants remain external typed references." }, { "dimension": "lifecycle", "status": "covered", "notes": "Proposal, decision, admission, renewal, suspension, reinstatement, resignation, termination, revocation and tombstone preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Member, organization, sponsor, nominator, approver, issuer, authority, role and activity relations are typed and time-qualified." }, { "dimension": "temporal", "status": "covered", "notes": "Event, decision, valid, observation, knowledge, issuance and ingestion times remain distinct and use RFC 3339 for events." }, { "dimension": "spatial", "status": "covered", "notes": "Geographic or logical scope is referenced when the membership scheme or role requires it; organization location remains external." }, { "dimension": "provenance", "status": "covered", "notes": "Member, organization, sponsor, issuer and authority assertions, evidence, revision and reconciliation are attributable." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Bilateral provenance and power asymmetry are explicit while each referenced record retains its master system." }, { "dimension": "validation and quality", "status": "covered", "notes": "Duplicates, scheme scope, eligibility, state transitions, stale standing, conflicting assertions and projection loss are checked." }, { "dimension": "access and privacy", "status": "covered", "notes": "Private existence, field-level purpose, minimum disclosure, correction, restriction and audit are covered." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Per-artifact retention, legal hold, credential status, tombstone and non-cascading deletion preserve lawful evidence." }, { "dimension": "interoperability", "status": "covered", "notes": "W3C ORG, OWL-Time, ODRL, VC, LegalRuleML and SKOS projections are versioned and loss-aware." } ], "known_omissions": [ "Domain profiles for companies, cooperatives, associations, unions, professional bodies, standards organizations, clubs, communities, families, religious bodies, political parties and machine-agent groups require specialist review.", "Applications, nominations, decisions, roles, posts, activities, payments, subscriptions, credentials, access grants and policy evaluation remain in neighboring models.", "Certified W3C ORG, OWL-Time, ODRL, VC, LegalRuleML, directory and domain-schema crosswalks, conformance suites and privacy fixtures remain future work." ], "conflicts": [ "A broad org:memberOf assertion may include affiliation, while this model requires a qualified scheme, parties, basis and standing and therefore cannot treat every memberOf edge as canonical Membership.", "A role may be held through membership or through an independently existing post or office, and those routes cannot be inferred as equivalent.", "Credential, payment, subscription and access status can diverge from underlying membership standing and must retain separate authority and time." ], "regional_assumptions": [ "The GDPR provides an EU privacy profile and does not create universal global obligations.", "LegalRuleML supplies legal-rule metadata patterns and does not determine which charter, bylaw or authority is valid in a particular jurisdiction.", "W3C ORG intentionally uses broad membership semantics, so domain profiles must narrow admission, role, standing and lifecycle rules." ], "adversarial_checks": [ "Reject employment, citizenship, office, subscription, licence, participation or access relationships represented as Membership without an explicit membership scheme and boundary decision.", "Reject current-standing inference from memberOf, a directory listing, payment, badge, credential or access grant alone.", "Reject organization-only control over member evidence, correction, appeal, portability, privacy or lawful retention.", "Reject private-membership leakage through predictable identifiers, directory counts, event timing, search results or credential-status endpoints.", "Reject mutation, attestation, disclosure or revocation beyond actor authority, scheme scope, purpose, state preconditions and confirmation class." ] }, "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 as a qualified member-to-organization relationship", "rationale": "The model represents one governed belonging relationship under a named membership scheme. Employment, offices, participation, subscriptions, citizenship, licences, credentials, payments, access grants, parties, roles, posts, policies, decisions and evidence remain distinct linked objects or records." }, "decisions": [ { "concept": "Membership and employment", "disposition": "accepted as separate models", "rationale": "Membership represents governed belonging and standing under a scheme, while WM-ORG-005 represents a work relationship with labour-status, term and assignment semantics." }, { "concept": "Qualified relationship identity", "disposition": "accepted as independently governed", "rationale": "The same member and organization may have several memberships under different schemes, periods or types, so a member-organization pair, role, badge, directory key, credential or payment is not sufficient identity." }, { "concept": "W3C ORG alignment", "disposition": "accepted with a narrower canonical boundary", "rationale": "W3C ORG provides a qualified Membership pattern with member, organization, role and duration, but its broad memberOf relation can also represent affiliation and cannot by itself prove governed Vercy Membership." }, { "concept": "Member kinds", "disposition": "accepted as profile-constrained agents", "rationale": "W3C ORG permits agents including people and organizations; Vercy also allows governed software-agent references when a membership profile explicitly permits them and does not imply AI subjecthood." }, { "concept": "Membership role and post", "disposition": "accepted as distinct linked concepts", "rationale": "A role binding qualifies what the member does through membership, while an independently existing post or office can be vacant, reassigned or governed by another relationship." }, { "concept": "Admission and eligibility", "disposition": "accepted as attributable effects and references", "rationale": "Applications, nominations, assessments and decisions retain their own records, while Membership stores the governing basis, evidence links and exact admission or rejection effect." }, { "concept": "Validity and standing", "disposition": "accepted as bitemporal assertions", "rationale": "Relationship validity, decision time, event time, observation time and knowledge time may differ and must survive renewal, suspension, reinstatement and retroactive correction." }, { "concept": "Terms, fees and benefits", "disposition": "accepted as external bindings", "rationale": "Policies, permissions, duties, fees, payments, subscriptions, benefits and access grants retain independent identity, evaluation and lifecycle; none alone proves current membership." }, { "concept": "Credential and directory", "disposition": "accepted as proof or projection", "rationale": "A verifiable credential, badge, roster or directory entry has its own issuer, validity, status and privacy surface and may diverge from the authoritative relationship." }, { "concept": "Private membership", "disposition": "accepted with existence privacy", "rationale": "Identifiers, counts, timing, search results and credential-status endpoints can reveal membership even when the detailed payload is hidden, so existence itself is field-policy controlled." }, { "concept": "Bilateral provenance and dispute", "disposition": "accepted without unilateral truth ownership", "rationale": "Member, organization, sponsor, issuer and authority assertions remain separately attributable, and no steward may silently erase disagreement, correction or appeal evidence." }, { "concept": "Approved registry composition", "disposition": "held pending relation governance", "rationale": "The approved relation ledger contains no WM-ORG-006 rows, so all proposed links to agents, organizations, roles, policies, payments, credentials, access and evidence remain draft." } ], "publicationHolds": [ "Claude and Grok timed out during their bounded attempts, so independent external review is absent and explicitly waived for this published reviewable draft.", "The previous O3 card combined Employment and Membership, while the current registry requires separate WM-ORG-005 and WM-ORG-006 boundaries; this publication defines only Membership.", "The approved relationship ledger contains no WM-ORG-006 rows, so all proposed sibling composition remains draft.", "Company, cooperative, association, union, professional-body, standards-body, club, community, family, religious, political and machine-agent membership profiles require specialist review.", "Certified W3C ORG, OWL-Time, ODRL, Verifiable Credentials, LegalRuleML, SKOS, directory and domain-schema crosswalks, conformance fixtures and privacy tests remain unverified.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Develop domain profiles for voluntary, statutory, professional, corporate, cooperative, community, family, standards, political and machine-agent memberships.", "Approve model identifiers and relation cardinalities for agents, organizations, roles, posts, activities, policies, payments, subscriptions, credentials, access grants, decisions and evidence.", "Create deterministic fixtures for duplicate memberships, multiple schemes, concurrent roles, non-contiguous validity, suspension, reinstatement, appeal, private existence and stale credential status.", "Validate certified organization, policy, credential, legal-rule, directory and domain projections with explicit loss, correlation-risk and round-trip tests." ] }, "statistics": { "sources": 9, "bundles": 7, "layers": 16, "findings": 32, "questions": 96, "artifacts": 32, "functions": 12 } }