# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T07:17:43Z", "synthesisSha256": "681940150e225eb6b5855694d947265610d25d5be6283bee01d61c9653fd7dc8", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-038", "registryId": "vr.wm-act-038", "name": "Learning Activity / Course Delivery", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.EDU" ], "tags": [ "learning", "activity", "course", "delivery", "act.edu" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-038-learning-activity-course-delivery/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-038", "model": { "registry_id": "vr.wm-act-038", "model_id": "WM-ACT-038", "name": "Learning Activity / Course Delivery", "entry_kind": "aggregate", "purpose": "Represent one governed delivery aggregate for a bounded learning activity, course, class, cohort, self-paced offering, workshop or session, connecting immutable learning intent to actual instruction, participation evidence, assessment and bounded outcomes.", "scope_statement": "Owns delivery identity and lineage, mandatory delivery profile, exact course, activity, curriculum and objective bindings, delivery-scoped design, provider and role assignments, cohort and participation assertions, schedule, location and modality, resource and tool bindings, instruction, attendance and learning-event assertions, assessment administrations, progress and completion assertions, quality, lifecycle, interoperability, access and retention. Person, Learner, Organization, Programme, Course or Activity Definition, Competency, Academic Session, Location, Resource, Tool, Enrollment, Attendance, Assessment Definition, Submission, Assessment Result, Qualification, Credential, Dataset, Communication, Artifact and Audit masters remain external.", "in_scope": [ "Delivery identity, profile, lineage, provider, authority, curriculum, objectives, instructional design, roles, cohorts, enrollment bindings and access", "Schedule, sessions, modality, locations, resources, tools, assignments, instruction, facilitation, attendance, participation and learning-experience events", "Assessment administrations, result links, feedback, progress, mastery and completion assertions, quality, lifecycle, interoperability, privacy, retention and safe agents" ], "out_of_scope": [ "Independent person, learner, provider, programme, course or activity definition, competency, session, location, resource, tool, enrollment, attendance, assessment, submission, result, qualification, credential, communication, artifact or audit master lifecycles", "Inferring enrollment from access, attendance from login, learning from activity completion, mastery from one score, qualification from course completion or causality from learning analytics", "Implementing a student information system, learning management system, learning record store, assessment platform, content repository, credential wallet or universal education policy and legal regime" ], "boundary_notes": [ { "neighbor": "Course, Activity, Curriculum or Programme Definition", "distinction": "Reusable intent, structure, prerequisites and objectives are external versioned definitions. The delivery binds exact revisions and records one governed realization.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-011", "SRC-013" ] }, { "neighbor": "Person, Learner, Cohort or Enrollment", "distinction": "The delivery owns source-qualified participation and role assertions. External identity and enrollment masters retain admission authority, lifecycle and learner rights.", "source_refs": [ "SRC-003", "SRC-004", "SRC-009", "SRC-014" ] }, { "neighbor": "Session, Attendance or Learning Experience Event", "distinction": "These are planned or observed occurrences within the delivery. Source events keep their own actor, action, object, context, time, authority and voiding semantics.", "source_refs": [ "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-016" ] }, { "neighbor": "Assessment Definition, Submission, Result or Grade", "distinction": "The delivery binds assessment revisions and issues delivery-scoped administration and grading assertions while external evidence and result masters retain identity and review history.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ] }, { "neighbor": "Qualification, Credential or Learner Record", "distinction": "Completion or mastery can support a separately authorized achievement, credit, qualification or credential. The delivery cannot issue or own those records unless explicitly delegated by their master system.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-012" ] } ] }, "sources": [ { "id": "SRC-001", "title": "International Standard Classification of Education", "organization": "UNESCO Institute for Statistics", "url": "https://uis.unesco.org/sites/default/files/documents/international-standard-classification-of-education-isced-2011-en.pdf", "version_or_date": "ISCED 2011", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Defines education-programme and qualification classification boundaries, level, orientation, completion and attainment concepts for international statistics." }, { "id": "SRC-002", "title": "The European Learning Model", "organization": "European Commission", "url": "https://esco.ec.europa.eu/en/about-esco/escopedia/escopedia/european-learning-model", "version_or_date": "European Learning Model overview, current page accessed 6 September 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Describes a multilingual model for formal, non-formal and informal learning opportunities, qualifications, accreditation and credentials, with ESCO alignment." }, { "id": "SRC-003", "title": "Edu-API", "organization": "1EdTech Consortium", "url": "https://www.1edtech.org/standards/edu-api", "version_or_date": "Edu-API Candidate Final Public overview", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Defines the higher-education enterprise exchange scope for organizations, course catalogues, offerings, enrollments and outcomes while distinguishing source systems." }, { "id": "SRC-004", "title": "OneRoster 1.2 Standard", "organization": "1EdTech Consortium", "url": "https://standards.1edtech.org/oneroster/specifications/standards/v1p2", "version_or_date": "OneRoster 1.2 Final Release", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Defines K-12 exchange models for academic sessions, users, classes, courses, organizations, enrollments, resources, gradebook line items and results." }, { "id": "SRC-005", "title": "Caliper Analytics", "organization": "1EdTech Consortium", "url": "https://www.1edtech.org/standards/caliper", "version_or_date": "Caliper Analytics 1.2", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Defines learning-interaction and product-usage event profiles including assessment, assignable, grading, reading, media, forum, session, feedback and tool use." }, { "id": "SRC-006", "title": "Competencies and Academic Standards Exchange", "organization": "1EdTech Consortium", "url": "https://standards.1edtech.org/case/", "version_or_date": "CASE 1.1 Final", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Defines identifiers and exchange models for competency frameworks, learning outcomes, associations, rubrics, criteria and performance levels." }, { "id": "SRC-007", "title": "Question and Test Interoperability specification documents", "organization": "1EdTech Consortium", "url": "https://www.1edtech.org/standards/qti/index", "version_or_date": "QTI 3.0 Final Release, 11 May 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Defines exchange of assessment items, tests and results between authoring, item-bank, delivery, scoring and analytics systems." }, { "id": "SRC-008", "title": "Experience API Data", "organization": "Advanced Distributed Learning Initiative", "url": "https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Data.md", "version_or_date": "xAPI 2.0 current specification repository", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Defines immutable statements with actor, verb, object, result, context, timestamp, stored time, authority and attachments for learning experiences." }, { "id": "SRC-009", "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-06T07:03:00Z", "relevance": "Defines entities, activities, agents, plans, usage, generation, derivation, association, revision and invalidation for attributable learning records." }, { "id": "SRC-010", "title": "Web Content Accessibility Guidelines 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/WCAG22/", "version_or_date": "W3C Recommendation, 12 December 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Provides testable accessibility criteria for perceivable, operable, understandable and robust digital content and interfaces." }, { "id": "SRC-011", "title": "Common Cartridge", "organization": "1EdTech Consortium", "url": "https://www.1edtech.org/standards/cc", "version_or_date": "Common Cartridge and Thin Common Cartridge 1.4 Candidate Final overview", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Defines packaging, exchange and linking of digital learning materials, assessments, tools and standards-aligned resource metadata." }, { "id": "SRC-012", "title": "Comprehensive Learner Record Standard", "organization": "1EdTech Consortium", "url": "https://www.1edtech.org/standards/clr", "version_or_date": "CLR Standard 2.0 Final", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Defines learner-specific achievement assertions with issuer, learner, achievement and supporting evidence, plus bundles of learning and employment records." }, { "id": "SRC-013", "title": "CourseInstance", "organization": "Schema.org Community Group", "url": "https://schema.org/CourseInstance", "version_or_date": "Schema.org current vocabulary page accessed 6 September 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Distinguishes a course instance by time, location, mode, schedule, workload, instructor and learner section from the reusable Course definition." }, { "id": "SRC-014", "title": "NIST Privacy Framework", "organization": "National Institute of Standards and Technology", "url": "https://www.nist.gov/privacy-framework", "version_or_date": "Privacy Framework 1.0 with later evolution materials", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Provides a voluntary risk-based structure for identifying and managing privacy risk across data collection, analysis, sharing and retention." }, { "id": "SRC-015", "title": "Disposing of records", "organization": "The National Archives, United Kingdom", "url": "https://www.nationalarchives.gov.uk/information-management/manage-information/policy-process/disposal/", "version_or_date": "Official records-management guidance accessed 6 September 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:03:00Z", "relevance": "Grounds retention and disposition decisions in business, legal, accountability and historical requirements." }, { "id": "SRC-016", "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-06T07:03:00Z", "relevance": "Defines an interoperable timestamp profile with seconds and explicit UTC offset." } ], "structure": { "bundles": [ { "id": "delivery-identity-definition-and-design", "name": "Delivery identity, definition and design", "description": "Defines the delivery aggregate and binds it to reusable curriculum and learning intent.", "rationale": "A delivery profile, stable identity and exact definition revisions are required to keep one offering or bounded activity distinct from course catalogues, programmes and later deliveries.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-013" ], "layers": [ { "id": "delivery-profile-identity-and-lineage", "name": "Delivery profile, identity and lineage", "description": "Establishes aggregate kind, offering identity, aliases and repeat-delivery lineage.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-009", "SRC-013" ], "findings": [ { "id": "learning-delivery-profile-definition-and-neighbor-boundary", "name": "Learning delivery profile, definition and neighbor boundary", "description": "Mandatory profile for bounded learning activity, course or cohort delivery, self-paced offering, workshop or session, with distinctions from reusable definition, programme, learner record and experience event.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-013" ], "questions": [ { "id": "learning-delivery-profile-definition-and-neighbor-boundary-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish learning delivery profile, definition and neighbor boundary?", "kind": "classification", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "learning-delivery-profile-definition-and-neighbor-boundary-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support learning delivery profile, definition and neighbor boundary?", "kind": "provenance", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "learning-delivery-profile-definition-and-neighbor-boundary-q03", "text": "How may learning delivery profile, definition and neighbor boundary be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "validation", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "learning-delivery-profile-definition-and-neighbor-boundary-data", "name": "Learning delivery profile, definition and neighbor boundary data", "description": "Structured learning-delivery data for learning delivery profile, definition and neighbor boundary with scope, provenance, time, confidence and access marking.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-013" ] } ], "artifacts": [ { "id": "learning-delivery-profile-definition-and-neighbor-boundary-record", "name": "Learning delivery profile, definition and neighbor boundary record", "description": "Versioned evidence-bearing learning-delivery record for learning delivery profile, definition and neighbor boundary with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus learning-delivery-profile-definition-and-neighbor-boundary assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "delivery-identifier-name-code-version-source-predecessor-repeat-and-lineage", "name": "Delivery identifier, name, code, version, source, predecessor, repeat and lineage", "description": "Authoritative and alternate identifiers, titles, local codes, profile and schema versions, source-system key, prior delivery, successor, correction and supersession lineage.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-009", "SRC-013" ], "questions": [ { "id": "delivery-identifier-name-code-version-source-predecessor-repeat-and-lineage-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish delivery identifier, name, code, version, source, predecessor, repeat and lineage?", "kind": "identity", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "delivery-identifier-name-code-version-source-predecessor-repeat-and-lineage-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support delivery identifier, name, code, version, source, predecessor, repeat and lineage?", "kind": "process", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "delivery-identifier-name-code-version-source-predecessor-repeat-and-lineage-q03", "text": "How may delivery identifier, name, code, version, source, predecessor, repeat and lineage be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "composition", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "delivery-identifier-name-code-version-source-predecessor-repeat-and-lineage-data", "name": "Delivery identifier, name, code, version, source, predecessor, repeat and lineage data", "description": "Structured learning-delivery data for delivery identifier, name, code, version, source, predecessor, repeat and lineage with scope, provenance, time, confidence and access marking.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-009", "SRC-013" ] } ], "artifacts": [ { "id": "delivery-identifier-name-code-version-source-predecessor-repeat-and-lineage-record", "name": "Delivery identifier, name, code, version, source, predecessor, repeat and lineage record", "description": "Versioned evidence-bearing learning-delivery record for delivery identifier, name, code, version, source, predecessor, repeat and lineage with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus delivery-identifier-name-code-version-source-predecessor-repeat-and-lineage assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-009", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "curriculum-objectives-and-instructional-design", "name": "Curriculum, objectives and instructional design", "description": "Pins what is intended to be taught, learned and experienced without copying curriculum masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-011", "SRC-013" ], "findings": [ { "id": "course-activity-programme-curriculum-definition-revision-and-scope-binding", "name": "Course, activity, programme and curriculum definition revision and scope binding", "description": "External definition and programme IDs, immutable revisions or digests, subject area, education level, language, intended audience, inclusion, exclusions and applicability.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-011", "SRC-013" ], "questions": [ { "id": "course-activity-programme-curriculum-definition-revision-and-scope-binding-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish course, activity, programme and curriculum definition revision and scope binding?", "kind": "composition", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "course-activity-programme-curriculum-definition-revision-and-scope-binding-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support course, activity, programme and curriculum definition revision and scope binding?", "kind": "validation", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "course-activity-programme-curriculum-definition-revision-and-scope-binding-q03", "text": "How may course, activity, programme and curriculum definition revision and scope binding be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "process", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "course-activity-programme-curriculum-definition-revision-and-scope-binding-data", "name": "Course, activity, programme and curriculum definition revision and scope binding data", "description": "Structured learning-delivery data for course, activity, programme and curriculum definition revision and scope binding with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-011", "SRC-013" ] } ], "artifacts": [ { "id": "course-activity-programme-curriculum-definition-revision-and-scope-binding-record", "name": "Course, activity, programme and curriculum definition revision and scope binding record", "description": "Versioned evidence-bearing learning-delivery record for course, activity, programme and curriculum definition revision and scope binding with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus course-activity-programme-curriculum-definition-revision-and-scope-binding assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-011", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "learning-objective-competency-prerequisite-pedagogy-sequence-workload-and-success-criteria", "name": "Learning objective, competency, prerequisite, pedagogy, sequence, workload and success criteria", "description": "Objective and competency references, prerequisites, instructional method, activity sequence, planned workload, completion rules, success criteria and allowed adaptations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-011", "SRC-013" ], "questions": [ { "id": "learning-objective-competency-prerequisite-pedagogy-sequence-workload-and-success-criteria-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish learning objective, competency, prerequisite, pedagogy, sequence, workload and success criteria?", "kind": "requirement", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "learning-objective-competency-prerequisite-pedagogy-sequence-workload-and-success-criteria-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support learning objective, competency, prerequisite, pedagogy, sequence, workload and success criteria?", "kind": "exception", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "learning-objective-competency-prerequisite-pedagogy-sequence-workload-and-success-criteria-q03", "text": "How may learning objective, competency, prerequisite, pedagogy, sequence, workload and success criteria be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "interoperability", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "learning-objective-competency-prerequisite-pedagogy-sequence-workload-and-success-criteria-data", "name": "Learning objective, competency, prerequisite, pedagogy, sequence, workload and success criteria data", "description": "Structured learning-delivery data for learning objective, competency, prerequisite, pedagogy, sequence, workload and success criteria with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-011", "SRC-013" ] } ], "artifacts": [ { "id": "learning-objective-competency-prerequisite-pedagogy-sequence-workload-and-success-criteria-record", "name": "Learning objective, competency, prerequisite, pedagogy, sequence, workload and success criteria record", "description": "Versioned evidence-bearing learning-delivery record for learning objective, competency, prerequisite, pedagogy, sequence, workload and success criteria with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus learning-objective-competency-prerequisite-pedagogy-sequence-workload-and-success-criteria assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-011", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-actors-enrollment-and-access", "name": "Governance, actors, enrollment and access", "description": "Records the authorities, roles and delivery-scoped participation relationships needed to operate learning safely.", "rationale": "Provider authority, instructional responsibility, learner identity, enrollment, accessibility preferences, privacy consent and support decisions have separate owners and must retain source boundaries.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-009", "SRC-010", "SRC-014" ], "layers": [ { "id": "provider-instructor-and-support-roles", "name": "Provider, instructor and support roles", "description": "Binds accountable organizations, people and agents to delivery-scoped responsibilities.", "source_refs": [ "SRC-003", "SRC-004", "SRC-009", "SRC-013" ], "findings": [ { "id": "provider-organization-department-site-authority-owner-and-policy", "name": "Provider organization, department, site, authority, owner and policy", "description": "External provider and site identities, governing unit, delivery owner, legal or institutional basis, applicable academic, workplace or community policy and jurisdiction.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-009" ], "questions": [ { "id": "provider-organization-department-site-authority-owner-and-policy-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish provider organization, department, site, authority, owner and policy?", "kind": "authority", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "provider-organization-department-site-authority-owner-and-policy-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support provider organization, department, site, authority, owner and policy?", "kind": "classification", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "provider-organization-department-site-authority-owner-and-policy-q03", "text": "How may provider organization, department, site, authority, owner and policy be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "provenance", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "provider-organization-department-site-authority-owner-and-policy-data", "name": "Provider organization, department, site, authority, owner and policy data", "description": "Structured learning-delivery data for provider organization, department, site, authority, owner and policy with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-009" ] } ], "artifacts": [ { "id": "provider-organization-department-site-authority-owner-and-policy-record", "name": "Provider organization, department, site, authority, owner and policy record", "description": "Versioned evidence-bearing learning-delivery record for provider organization, department, site, authority, owner and policy with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus provider-organization-department-site-authority-owner-and-policy assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "instructor-facilitator-assessor-coordinator-mentor-support-agent-role-and-delegation", "name": "Instructor, facilitator, assessor, coordinator, mentor, support agent, role and delegation", "description": "External actor identities, delivery role, assignment period, delegated authority, qualifications or competence references, separation of duties, workload and substitution history.", "source_refs": [ "SRC-003", "SRC-004", "SRC-009", "SRC-013" ], "questions": [ { "id": "instructor-facilitator-assessor-coordinator-mentor-support-agent-role-and-delegation-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish instructor, facilitator, assessor, coordinator, mentor, support agent, role and delegation?", "kind": "ownership", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "instructor-facilitator-assessor-coordinator-mentor-support-agent-role-and-delegation-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support instructor, facilitator, assessor, coordinator, mentor, support agent, role and delegation?", "kind": "temporal", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "instructor-facilitator-assessor-coordinator-mentor-support-agent-role-and-delegation-q03", "text": "How may instructor, facilitator, assessor, coordinator, mentor, support agent, role and delegation be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "security", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "instructor-facilitator-assessor-coordinator-mentor-support-agent-role-and-delegation-data", "name": "Instructor, facilitator, assessor, coordinator, mentor, support agent, role and delegation data", "description": "Structured learning-delivery data for instructor, facilitator, assessor, coordinator, mentor, support agent, role and delegation with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009", "SRC-013" ] } ], "artifacts": [ { "id": "instructor-facilitator-assessor-coordinator-mentor-support-agent-role-and-delegation-record", "name": "Instructor, facilitator, assessor, coordinator, mentor, support agent, role and delegation record", "description": "Versioned evidence-bearing learning-delivery record for instructor, facilitator, assessor, coordinator, mentor, support agent, role and delegation with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus instructor-facilitator-assessor-coordinator-mentor-support-agent-role-and-delegation assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-009", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "learners-enrollment-eligibility-accommodation-and-privacy", "name": "Learners, enrollment, eligibility, accommodation and privacy", "description": "Represents delivery-scoped learner relationships and safeguards without copying person or learner masters.", "source_refs": [ "SRC-003", "SRC-004", "SRC-010", "SRC-014" ], "findings": [ { "id": "learner-cohort-enrollment-role-status-admission-capacity-waitlist-and-lineage", "name": "Learner, cohort, enrollment, role, status, admission, capacity, waitlist and lineage", "description": "External learner and cohort references, enrollment identity and role, request, admission or allocation authority, status, effective period, capacity, waitlist, transfer, withdrawal and source lineage.", "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ], "questions": [ { "id": "learner-cohort-enrollment-role-status-admission-capacity-waitlist-and-lineage-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish learner, cohort, enrollment, role, status, admission, capacity, waitlist and lineage?", "kind": "relationship", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "learner-cohort-enrollment-role-status-admission-capacity-waitlist-and-lineage-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support learner, cohort, enrollment, role, status, admission, capacity, waitlist and lineage?", "kind": "requirement", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "learner-cohort-enrollment-role-status-admission-capacity-waitlist-and-lineage-q03", "text": "How may learner, cohort, enrollment, role, status, admission, capacity, waitlist and lineage be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "state", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "learner-cohort-enrollment-role-status-admission-capacity-waitlist-and-lineage-data", "name": "Learner, cohort, enrollment, role, status, admission, capacity, waitlist and lineage data", "description": "Structured learning-delivery data for learner, cohort, enrollment, role, status, admission, capacity, waitlist and lineage with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] } ], "artifacts": [ { "id": "learner-cohort-enrollment-role-status-admission-capacity-waitlist-and-lineage-record", "name": "Learner, cohort, enrollment, role, status, admission, capacity, waitlist and lineage record", "description": "Versioned evidence-bearing learning-delivery record for learner, cohort, enrollment, role, status, admission, capacity, waitlist and lineage with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus learner-cohort-enrollment-role-status-admission-capacity-waitlist-and-lineage assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "eligibility-prerequisite-accessibility-accommodation-language-privacy-consent-and-exception", "name": "Eligibility, prerequisite, accessibility, accommodation, language, privacy, consent and exception", "description": "Eligibility and prerequisite checks, accessibility and language needs, approved accommodations, privacy notice or lawful basis, consent where required, minimum disclosure and exception authority.", "source_refs": [ "SRC-004", "SRC-010", "SRC-014" ], "questions": [ { "id": "eligibility-prerequisite-accessibility-accommodation-language-privacy-consent-and-exception-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish eligibility, prerequisite, accessibility, accommodation, language, privacy, consent and exception?", "kind": "access", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "eligibility-prerequisite-accessibility-accommodation-language-privacy-consent-and-exception-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support eligibility, prerequisite, accessibility, accommodation, language, privacy, consent and exception?", "kind": "evidence", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "eligibility-prerequisite-accessibility-accommodation-language-privacy-consent-and-exception-q03", "text": "How may eligibility, prerequisite, accessibility, accommodation, language, privacy, consent and exception be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "event", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "eligibility-prerequisite-accessibility-accommodation-language-privacy-consent-and-exception-data", "name": "Eligibility, prerequisite, accessibility, accommodation, language, privacy, consent and exception data", "description": "Structured learning-delivery data for eligibility, prerequisite, accessibility, accommodation, language, privacy, consent and exception with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-010", "SRC-014" ] } ], "artifacts": [ { "id": "eligibility-prerequisite-accessibility-accommodation-language-privacy-consent-and-exception-record", "name": "Eligibility, prerequisite, accessibility, accommodation, language, privacy, consent and exception record", "description": "Versioned evidence-bearing learning-delivery record for eligibility, prerequisite, accessibility, accommodation, language, privacy, consent and exception with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus eligibility-prerequisite-accessibility-accommodation-language-privacy-consent-and-exception assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-004", "SRC-010", "SRC-014" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "schedule-environment-resources-and-tools", "name": "Schedule, environment, resources and tools", "description": "Defines when and where delivery occurs and which content, platforms and resources are used.", "rationale": "Planned schedules and resources are distinct from actual session occurrences, learner access and observed use; the delivery binds versions but does not own external locations, content or tools.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-010", "SRC-011", "SRC-013", "SRC-016" ], "layers": [ { "id": "academic-session-calendar-meetings-location-and-modality", "name": "Academic session, calendar, meetings, location and modality", "description": "Pins time frames, scheduled occurrences and physical or virtual delivery settings.", "source_refs": [ "SRC-003", "SRC-004", "SRC-013", "SRC-016" ], "findings": [ { "id": "term-academic-session-start-end-timezone-recurrence-deadline-and-calendar", "name": "Term, academic session, start, end, time zone, recurrence, deadline and calendar", "description": "External academic-session reference, delivery window, event schedule, recurrence, breaks, milestones, due dates, time zone and source precision.", "source_refs": [ "SRC-003", "SRC-004", "SRC-013", "SRC-016" ], "questions": [ { "id": "term-academic-session-start-end-timezone-recurrence-deadline-and-calendar-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish term, academic session, start, end, time zone, recurrence, deadline and calendar?", "kind": "temporal", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "term-academic-session-start-end-timezone-recurrence-deadline-and-calendar-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support term, academic session, start, end, time zone, recurrence, deadline and calendar?", "kind": "retention", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "term-academic-session-start-end-timezone-recurrence-deadline-and-calendar-q03", "text": "How may term, academic session, start, end, time zone, recurrence, deadline and calendar be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "decision", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "term-academic-session-start-end-timezone-recurrence-deadline-and-calendar-data", "name": "Term, academic session, start, end, time zone, recurrence, deadline and calendar data", "description": "Structured learning-delivery data for term, academic session, start, end, time zone, recurrence, deadline and calendar with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-013", "SRC-016" ] } ], "artifacts": [ { "id": "term-academic-session-start-end-timezone-recurrence-deadline-and-calendar-record", "name": "Term, academic session, start, end, time zone, recurrence, deadline and calendar record", "description": "Versioned evidence-bearing learning-delivery record for term, academic session, start, end, time zone, recurrence, deadline and calendar with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus term-academic-session-start-end-timezone-recurrence-deadline-and-calendar assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-013", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "session-meeting-location-room-virtual-context-modality-attendance-window-and-capacity", "name": "Session, meeting, location, room, virtual context, modality, attendance window and capacity", "description": "Planned and actual meeting identity, physical or virtual location, online, onsite or blended mode, synchronous status, access window, capacity, cancellation and change evidence.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-013", "SRC-016" ], "questions": [ { "id": "session-meeting-location-room-virtual-context-modality-attendance-window-and-capacity-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish session, meeting, location, room, virtual context, modality, attendance window and capacity?", "kind": "spatial", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "session-meeting-location-room-virtual-context-modality-attendance-window-and-capacity-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support session, meeting, location, room, virtual context, modality, attendance window and capacity?", "kind": "definition", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "session-meeting-location-room-virtual-context-modality-attendance-window-and-capacity-q03", "text": "How may session, meeting, location, room, virtual context, modality, attendance window and capacity be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "ownership", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "session-meeting-location-room-virtual-context-modality-attendance-window-and-capacity-data", "name": "Session, meeting, location, room, virtual context, modality, attendance window and capacity data", "description": "Structured learning-delivery data for session, meeting, location, room, virtual context, modality, attendance window and capacity with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-013", "SRC-016" ] } ], "artifacts": [ { "id": "session-meeting-location-room-virtual-context-modality-attendance-window-and-capacity-record", "name": "Session, meeting, location, room, virtual context, modality, attendance window and capacity record", "description": "Versioned evidence-bearing learning-delivery record for session, meeting, location, room, virtual context, modality, attendance window and capacity with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus session-meeting-location-room-virtual-context-modality-attendance-window-and-capacity assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-013", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "content-resources-tools-and-assignments", "name": "Content, resources, tools and assignments", "description": "Binds exact learning materials and activity definitions to the delivery plan.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011" ], "findings": [ { "id": "learning-resource-content-package-media-document-tool-platform-version-and-access", "name": "Learning resource, content package, media, document, tool, platform, version and access", "description": "External resource and tool IDs, package or link, revision and digest, media type, rights, availability, platform context, accessibility metadata, localization and access conditions.", "source_refs": [ "SRC-005", "SRC-010", "SRC-011" ], "questions": [ { "id": "learning-resource-content-package-media-document-tool-platform-version-and-access-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish learning resource, content package, media, document, tool, platform, version and access?", "kind": "interoperability", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "learning-resource-content-package-media-document-tool-platform-version-and-access-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support learning resource, content package, media, document, tool, platform, version and access?", "kind": "state", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "learning-resource-content-package-media-document-tool-platform-version-and-access-q03", "text": "How may learning resource, content package, media, document, tool, platform, version and access be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "privacy", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "learning-resource-content-package-media-document-tool-platform-version-and-access-data", "name": "Learning resource, content package, media, document, tool, platform, version and access data", "description": "Structured learning-delivery data for learning resource, content package, media, document, tool, platform, version and access with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "learning-resource-content-package-media-document-tool-platform-version-and-access-record", "name": "Learning resource, content package, media, document, tool, platform, version and access record", "description": "Versioned evidence-bearing learning-delivery record for learning resource, content package, media, document, tool, platform, version and access with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus learning-resource-content-package-media-document-tool-platform-version-and-access assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-005", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "activity-assignment-instruction-sequence-dependency-due-rule-grouping-and-availability", "name": "Activity, assignment, instruction, sequence, dependency, due rule, grouping and availability", "description": "External activity or assignment definition, delivery-specific instructions, prerequisite and sequence graph, individual or group mode, availability window, due rule, submission channel and allowed variation.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011" ], "questions": [ { "id": "activity-assignment-instruction-sequence-dependency-due-rule-grouping-and-availability-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish activity, assignment, instruction, sequence, dependency, due rule, grouping and availability?", "kind": "process", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "activity-assignment-instruction-sequence-dependency-due-rule-grouping-and-availability-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support activity, assignment, instruction, sequence, dependency, due rule, grouping and availability?", "kind": "ownership", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "activity-assignment-instruction-sequence-dependency-due-rule-grouping-and-availability-q03", "text": "How may activity, assignment, instruction, sequence, dependency, due rule, grouping and availability be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "state", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "activity-assignment-instruction-sequence-dependency-due-rule-grouping-and-availability-data", "name": "Activity, assignment, instruction, sequence, dependency, due rule, grouping and availability data", "description": "Structured learning-delivery data for activity, assignment, instruction, sequence, dependency, due rule, grouping and availability with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011" ] } ], "artifacts": [ { "id": "activity-assignment-instruction-sequence-dependency-due-rule-grouping-and-availability-record", "name": "Activity, assignment, instruction, sequence, dependency, due rule, grouping and availability record", "description": "Versioned evidence-bearing learning-delivery record for activity, assignment, instruction, sequence, dependency, due rule, grouping and availability with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus activity-assignment-instruction-sequence-dependency-due-rule-grouping-and-availability assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "instruction-participation-and-learning-evidence", "name": "Instruction, participation and learning evidence", "description": "Captures actual facilitation and learner activity while separating raw events from engagement or learning claims.", "rationale": "Access, login, presence, activity, engagement, learning, mastery and completion are different assertions. Every event requires actor, action, object, context, time, authority and privacy controls.", "source_refs": [ "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-014", "SRC-016" ], "layers": [ { "id": "attendance-participation-attempts-and-experience-events", "name": "Attendance, participation, attempts and experience events", "description": "Records source-qualified occurrences without over-interpreting them.", "source_refs": [ "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-016" ], "findings": [ { "id": "attendance-presence-access-participation-status-duration-and-evidence", "name": "Attendance, presence, access, participation, status, duration and evidence", "description": "External attendance or presence references, event scope, claimed or observed status, duration and breaks, source method, evidence, disputes and explicit distinction from login and engagement.", "source_refs": [ "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-016" ], "questions": [ { "id": "attendance-presence-access-participation-status-duration-and-evidence-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish attendance, presence, access, participation, status, duration and evidence?", "kind": "evidence", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "attendance-presence-access-participation-status-duration-and-evidence-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support attendance, presence, access, participation, status, duration and evidence?", "kind": "event", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "attendance-presence-access-participation-status-duration-and-evidence-q03", "text": "How may attendance, presence, access, participation, status, duration and evidence be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "measurement", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "attendance-presence-access-participation-status-duration-and-evidence-data", "name": "Attendance, presence, access, participation, status, duration and evidence data", "description": "Structured learning-delivery data for attendance, presence, access, participation, status, duration and evidence with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-016" ] } ], "artifacts": [ { "id": "attendance-presence-access-participation-status-duration-and-evidence-record", "name": "Attendance, presence, access, participation, status, duration and evidence record", "description": "Versioned evidence-bearing learning-delivery record for attendance, presence, access, participation, status, duration and evidence with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus attendance-presence-access-participation-status-duration-and-evidence assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "learning-event-actor-action-object-attempt-result-context-time-authority-and-voiding", "name": "Learning event, actor, action, object, attempt, result, context, time, authority and voiding", "description": "Immutable xAPI or Caliper-like source event, actor or pseudonym, verb or action, object and definition, registration or delivery context, attempt, result, event and stored times, authority, attachments and invalidation link.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-016" ], "questions": [ { "id": "learning-event-actor-action-object-attempt-result-context-time-authority-and-voiding-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish learning event, actor, action, object, attempt, result, context, time, authority and voiding?", "kind": "event", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "learning-event-actor-action-object-attempt-result-context-time-authority-and-voiding-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support learning event, actor, action, object, attempt, result, context, time, authority and voiding?", "kind": "security", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "learning-event-actor-action-object-attempt-result-context-time-authority-and-voiding-q03", "text": "How may learning event, actor, action, object, attempt, result, context, time, authority and voiding be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "definition", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "learning-event-actor-action-object-attempt-result-context-time-authority-and-voiding-data", "name": "Learning event, actor, action, object, attempt, result, context, time, authority and voiding data", "description": "Structured learning-delivery data for learning event, actor, action, object, attempt, result, context, time, authority and voiding with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-016" ] } ], "artifacts": [ { "id": "learning-event-actor-action-object-attempt-result-context-time-authority-and-voiding-record", "name": "Learning event, actor, action, object, attempt, result, context, time, authority and voiding record", "description": "Versioned evidence-bearing learning-delivery record for learning event, actor, action, object, attempt, result, context, time, authority and voiding with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus learning-event-actor-action-object-attempt-result-context-time-authority-and-voiding assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "instruction-feedback-communication-and-support", "name": "Instruction, feedback, communication and support", "description": "Preserves teaching and support actions with their scope and audience.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-014" ], "findings": [ { "id": "instruction-facilitation-demonstration-guidance-question-feedback-and-adaptation", "name": "Instruction, facilitation, demonstration, guidance, question, feedback and adaptation", "description": "Actual instructional action, actor, audience, learning target, method, resources, feedback type, adaptation, reason, response window and evidence.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-010" ], "questions": [ { "id": "instruction-facilitation-demonstration-guidance-question-feedback-and-adaptation-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish instruction, facilitation, demonstration, guidance, question, feedback and adaptation?", "kind": "process", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "instruction-facilitation-demonstration-guidance-question-feedback-and-adaptation-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support instruction, facilitation, demonstration, guidance, question, feedback and adaptation?", "kind": "interoperability", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "instruction-facilitation-demonstration-guidance-question-feedback-and-adaptation-q03", "text": "How may instruction, facilitation, demonstration, guidance, question, feedback and adaptation be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "authority", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "instruction-facilitation-demonstration-guidance-question-feedback-and-adaptation-data", "name": "Instruction, facilitation, demonstration, guidance, question, feedback and adaptation data", "description": "Structured learning-delivery data for instruction, facilitation, demonstration, guidance, question, feedback and adaptation with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "instruction-facilitation-demonstration-guidance-question-feedback-and-adaptation-record", "name": "Instruction, facilitation, demonstration, guidance, question, feedback and adaptation record", "description": "Versioned evidence-bearing learning-delivery record for instruction, facilitation, demonstration, guidance, question, feedback and adaptation with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus instruction-facilitation-demonstration-guidance-question-feedback-and-adaptation assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "announcement-discussion-collaboration-message-support-intervention-referral-and-followup", "name": "Announcement, discussion, collaboration, message, support, intervention, referral and follow-up", "description": "External communication and support references, participants and roles, purpose, channel, protected content pointer, trigger evidence, responsible party, follow-up and outcome without copying message bodies by default.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-014" ], "questions": [ { "id": "announcement-discussion-collaboration-message-support-intervention-referral-and-followup-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish announcement, discussion, collaboration, message, support, intervention, referral and follow-up?", "kind": "relationship", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "announcement-discussion-collaboration-message-support-intervention-referral-and-followup-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support announcement, discussion, collaboration, message, support, intervention, referral and follow-up?", "kind": "composition", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "announcement-discussion-collaboration-message-support-intervention-referral-and-followup-q03", "text": "How may announcement, discussion, collaboration, message, support, intervention, referral and follow-up be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "retention", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "announcement-discussion-collaboration-message-support-intervention-referral-and-followup-data", "name": "Announcement, discussion, collaboration, message, support, intervention, referral and follow-up data", "description": "Structured learning-delivery data for announcement, discussion, collaboration, message, support, intervention, referral and follow-up with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-014" ] } ], "artifacts": [ { "id": "announcement-discussion-collaboration-message-support-intervention-referral-and-followup-record", "name": "Announcement, discussion, collaboration, message, support, intervention, referral and follow-up record", "description": "Versioned evidence-bearing learning-delivery record for announcement, discussion, collaboration, message, support, intervention, referral and follow-up with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus announcement-discussion-collaboration-message-support-intervention-referral-and-followup assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-014" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "assessment-progress-outcomes-and-completion", "name": "Assessment, progress, outcomes and completion", "description": "Relates delivery evidence to assessed performance and bounded outcome assertions.", "rationale": "Assessment definition, submission, result, grade, mastery, completion, credit, qualification and credential are distinct records. No downstream claim may be inferred solely from one score or activity event.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-012" ], "layers": [ { "id": "assessment-administration-submission-result-and-feedback", "name": "Assessment administration, submission, result and feedback", "description": "Binds reusable assessment definitions to delivery occurrences and independently governed evidence.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ], "findings": [ { "id": "assessment-test-item-task-rubric-criterion-learning-objective-and-administration", "name": "Assessment, test, item, task, rubric, criterion, learning objective and administration", "description": "External assessment definition and exact revision, items or tasks, rubric and performance levels, competency alignment, delivery administration, assessor, accommodations, integrity controls and permitted attempts.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007", "SRC-009" ], "questions": [ { "id": "assessment-test-item-task-rubric-criterion-learning-objective-and-administration-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish assessment, test, item, task, rubric, criterion, learning objective and administration?", "kind": "requirement", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "assessment-test-item-task-rubric-criterion-learning-objective-and-administration-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support assessment, test, item, task, rubric, criterion, learning objective and administration?", "kind": "spatial", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "assessment-test-item-task-rubric-criterion-learning-objective-and-administration-q03", "text": "How may assessment, test, item, task, rubric, criterion, learning objective and administration be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "lifecycle", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "assessment-test-item-task-rubric-criterion-learning-objective-and-administration-data", "name": "Assessment, test, item, task, rubric, criterion, learning objective and administration data", "description": "Structured learning-delivery data for assessment, test, item, task, rubric, criterion, learning objective and administration with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007", "SRC-009" ] } ], "artifacts": [ { "id": "assessment-test-item-task-rubric-criterion-learning-objective-and-administration-record", "name": "Assessment, test, item, task, rubric, criterion, learning objective and administration record", "description": "Versioned evidence-bearing learning-delivery record for assessment, test, item, task, rubric, criterion, learning objective and administration with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus assessment-test-item-task-rubric-criterion-learning-objective-and-administration assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "submission-attempt-response-evidence-score-grade-result-feedback-review-and-appeal", "name": "Submission, attempt, response, evidence, score, grade, result, feedback, review and appeal", "description": "External submission and result IDs, attempt, response or artifact pointers, score and scale, grade, success and completion flags, feedback, grading authority, confidence, moderation, review, appeal and correction lineage.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "submission-attempt-response-evidence-score-grade-result-feedback-review-and-appeal-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish submission, attempt, response, evidence, score, grade, result, feedback, review and appeal?", "kind": "validation", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "submission-attempt-response-evidence-score-grade-result-feedback-review-and-appeal-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support submission, attempt, response, evidence, score, grade, result, feedback, review and appeal?", "kind": "constraint", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "submission-attempt-response-evidence-score-grade-result-feedback-review-and-appeal-q03", "text": "How may submission, attempt, response, evidence, score, grade, result, feedback, review and appeal be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "evidence", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "submission-attempt-response-evidence-score-grade-result-feedback-review-and-appeal-data", "name": "Submission, attempt, response, evidence, score, grade, result, feedback, review and appeal data", "description": "Structured learning-delivery data for submission, attempt, response, evidence, score, grade, result, feedback, review and appeal with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "submission-attempt-response-evidence-score-grade-result-feedback-review-and-appeal-record", "name": "Submission, attempt, response, evidence, score, grade, result, feedback, review and appeal record", "description": "Versioned evidence-bearing learning-delivery record for submission, attempt, response, evidence, score, grade, result, feedback, review and appeal with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus submission-attempt-response-evidence-score-grade-result-feedback-review-and-appeal assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "progress-mastery-completion-credit-and-achievement", "name": "Progress, mastery, completion, credit and achievement", "description": "Issues bounded delivery-scoped summaries while referencing authoritative personal and credential records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-008", "SRC-009", "SRC-012" ], "findings": [ { "id": "progress-status-pathway-milestone-competency-evidence-mastery-and-uncertainty", "name": "Progress status, pathway, milestone, competency evidence, mastery and uncertainty", "description": "Progress calculation and effective time, pathway position, milestones, competency or learning-outcome evidence, mastery rule and version, issuer, confidence, contrary evidence and expiry.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008", "SRC-009", "SRC-012" ], "questions": [ { "id": "progress-status-pathway-milestone-competency-evidence-mastery-and-uncertainty-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish progress status, pathway, milestone, competency evidence, mastery and uncertainty?", "kind": "measurement", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "progress-status-pathway-milestone-competency-evidence-mastery-and-uncertainty-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support progress status, pathway, milestone, competency evidence, mastery and uncertainty?", "kind": "quality", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "progress-status-pathway-milestone-competency-evidence-mastery-and-uncertainty-q03", "text": "How may progress status, pathway, milestone, competency evidence, mastery and uncertainty be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "identity", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "progress-status-pathway-milestone-competency-evidence-mastery-and-uncertainty-data", "name": "Progress status, pathway, milestone, competency evidence, mastery and uncertainty data", "description": "Structured learning-delivery data for progress status, pathway, milestone, competency evidence, mastery and uncertainty with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-008", "SRC-009", "SRC-012" ] } ], "artifacts": [ { "id": "progress-status-pathway-milestone-competency-evidence-mastery-and-uncertainty-record", "name": "Progress status, pathway, milestone, competency evidence, mastery and uncertainty record", "description": "Versioned evidence-bearing learning-delivery record for progress status, pathway, milestone, competency evidence, mastery and uncertainty with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus progress-status-pathway-milestone-competency-evidence-mastery-and-uncertainty assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008", "SRC-009", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "completion-withdrawal-failure-credit-outcome-qualification-credential-and-next-step", "name": "Completion, withdrawal, failure, credit, outcome, qualification, credential and next step", "description": "Delivery disposition and authority, completion-rule evaluation, withdrawal or failure reason, credit recommendation or award reference, qualification and credential links, achievement assertion, progression eligibility and next step.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-009", "SRC-012" ], "questions": [ { "id": "completion-withdrawal-failure-credit-outcome-qualification-credential-and-next-step-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish completion, withdrawal, failure, credit, outcome, qualification, credential and next step?", "kind": "lifecycle", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "completion-withdrawal-failure-credit-outcome-qualification-credential-and-next-step-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support completion, withdrawal, failure, credit, outcome, qualification, credential and next step?", "kind": "access", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "completion-withdrawal-failure-credit-outcome-qualification-credential-and-next-step-q03", "text": "How may completion, withdrawal, failure, credit, outcome, qualification, credential and next step be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "requirement", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "completion-withdrawal-failure-credit-outcome-qualification-credential-and-next-step-data", "name": "Completion, withdrawal, failure, credit, outcome, qualification, credential and next step data", "description": "Structured learning-delivery data for completion, withdrawal, failure, credit, outcome, qualification, credential and next step with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-009", "SRC-012" ] } ], "artifacts": [ { "id": "completion-withdrawal-failure-credit-outcome-qualification-credential-and-next-step-record", "name": "Completion, withdrawal, failure, credit, outcome, qualification, credential and next step record", "description": "Versioned evidence-bearing learning-delivery record for completion, withdrawal, failure, credit, outcome, qualification, credential and next step with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus completion-withdrawal-failure-credit-outcome-qualification-credential-and-next-step assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-009", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "quality-lifecycle-interoperability-and-agents", "name": "Quality, lifecycle, interoperability and agents", "description": "Controls delivery change, quality improvement, exchange, privacy, retention and safe machine operations.", "rationale": "A delivery must remain inspectable as its schedule, roster, content, evidence, grades and outcomes change, and exchange profiles must preserve loss and authority instead of becoming a hidden master.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016" ], "layers": [ { "id": "lifecycle-quality-accessibility-and-improvement", "name": "Lifecycle, quality, accessibility and improvement", "description": "Preserves state history, evaluation evidence and governed changes.", "source_refs": [ "SRC-004", "SRC-005", "SRC-009", "SRC-010", "SRC-014", "SRC-016" ], "findings": [ { "id": "planned-published-enrollment-scheduled-active-paused-closed-completed-cancelled-and-archived-event", "name": "Planned, published, enrollment, scheduled, active, paused, closed, completed, cancelled and archived event", "description": "Typed lifecycle event, prior and next state, actor, authority, rationale, effective and recorded times, affected cohort or scope, evidence, correction, repeat and supersession.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-009", "SRC-013", "SRC-016" ], "questions": [ { "id": "planned-published-enrollment-scheduled-active-paused-closed-completed-cancelled-and-archived-event-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish planned, published, enrollment, scheduled, active, paused, closed, completed, cancelled and archived event?", "kind": "lifecycle", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "planned-published-enrollment-scheduled-active-paused-closed-completed-cancelled-and-archived-event-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support planned, published, enrollment, scheduled, active, paused, closed, completed, cancelled and archived event?", "kind": "identity", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "planned-published-enrollment-scheduled-active-paused-closed-completed-cancelled-and-archived-event-q03", "text": "How may planned, published, enrollment, scheduled, active, paused, closed, completed, cancelled and archived event be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "access", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "planned-published-enrollment-scheduled-active-paused-closed-completed-cancelled-and-archived-event-data", "name": "Planned, published, enrollment, scheduled, active, paused, closed, completed, cancelled and archived event data", "description": "Structured learning-delivery data for planned, published, enrollment, scheduled, active, paused, closed, completed, cancelled and archived event with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-009", "SRC-013", "SRC-016" ] } ], "artifacts": [ { "id": "planned-published-enrollment-scheduled-active-paused-closed-completed-cancelled-and-archived-event-record", "name": "Planned, published, enrollment, scheduled, active, paused, closed, completed, cancelled and archived event record", "description": "Versioned evidence-bearing learning-delivery record for planned, published, enrollment, scheduled, active, paused, closed, completed, cancelled and archived event with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus planned-published-enrollment-scheduled-active-paused-closed-completed-cancelled-and-archived-event assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-009", "SRC-013", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "delivery-quality-accessibility-integrity-equity-satisfaction-evaluation-and-improvement", "name": "Delivery quality, accessibility, integrity, equity, satisfaction, evaluation and improvement", "description": "Quality criteria and observations, accessibility conformance and barriers, instructional integrity, participation or outcome disparities, learner feedback, evaluation method, limitations, improvement action and later evidence.", "source_refs": [ "SRC-005", "SRC-009", "SRC-010", "SRC-014" ], "questions": [ { "id": "delivery-quality-accessibility-integrity-equity-satisfaction-evaluation-and-improvement-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish delivery quality, accessibility, integrity, equity, satisfaction, evaluation and improvement?", "kind": "quality", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "delivery-quality-accessibility-integrity-equity-satisfaction-evaluation-and-improvement-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support delivery quality, accessibility, integrity, equity, satisfaction, evaluation and improvement?", "kind": "lifecycle", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "delivery-quality-accessibility-integrity-equity-satisfaction-evaluation-and-improvement-q03", "text": "How may delivery quality, accessibility, integrity, equity, satisfaction, evaluation and improvement be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "temporal", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "delivery-quality-accessibility-integrity-equity-satisfaction-evaluation-and-improvement-data", "name": "Delivery quality, accessibility, integrity, equity, satisfaction, evaluation and improvement data", "description": "Structured learning-delivery data for delivery quality, accessibility, integrity, equity, satisfaction, evaluation and improvement with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-009", "SRC-010", "SRC-014" ] } ], "artifacts": [ { "id": "delivery-quality-accessibility-integrity-equity-satisfaction-evaluation-and-improvement-record", "name": "Delivery quality, accessibility, integrity, equity, satisfaction, evaluation and improvement record", "description": "Versioned evidence-bearing learning-delivery record for delivery quality, accessibility, integrity, equity, satisfaction, evaluation and improvement with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus delivery-quality-accessibility-integrity-equity-satisfaction-evaluation-and-improvement assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-005", "SRC-009", "SRC-010", "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "interoperability-provenance-access-retention-and-safe-automation", "name": "Interoperability, provenance, access, retention and safe automation", "description": "Creates loss-aware views and governs human and agent operations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016" ], "findings": [ { "id": "isced-elm-eduapi-oneroster-caliper-case-qti-xapi-clr-courseinstance-crosswalk", "name": "ISCED, ELM, Edu-API, OneRoster, Caliper, CASE, QTI, xAPI, CLR and CourseInstance crosswalk", "description": "Pinned source and target versions, identity, offering, class, enrollment, activity, competency, resource, assessment, result, achievement, event and provenance mappings, omissions, conflicts and round-trip classification.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-011", "SRC-012", "SRC-013" ], "questions": [ { "id": "isced-elm-eduapi-oneroster-caliper-case-qti-xapi-clr-courseinstance-crosswalk-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish isced, elm, edu-api, oneroster, caliper, case, qti, xapi, clr and courseinstance crosswalk?", "kind": "interoperability", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "isced-elm-eduapi-oneroster-caliper-case-qti-xapi-clr-courseinstance-crosswalk-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support isced, elm, edu-api, oneroster, caliper, case, qti, xapi, clr and courseinstance crosswalk?", "kind": "authority", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "isced-elm-eduapi-oneroster-caliper-case-qti-xapi-clr-courseinstance-crosswalk-q03", "text": "How may isced, elm, edu-api, oneroster, caliper, case, qti, xapi, clr and courseinstance crosswalk be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "quality", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "isced-elm-eduapi-oneroster-caliper-case-qti-xapi-clr-courseinstance-crosswalk-data", "name": "ISCED, ELM, Edu-API, OneRoster, Caliper, CASE, QTI, xAPI, CLR and CourseInstance crosswalk data", "description": "Structured learning-delivery data for isced, elm, edu-api, oneroster, caliper, case, qti, xapi, clr and courseinstance crosswalk with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-011", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "isced-elm-eduapi-oneroster-caliper-case-qti-xapi-clr-courseinstance-crosswalk-record", "name": "ISCED, ELM, Edu-API, OneRoster, Caliper, CASE, QTI, xAPI, CLR and CourseInstance crosswalk record", "description": "Versioned evidence-bearing learning-delivery record for isced, elm, edu-api, oneroster, caliper, case, qti, xapi, clr and courseinstance crosswalk with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus isced-elm-eduapi-oneroster-caliper-case-qti-xapi-clr-courseinstance-crosswalk assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-011", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "purpose-access-privacy-redaction-retention-hold-agent-authority-idempotency-and-postcheck", "name": "Purpose, access, privacy, redaction, retention, hold, agent authority, idempotency and post-check", "description": "Purpose-bound role views, field redaction, disclosure and export decisions, retention trigger, hold, deletion eligibility, minimum tombstone, delegated agent scope, preconditions, dry run, idempotency key, expected revision and post-condition verification.", "source_refs": [ "SRC-008", "SRC-009", "SRC-014", "SRC-015", "SRC-016" ], "questions": [ { "id": "purpose-access-privacy-redaction-retention-hold-agent-authority-idempotency-and-postcheck-q01", "text": "What delivery-scoped identities, classifications, roles, definitions, versions, values and explicit unknowns establish purpose, access, privacy, redaction, retention, hold, agent authority, idempotency and post-check?", "kind": "access", "answer_data": [ "identifiers and classifications", "roles, scope and versions", "values and explicit unknowns" ] }, { "id": "purpose-access-privacy-redaction-retention-hold-agent-authority-idempotency-and-postcheck-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support purpose, access, privacy, redaction, retention, hold, agent authority, idempotency and post-check?", "kind": "measurement", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "purpose-access-privacy-redaction-retention-hold-agent-authority-idempotency-and-postcheck-q03", "text": "How may purpose, access, privacy, redaction, retention, hold, agent authority, idempotency and post-check be validated, accessed, adapted, disputed, corrected, related, retained or disposed without losing prior delivery history?", "kind": "classification", "answer_data": [ "validation and access rules", "authorized adaptation and dispute", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "purpose-access-privacy-redaction-retention-hold-agent-authority-idempotency-and-postcheck-data", "name": "Purpose, access, privacy, redaction, retention, hold, agent authority, idempotency and post-check data", "description": "Structured learning-delivery data for purpose, access, privacy, redaction, retention, hold, agent authority, idempotency and post-check with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-008", "SRC-009", "SRC-014", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "purpose-access-privacy-redaction-retention-hold-agent-authority-idempotency-and-postcheck-record", "name": "Purpose, access, privacy, redaction, retention, hold, agent authority, idempotency and post-check record", "description": "Versioned evidence-bearing learning-delivery record for purpose, access, privacy, redaction, retention, hold, agent authority, idempotency and post-check with authority, time, provenance and access marking.", "media_or_form": [ "logical learning-delivery assertion", "plan, roster link, event, evidence, result, outcome or governance reference" ], "serial": true, "identity_strategy": "Delivery identifier plus purpose-access-privacy-redaction-retention-hold-agent-authority-idempotency-and-postcheck assertion, artifact or event identifier; title, date, timestamp and digest never identify the delivery alone.", "source_refs": [ "SRC-008", "SRC-009", "SRC-014", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-learning-delivery", "name": "Register learning delivery", "description": "Create a stable aggregate identity and mandatory delivery profile while resolving duplicate offerings and neighboring masters.", "inputs": [ "delivery request", "definition references", "provider authority", "profile" ], "outputs": [ "versioned learning-delivery root" ], "preconditions": [ "identity, duplicate, profile, authority and boundary checks pass" ], "effects": [ "one delivery aggregate exists without copying the course definition, learner or programme" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-009", "SRC-013" ] }, { "id": "bind-curriculum-objectives-and-design", "name": "Bind curriculum, objectives and design", "description": "Freeze exact course or activity definitions, competency targets, prerequisites, pedagogy, sequence and success rules.", "inputs": [ "delivery root", "curriculum and activity revisions", "objectives", "design" ], "outputs": [ "instructional-design release" ], "preconditions": [ "versions, scope, outcomes, workload, dependencies, language and adaptation rules validate" ], "effects": [ "delivery intent remains interpretable after source definitions change" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-011", "SRC-013" ] }, { "id": "assign-authority-roles-and-safeguards", "name": "Assign authority, roles and safeguards", "description": "Bind provider, instructors, assessors, support roles, privacy rules and accessibility controls.", "inputs": [ "design release", "actor references", "policies", "accessibility needs" ], "outputs": [ "governance and role release" ], "preconditions": [ "authority, delegation, separation, privacy, accessibility and exception checks pass" ], "effects": [ "learning delivery can operate within an explicit control envelope" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-009", "SRC-010", "SRC-014" ] }, { "id": "enroll-allocate-and-provision", "name": "Enroll, allocate and provision", "description": "Record source-qualified learner and cohort relationships, eligibility, capacity, waitlist, access and accommodations.", "inputs": [ "delivery", "learner references", "enrollment decisions", "resource policy" ], "outputs": [ "participation and access release" ], "preconditions": [ "identity matching, eligibility, prerequisite, capacity, privacy and accommodation checks pass" ], "effects": [ "participants receive governed access without inferring attendance" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-010", "SRC-014" ] }, { "id": "schedule-sessions-and-resources", "name": "Schedule sessions and resources", "description": "Publish and revise calendars, locations, modality, content, tools, activities and availability.", "inputs": [ "authorized delivery", "academic session", "resource references", "calendar" ], "outputs": [ "schedule and resource release" ], "preconditions": [ "time-zone, recurrence, rights, version, accessibility, dependency and capacity checks pass" ], "effects": [ "participants and systems can resolve what is available when and where" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-013", "SRC-016" ] }, { "id": "record-instruction-and-participation", "name": "Record instruction and participation", "description": "Append actual sessions, facilitation, attendance and immutable learner-experience events without converting them into learning claims.", "inputs": [ "active delivery", "source events", "actor and object references" ], "outputs": [ "instruction and participation event stream" ], "preconditions": [ "actor, action, object, context, authority, time, privacy and voiding checks pass" ], "effects": [ "actual delivery history remains attributable and source-qualified" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-014", "SRC-016" ] }, { "id": "administer-assessments-and-return-feedback", "name": "Administer assessments and return feedback", "description": "Bind exact assessment revisions, accept governed submissions and record results, grades, feedback and review lineage.", "inputs": [ "delivery", "assessment definition", "submission or response", "grading policy" ], "outputs": [ "administration, result and feedback release" ], "preconditions": [ "attempt, accommodation, integrity, scale, assessor, evidence, moderation and appeal checks pass" ], "effects": [ "performance evidence remains distinct from mastery and qualification" ], "source_refs": [ "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ] }, { "id": "evaluate-progress-mastery-and-completion", "name": "Evaluate progress, mastery and completion", "description": "Apply versioned rules to evidence and issue bounded delivery-scoped progress and disposition assertions.", "inputs": [ "activity and assessment evidence", "objectives", "progress and completion rules" ], "outputs": [ "progress, mastery or completion assertion" ], "preconditions": [ "rule version, evidence, authority, uncertainty, contrary evidence and downstream-boundary checks pass" ], "effects": [ "course completion does not automatically become qualification or credential issuance" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-009", "SRC-012" ] }, { "id": "review-correct-repeat-and-improve", "name": "Review, correct, repeat and improve", "description": "Preserve released history while appending disputes, corrections, cancellations, improvements or a new repeat-delivery identity.", "inputs": [ "current delivery head", "review or quality evidence", "change authority" ], "outputs": [ "review event, correction successor, improvement action or new delivery root" ], "preconditions": [ "expected revision, reason, impact, affected scope and residual-validity checks pass" ], "effects": [ "later change cannot erase prior rosters, events, grades or outcomes" ], "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-015", "SRC-016" ] }, { "id": "project-disclose-retain-and-audit", "name": "Project, disclose, retain and audit", "description": "Create version-pinned external views and perform controlled access, export and information-lifecycle operations.", "inputs": [ "delivery revision", "target profile", "purpose", "policy" ], "outputs": [ "projection, disclosure, disposition or audit event" ], "preconditions": [ "mapping loss, privacy, redaction, hold, tombstone, idempotency and post-checks validate" ], "effects": [ "learning context remains interoperable, protected and accountable" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016" ] } ], "composition": [ { "target": "Course, Learning Activity, Curriculum, Programme, Competency and Learning Outcome models", "relation": "REFERENCE", "purpose": "Resolve immutable learning intent and reusable definitions while keeping the delivery realization separate.", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-011", "SRC-013" ] }, { "target": "Person, Learner, Organization, Cohort, Enrollment and Role models", "relation": "REFERENCE", "purpose": "Bind provider, instructor and participant roles without copying identity, admission or enrollment lifecycles.", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009", "SRC-014" ] }, { "target": "Academic Session, Schedule, Location, Resource, Tool, Communication and Dataset models", "relation": "REFERENCE", "purpose": "Bind delivery timing, environment, resources and external communications through exact source versions.", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-009", "SRC-011", "SRC-013", "SRC-016" ] }, { "target": "Attendance, Experience Event, Assessment Definition, Submission and Assessment Result models", "relation": "COMPOSE", "purpose": "Relate governed delivery occurrences and evidence without absorbing their source identity, authority or correction history.", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ] }, { "target": "Qualification, Credential, Comprehensive Learner Record and Education or Qualification models", "relation": "REFERENCE", "purpose": "Link bounded completion and mastery evidence to separately authorized personal achievement and credential records.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-012" ] }, { "target": "ISCED 2011, European Learning Model, Edu-API, OneRoster 1.2, Caliper 1.2, CASE 1.1, QTI 3, xAPI 2.0, Common Cartridge, CLR 2.0 and Schema.org CourseInstance", "relation": "ALIGN", "purpose": "Project classification, opportunity, offering, roster, event, competency, assessment, content and achievement views through version-pinned mappings with declared loss.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, education or training authority, provider, academic, privacy, accessibility, data and records stewards", "Learning-delivery profile, definition, curriculum, role, enrollment, schedule, resource, participation, assessment, progress, lifecycle, interoperability, access and retention registries", "Master mappings for people, learners, organizations, programmes, courses, activities, competencies, sessions, locations, resources, tools, enrollments, attendance, assessments, submissions, results, qualifications, credentials, communications, artifacts and audit records", "Delivery release, roster, access, accessibility, instruction, assessment, grading, completion, correction, disclosure, retention and agent-operation policies" ], "namespace_guidance": "Mint stable IDs for delivery roots, releases, profile bindings, schedules, role and participation assertions, session and learning events, assessment administrations, progress and completion assertions, reviews and lifecycle events. Preserve authoritative external course, learner, enrollment, assessment, result, qualification and credential identities; never use title, class code, date or digest as delivery identity.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local learning, curriculum, delivery, participant, assessment, outcome and policy registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative source plus delivery identifier, mandatory delivery profile and lineage head, not by course title, class code, dates, instructor or digest.", "Keep reusable definition, planned activity, actual session, access, attendance, experience event, assessment, grade, mastery, completion, qualification and credential as distinct assertion classes." ], "patch_rules": [ "Extensions declare education sector and delivery profile, target finding, semantics, authority, lifecycle, accessibility, privacy, assessment, quality and interoperability effects.", "Released rosters, schedules, events, submissions, results, grades and outcomes are immutable; corrections create attributable successors and repeat deliveries create new roots.", "A patch must never silently change curriculum revision, objectives, eligibility, learner identity, accommodations, grading rule, source evidence or original event history." ], "compatibility_rules": [ "Unknown additive fields may be ignored only when delivery identity, profile, curriculum binding, roles, participants, schedule, evidence, assessment, outcomes, lifecycle and provenance remain intact.", "ISCED, ELM, Edu-API, OneRoster, Caliper, CASE, QTI, xAPI, CLR, Common Cartridge and CourseInstance mappings pin versions and declare omissions, semantic conflicts and round-trip limits." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system delivery or class-offering identifier qualified by source and delivery profile.", "Governed globally resolvable delivery IRI under a controlled namespace.", "Dimension UUID when no authoritative or governed global identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; separate planned, effective, event, submission, assessment, result, release, ingestion and knowledge times and preserve source precision.", "serial_naming_rule": "Use {delivery-id}--{release-or-session}--{artifact-kind}--{assertion-or-event-id}; never use title, class code, date, timestamp or digest alone.", "integrity_rule": "Store digest, media type, delivery and release binding, source and profile versions, definition, resource, assessment and grading revisions, generating actor or tool, event and knowledge times, access marking and provenance." }, "policies": [ "A Learning Activity or Course Delivery is not the reusable Course or Activity Definition, Curriculum or Programme, a Learner, Enrollment, Session, learning event, Assessment, Qualification or Credential.", "Access, login, attendance, participation, engagement, learning, assessment success, mastery, completion, credit, qualification and credential remain separate source-qualified assertions.", "Delivery ownership does not transfer ownership of person, learner, organization, programme, course, activity, competency, session, location, resource, tool, enrollment, attendance, assessment, submission, result, qualification, credential, communication, artifact or audit masters. Delivery disposition never cascades to linked masters.", "Agents may validate, link and project allowlisted data, but enrollment admission, learner contact, accommodation decisions, grading, mastery or completion signoff, credential issuance, protected disclosure and disposition require delegated authority and applicable policies." ], "crud": { "read": [ "Resolve Dimension policies, delivery identity and lineage, profile, definition bindings, objectives, roles, participants, schedule, resources, instruction, events, assessments, progress, outcomes, provenance and access purpose." ], "create": [ "Record delivery identity and profile, exact course or activity definition, objectives, provider, roles, schedule, resource and policy bindings before accepting participants or events." ], "update": [ "Append enrollment, access, schedule, resource, session, participation, instruction, submission, result, grade, progress, completion, review, correction, cancellation or supersession events with actor, authority, rationale, event and knowledge time and expected revision; never overwrite released history." ], "delete": [ "Apply learner-rights, academic, contract, privacy, records, retention and legal-hold policy; cancel or archive a delivery separately from deleting eligible working copies, preserve required evidence lineage and minimum tombstone, and never cascade deletion to linked masters." ] }, "roles": [ { "name": "Learning provider or accountable authority", "responsibilities": [ "Own delivery mandate, policy, responsible-party appointment, resource envelope and accountable disposition." ] }, { "name": "Course, activity or curriculum steward", "responsibilities": [ "Own reusable definitions, objectives, competencies, prerequisites and permitted adaptations." ] }, { "name": "Instructor, facilitator or mentor", "responsibilities": [ "Perform authorized instruction, guidance, feedback and learner support while recording material deviations." ] }, { "name": "Registrar or enrollment steward", "responsibilities": [ "Own external learner matching, enrollment, eligibility, capacity, waitlist and status assertions." ] }, { "name": "Assessment and grading authority", "responsibilities": [ "Own assessment definitions, administration rules, scoring, grading, moderation, appeal and correction authority." ] }, { "name": "Accessibility, learner-support and safeguarding steward", "responsibilities": [ "Control accommodations, accessible alternatives, support and applicable safeguarding without unnecessary disclosure." ] }, { "name": "Learning-data and interoperability steward", "responsibilities": [ "Protect event semantics, source mappings, analytics limits, versions, quality and provenance." ] }, { "name": "Privacy, access and records steward", "responsibilities": [ "Control protected views, exports, retention, holds, disposition and access auditability." ] } ], "access": { "default_rule": "Deny direct learner identifiers, demographics, disability or accommodation details, communications, submissions, grades, behavioural analytics, predictions and protected content unless a purpose-bound Dimension policy permits the minimum necessary view. Field redaction is a governed projection, not a separate access scope.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Learner, guardian where applicable, instructor, assessor, support worker, registrar, provider, auditor, regulator or court access cites authority and remains minimum-necessary, time-limited and separately logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, delivery, operation, policy, RFC 3339 time, release or affected fields, source revision and outcome without copying protected learner data unnecessarily." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension education, learner-rights, safeguarding, accessibility, privacy, access, assessment, retention and agent-operation policies.", "Read this model and linked person, learner, organization, programme, course, activity, competency, session, location, resource, tool, enrollment, attendance, assessment, submission, result, qualification, credential, communication, artifact and audit models before mutation." ] } }, "coverage": { "claim": "Covers a cross-sector Learning Activity / Course Delivery aggregate from immutable definition and objective bindings through roles, enrollment, schedule, resources, instruction, participation evidence, assessment, bounded progress and completion assertions, lifecycle, interoperability and governed disposition. Scope is clear and composition relations to external masters are explicit. Interoperability mappings are intentional but not proven working; accessibility and regional legal variance require further specialist review; technical inference safeguards are policy-stated but not machine-enforced in schema.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Delivery, release, profile, schedule, role, participant, event, assessment, result, outcome and lifecycle identities are distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Formal, non-formal, informal and workplace profiles and definition, programme, learner-record and event boundaries are explicit." }, { "dimension": "direct properties", "status": "covered", "notes": "Curriculum binding, objectives, roles, participants, schedule, resources, instruction, evidence, assessment, progress and completion are first-class." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Attendance, activity, assessment and outcome observations retain source method, scope, time, confidence and limitations." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Register, bind, assign, enroll, schedule, deliver, record, assess, evaluate, review, project and retain are governed." }, { "dimension": "composition", "status": "gap", "notes": "People, learners, programmes, courses, activities, competencies, sessions, resources, enrollments, assessments, results, qualifications and credentials remain external masters. Proposed relations or mapping versions remain held for review." }, { "dimension": "lifecycle", "status": "covered", "notes": "Planning, publication, enrollment, scheduling, activation, pause, closure, completion, cancellation, correction, repeat and archive preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Definition, curriculum, role, enrollment, schedule, activity, evidence, assessment, outcome and crosswalk links are typed." }, { "dimension": "temporal", "status": "covered", "notes": "Planned, effective, session, event, submission, assessment, result, release, ingestion and knowledge times remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Physical, virtual and blended locations, rooms, platforms and event contexts remain source-qualified." }, { "dimension": "provenance", "status": "covered", "notes": "Plans, agents, used resources, generated events, submissions, results, outcomes, revisions and invalidations preserve provenance." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Provider, curriculum, instruction, enrollment, assessment, support, accessibility, privacy, data and records duties are separated." }, { "dimension": "validation and quality", "status": "covered", "notes": "Identity, revision, eligibility, schedule, resource, accessibility, evidence, grading, outcome and stale-head checks are explicit." }, { "dimension": "access and privacy", "status": "covered", "notes": "Purpose-bound views, learner privacy, accommodations, protected evidence and field-redacted projections are explicit." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Cancellation or archive, working-copy deletion, retained evidence, holds and minimum tombstones are distinguished." }, { "dimension": "interoperability", "status": "gap", "notes": "ISCED, ELM, Edu-API, OneRoster, Caliper, CASE, QTI, xAPI, CLR, Common Cartridge and CourseInstance mappings are versioned and loss-aware. Proposed relations or mapping versions remain held for review." } ], "known_omissions": [ "No successful independent Claude or Grok result was available; education-sector, pedagogy, accessibility, learner-rights, analytics, regional and legal review is required before canonical promotion.", "The slash name covers several delivery forms through a mandatory profile. Formal course, cohort, self-paced, workplace, community, informal and single-activity profiles require their own invariants.", "No approved relation rows were supplied. The registry parent link to Personal Education or Qualification and proposed definition, learner, enrollment, assessment, result and credential relations remain holds.", "Edu-API remains Candidate Final Public and its full specification is access-controlled. Common Cartridge 1.4 is Candidate Final. No final-version conformance claim is made for either.", "OneRoster is K-12 oriented, Edu-API is higher-education oriented, ELM is European, and CLR, Caliper, QTI, CASE and xAPI cover narrower exchange domains.", "Accessibility, child protection, consent, grading, record access, retention, intellectual property and credential authority vary by jurisdiction, provider and learning context." ], "conflicts": [ "Course, class, section, offering, learning opportunity, activity, session and delivery are used differently across standards. The mandatory profile and source mapping preserve those distinctions.", "Login, access, attendance, participation, engagement, learning, mastery, completion, credit, qualification and credential can disagree and must not be collapsed.", "Learner analytics, personalization, privacy, accessibility, safeguarding, academic integrity, transparency and instructor autonomy can impose competing requirements." ], "regional_assumptions": [ "K-12, higher education, vocational, workplace, professional, community and informal learning have different provider authority, learner-rights, accessibility, safeguarding and records rules.", "ISCED is a statistical classification, ELM is European, OneRoster is K-12 oriented and Edu-API targets higher education; none supplies a universal delivery lifecycle.", "QTI, CASE, Caliper, xAPI, CLR and Common Cartridge are exchange profiles whose adoption and conformance requirements do not automatically govern the Vercy aggregate." ], "adversarial_checks": [ "Reject a delivery without stable identity, mandatory profile, exact definition and objective revisions, provider authority, schedule basis and lifecycle head.", "Reject enrollment inferred from access, attendance from login, engagement or learning from time online, mastery from one score, qualification from completion or causality from analytics correlation.", "Reject a repeat delivery or correction that overwrites earlier rosters, schedules, events, submissions, grades, feedback, outcomes or source evidence.", "Reject copied learner, enrollment, resource, assessment, submission, result, qualification or credential masters whose independent identity, authority and lifecycle are lost.", "Reject agent enrollment, accommodation, grading, progression, credential issuance, protected disclosure or disposition outside delegated authority and applicable learner-rights, accessibility, privacy and retention controls." ] }, "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": "aggregate", "status": "accepted", "rationale": "The model is a bounded delivery lifecycle container (aggregate root per domain-driven design) with explicit composition relations to external masters: person, learner, organization, programme, course, activity, competency, session, location, resource, tool, enrollment, assessment, submission, result, qualification, credential, communication and audit remain external. The delivery owns identity, mandatory profile, exact definition and objective revisions, provider authority, role assignments, enrollment participation assertions, schedule, resources, instruction, events, assessments, progress and completion within its scope, not the reusable definition, learner or master system lifecycles. Five boundary notes explicitly state distinctions from neighboring entities. Mandatory profile and external definition binding confirm aggregate boundary. The schema enum 'aggregate' is correct; a frozen registry value like 'standalone-mm' classifies the record plane and is never a valid subject-model entry kind." }, "decisions": [ { "concept": "Entry kind: aggregate root classification", "disposition": "Accepted", "rationale": "Model correctly maps to schema enum 'aggregate'. It is a bounded delivery container with composition relations to external masters (learner, organization, course, assessment, credential), not a standalone entity. Mandatory profile and external definition binding confirm aggregate boundary. Five explicit boundary notes distinguish it from Course Definition, Person, Learner, Session, Assessment, Qualification and Credential masters. Domain-driven design and ownership rules support this classification." }, { "concept": "Learner and enrollment boundary: source-qualified assertions vs. external masters", "disposition": "Accepted with documentation enhancement required", "rationale": "Boundary is correctly drawn: learner and enrollment identity remain external; delivery records source-qualified participation assertions within its scope. Boundary notes explicitly distinguish 'External learner and cohort references' from 'source-qualified participation and role assertions' owned by delivery. However, data model should include explicit composition-relation artifact types (learner-reference, enrollment-reference) to enforce this at schema level, preventing accidental ownership collapse at implementation time. Accept boundary; require schema-level reinforcement." }, { "concept": "Source versioning, authority tier and specification maturity", "disposition": "Accepted with specification-level verification hold", "rationale": "All 16 sources pinned to versions or access dates (2026-09-06). Authority tier consistently 1 (primary sources). Standards bodies authoritative (UNESCO, EC, 1EdTech, W3C, IETF, NIST, ADL, UK National Archives). Coverage notes correctly identify Edu-API as Candidate Final Public (not released) and Common Cartridge 1.4 as Candidate Final. No conformance claim to final versions made, which is correct. Accept for reviewable-draft; final promotion requires final-version conformance or explicit specification-level hold declaration in publication artifacts." }, { "concept": "Inference safeguards: login, attendance, activity, learning, score, mastery, completion and qualification boundaries", "disposition": "Deferred: policy stated, schema enforcement absent", "rationale": "Adversarial checks and service-layer policies explicitly forbid collapsing: enrollment inferred from access, attendance from login, learning from activity completion, mastery from one score, qualification from completion. Policy is clear and strong. However, data model provides no technical schema elements (evidence-method tags, confidence markers, forbidden-rule validators, source-method requirements) to enforce or audit these distinctions at implementation time. Consumer implementation could still collapse them. Accept policy intent; defer with hold pending schema-level constraints that make distinctions machine-checkable." }, { "concept": "Interoperability: ISCED, ELM, Edu-API, OneRoster, Caliper, CASE, QTI, xAPI, CLR and CourseInstance crosswalk", "disposition": "Deferred: intent clear, working round-trip and conflict rules not proven", "rationale": "Model lists 11 mapping targets; crosswalk finding marked 'covered' in layer. However, coverage checklist explicitly shows 'composition' as gap; known omissions state 'proposed relations or mapping versions remain held for review.' No approved mapping tables, version-pair conflict rules or bidirectional proof supplied. OneRoster K-12 oriented, Edu-API higher-education oriented, ELM European; universal interoperability not formally claimed but variance not formally scoped. Accept intent; defer interoperability claim pending approved mapping tables with identified omissions, conflict-resolution rules for each standard pair and working round-trip tests." }, { "concept": "Lifecycle immutability and correction-history preservation", "disposition": "Accepted", "rationale": "Patch rules correctly enforce: 'Released rosters, schedules, events, submissions, results, grades and outcomes are immutable; corrections create attributable successors and repeat deliveries create new roots.' This prevents silent overwriting and preserves full history with attribution. Service-layer CRUD and adversarial checks reinforce. Accept. Technical constraint at schema level (forbidding PATCH on released artifacts, requiring POST for corrections with prior-reference) would strengthen confidence but is implementation detail." }, { "concept": "Accessibility, child protection, learner-rights and regional legal variance", "disposition": "Deferred: scope acknowledged and required, specialist review pending", "rationale": "Model references WCAG 2.2 (W3C Dec 2024) and coverage explicitly covers accessibility layer. However, known omissions and regional assumptions sections acknowledge that accessibility, child protection, learner consent, grading authority, retention rules and credential authority vary by jurisdiction and provider. Known omissions explicitly state 'education-sector, pedagogy, accessibility, learner-rights, analytics, regional and legal review is required before canonical promotion.' Accept acknowledgment; defer full scope pending education-sector review, accessibility conformance audit, child-protection governance mapping, and jurisdiction-specific policy coverage (FERPA, GDPR, UK Records Act, national learner-rights, retention and credential-authority rules)." }, { "concept": "Single-provider waiver: absence of independent Claude and Grok review", "disposition": "Required: publication hold must remain active and visible", "rationale": "Provider policy requires a separate no-tools adversarial audit and a visible absence-of-external-review hold. For WM-ACT-038, Claude Sonnet and Grok 4.6 each timed out on exactly one bounded 120-second attempt. No external result was admitted. This audit is the mandated no-tools review. The internally valid result may be published as a reviewable draft, but it must retain a visible hold pending independent review or explicit owner authorization for canonical promotion." } ], "publicationHolds": [ "Codex single-provider fallback research: Claude Sonnet and Grok 4.6 each timed out on their one bounded 120-second attempt for WM-ACT-038. No external provider result was admitted. The source-grounded Codex fallback passed local schema validation and the required separate no-tools adversarial audit. The result remains reviewable-draft pending independent review or explicit owner authorization for canonical promotion, and this hold must remain visible.", "Specification-version verification required before final promotion: Edu-API is Candidate Final Public (not released); Common Cartridge 1.4 is Candidate Final. Accept for draft and peer review; final release requires conformance to final-version standards or explicit specification-level hold declaration in publication artifacts.", "Schema-level enforcement of inference safeguards deferred: policy forbids collapsing login into attendance, activity into learning, score into mastery, completion into credit. Data model currently lacks technical constraints (required evidence-method fields, confidence markers, forbidden-inference rules). Publication hold pending schema-level additions that make these distinctions machine-auditable and prevent silent consumer collapse.", "Interoperability round-trip not proven: mappings among ISCED, ELM, Edu-API, OneRoster, Caliper, CASE, QTI, xAPI, CLR and CourseInstance are listed as intentional but proposed relations or mapping versions remain held for review. No working mapping tables, version-pair conflict rules or bidirectional validation were supplied. Hold pending approved mapping specifications with identified omissions and conflict resolution.", "Regional legal and accessibility variance requires education-sector specialist review: model explicitly acknowledges jurisdiction variation (FERPA, GDPR, UK Records Act, national retention, consent, learner-rights, child protection, intellectual property, credential authority) and regional context assumptions (K-12 vs. higher-education vs. vocational vs. workplace vs. community vs. informal). Known omissions state this review is required before canonical promotion. Hold pending education-sector audit, accessibility conformance assessment, child-protection governance mapping and jurisdiction-specific policy coverage.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Interoperability proof-of-work: develop and approve working test mappings among ISCED, ELM, Edu-API, OneRoster, Caliper, CASE, QTI, xAPI, CLR and CourseInstance with explicitly identified omissions, semantic conflicts and round-trip limits. Include version-pair specific conflict-resolution rules and formal approved mapping tables for each relevant standard pair to move from intentional coverage to validated interoperability.", "Schema-level inference-safeguard enforcement: augment data model with required evidence-method enum fields, confidence and source-authority markers, and forbidden-rule validators to prevent silent collapse of login-into-attendance, activity-into-learning, score-into-mastery and completion-into-qualification. Add machine-auditable schema constraints and implement validation rules at model level.", "Regional legal and accessibility audit: conduct formal cross-context review spanning K-12, higher-education, vocational, workplace, professional, community and informal learning contexts. Map jurisdiction-specific requirements (FERPA, GDPR, UK Records Act, COPPA, VCAA, regional learner-rights), disability-access conformance (WCAG 2.2 implementation profile by context), child-protection policy, intellectual-property attribution rules and credential-authority delegation governance. Document context-specific profile invariants and version the model accordingly.", "Composition-relation artifact schema design: define explicit reference types for person-reference, learner-reference, organization-reference, programme-reference, course-definition-reference, activity-reference, competency-reference, session-reference, location-reference, resource-reference, tool-reference, enrollment-reference, assessment-reference and credential-reference to enforce external-master boundaries at schema level and prevent accidental ownership collapse.", "Delivery-form profile invariants: formal cohort courses, self-paced offerings, workplace training, community learning and informal single-activity sessions require different governance rules, completion criteria, assessment authority, credential eligibility and learner-rights protections. Currently a single slash name and mandatory profile attempt to cover all forms. Document mandatory profile variations and develop context-specific schemas or version controls for each delivery form." ] }, "statistics": { "sources": 16, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }