{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-act-035","code":"wm-act-035-test-execution","url":"https://ver.cy/models/wm-act-035-test-execution/","name":"Test Execution","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Activities and processes","entryKind":"event","plane":"","domain":["ACT.TST"],"industry":["Cross-industry"],"navPath":"NAV.ACT.TST","tags":["test","execution","act.tst"],"facets":{}},"whatItIs":"Owns execution identity and lineage, source-qualified classification, immutable bindings to test definition, criterion, expected result and oracle, run-specific subject and configuration snapshots, inputs and samples, environment, equipment and tools, actor and automation assignments, authorization and safety envelope, lifecycle and step events, source observations, evidence pointers, comparison and verdict assertions, anomalies, rerun and review lineage, projections, access and retention. Test case, requirement, subject, product, configuration, sample, environment, resource, instrument, dataset, observation, artifact, defect, incident, risk, assessment, verification or validation claim and generic audit masters remain external.","purpose":"Represent one attributable occurrence of running a versioned test procedure against identified subjects in a declared context, producing preserved observations, evidence and bounded result assertions.","scope":{"in":["Execution identity, attempt and lineage, procedure and criterion revisions, expected results, oracle, subject configuration, inputs, environment, tools, resources, actors and authority","Lifecycle and step occurrences, deviations, observations, measurements, evidence, comparisons, outcomes, verdicts, confidence, anomalies and external issue links","Rerun, reproducibility, review, invalidation, correction, supersession, interoperability, access, retention and safe agent operations"],"out":["Test case, requirement, subject, product, configuration, sample, environment, instrument, dataset, observation, artifact, defect, incident, risk, assessment, verification or validation claim or audit-log master lifecycle","Treating completion as pass, pass as compliance, failure as a defect, one run as reproducibility, or a rerun as a mutable revision of the first execution","Implementing a test runner, laboratory information system, observability backend, issue tracker, certification scheme or universal legal compliance and claiming full ISO conformance from public abstracts"],"boundaries":[{"neighbor":"Test Case / Procedure / Requirement / Criterion","distinction":"Reusable intent and acceptance logic are external versioned definitions. The execution binds the exact revision and records what actually occurred."},{"neighbor":"Subject / Sample / Environment / Instrument","distinction":"The execution owns source-qualified snapshots and usage assertions while external masters keep identity, lifecycle and authority."},{"neighbor":"Observation / Measurement / Evidence Artifact","distinction":"The execution organizes run-scoped observations and pointers, but source observation and artifact masters retain method, integrity and custody provenance."},{"neighbor":"Assessment / Verification / Validation / Certification","distinction":"A test execution may supply evidence to a broader assessment or assurance claim. Its bounded verdict does not itself establish system compliance, fitness or certification."},{"neighbor":"Defect / Incident / Risk / Nonconformity","distinction":"A failed or anomalous run can link to external issue masters through source-qualified correlation or causality assertions; it does not create or control them automatically."}]},"distinguishingFeatures":["Models one run of a test under frozen conditions, not the reusable test case or procedure.","Keeps expected result, observed result, comparison and verdict as separate assertions.","Snapshots subject, configuration, environment and equipment as they were at run time.","Links defects and nonconformities without owning them."],"structure":{"bundles":[{"id":"execution-identity-definition-and-procedure","name":"Execution identity, definition and procedure","description":"Defines the event root and binds it to reusable test intent without copying the test specification.","layers":[{"id":"execution-definition-identity-and-lineage","name":"Execution definition, identity and lineage","description":"Pins the event boundary, source profile, identity and attempt lineage.","findings":[{"id":"test-execution-definition-profile-classification-and-neighbor-boundary","name":"Test execution definition, profile, classification and neighbor boundary","description":"Source-qualified execution type, domain profile, inclusion and exclusion rules, and distinctions from test case, assessment, experiment, inspection, monitoring and verification claim.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define test execution definition, profile, classification and neighbor boundary?","id":"test-execution-definition-profile-classification-and-neighbor-boundary-q01","kind":"classification"},{"text":"Which authority, source, method, evidence, event time and knowledge time support test execution definition, profile, classification and neighbor boundary?","id":"test-execution-definition-profile-classification-and-neighbor-boundary-q02","kind":"provenance"},{"text":"How is test execution definition, profile, classification and neighbor boundary validated, accessed, changed, contested, corrected and retained?","id":"test-execution-definition-profile-classification-and-neighbor-boundary-q03","kind":"validation"}]},{"id":"execution-identifier-name-attempt-version-source-predecessor-rerun-and-lineage","name":"Execution identifier, name, attempt, version, source, predecessor, rerun and lineage","description":"Stable execution identity, source run ID, attempt number, schema and profile version, prior execution link, rerun reason and correction or supersession lineage.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define execution identifier, name, attempt, version, source, predecessor, rerun and lineage?","id":"execution-identifier-name-attempt-version-source-predecessor-rerun-and-lineage-q01","kind":"identity"},{"text":"Which authority, source, method, evidence, event time and knowledge time support execution identifier, name, attempt, version, source, predecessor, rerun and lineage?","id":"execution-identifier-name-attempt-version-source-predecessor-rerun-and-lineage-q02","kind":"provenance"},{"text":"How is execution identifier, name, attempt, version, source, predecessor, rerun and lineage validated, accessed, changed, contested, corrected and retained?","id":"execution-identifier-name-attempt-version-source-predecessor-rerun-and-lineage-q03","kind":"validation"}]}]},{"id":"test-definition-criterion-procedure-expectation-and-oracle","name":"Test definition, criterion, procedure, expectation and oracle","description":"Binds the occurrence to the exact reusable definitions used at run time.","findings":[{"id":"test-case-procedure-method-revision-step-plan-parameter-and-applicability-binding","name":"Test case, procedure, method, revision, step plan, parameter and applicability binding","description":"External test definition and procedure IDs, immutable revision or digest, method, ordered planned steps, parameters, applicability and permitted variation.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define test case, procedure, method, revision, step plan, parameter and applicability binding?","id":"test-case-procedure-method-revision-step-plan-parameter-and-applicability-binding-q01","kind":"requirement"},{"text":"Which authority, source, method, evidence, event time and knowledge time support test case, procedure, method, revision, step plan, parameter and applicability binding?","id":"test-case-procedure-method-revision-step-plan-parameter-and-applicability-binding-q02","kind":"provenance"},{"text":"How is test case, procedure, method, revision, step plan, parameter and applicability binding validated, accessed, changed, contested, corrected and retained?","id":"test-case-procedure-method-revision-step-plan-parameter-and-applicability-binding-q03","kind":"validation"}]},{"id":"requirement-criterion-expected-result-acceptance-rule-tolerance-and-oracle","name":"Requirement, criterion, expected result, acceptance rule, tolerance and oracle","description":"External requirement and test criterion, expected value or behavior, acceptance rule, tolerance, oracle type, comparator revision and ambiguity handling.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define requirement, criterion, expected result, acceptance rule, tolerance and oracle?","id":"requirement-criterion-expected-result-acceptance-rule-tolerance-and-oracle-q01","kind":"requirement"},{"text":"Which authority, source, method, evidence, event time and knowledge time support requirement, criterion, expected result, acceptance rule, tolerance and oracle?","id":"requirement-criterion-expected-result-acceptance-rule-tolerance-and-oracle-q02","kind":"provenance"},{"text":"How is requirement, criterion, expected result, acceptance rule, tolerance and oracle validated, accessed, changed, contested, corrected and retained?","id":"requirement-criterion-expected-result-acceptance-rule-tolerance-and-oracle-q03","kind":"validation"}]}]}]},{"id":"subject-configuration-environment-and-resources","name":"Subject, configuration, environment and resources","description":"Freezes what was tested and the conditions and means of the run.","layers":[{"id":"subject-sample-input-and-configuration","name":"Subject, sample, input and configuration","description":"Identifies the tested thing and its run-specific state without taking ownership of the subject master.","findings":[{"id":"subject-identity-type-version-build-pedigree-configuration-state-and-scope","name":"Subject identity, type, version, build, pedigree, configuration, state and scope","description":"External subject ID and type, version or build, provenance or test-article pedigree, frozen configuration, initial state, tested boundary and excluded portions.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define subject identity, type, version, build, pedigree, configuration, state and scope?","id":"subject-identity-type-version-build-pedigree-configuration-state-and-scope-q01","kind":"identity"},{"text":"Which authority, source, method, evidence, event time and knowledge time support subject identity, type, version, build, pedigree, configuration, state and scope?","id":"subject-identity-type-version-build-pedigree-configuration-state-and-scope-q02","kind":"provenance"},{"text":"How is subject identity, type, version, build, pedigree, configuration, state and scope validated, accessed, changed, contested, corrected and retained?","id":"subject-identity-type-version-build-pedigree-configuration-state-and-scope-q03","kind":"validation"}]},{"id":"sample-specimen-dataset-input-fixture-precondition-and-chain-of-custody","name":"Sample, specimen, dataset, input, fixture, precondition and chain of custody","description":"External sample or dataset identity, selection and preparation, fixture input, preconditions, custody, integrity, representativeness and consumption state.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define sample, specimen, dataset, input, fixture, precondition and chain of custody?","id":"sample-specimen-dataset-input-fixture-precondition-and-chain-of-custody-q01","kind":"evidence"},{"text":"Which authority, source, method, evidence, event time and knowledge time support sample, specimen, dataset, input, fixture, precondition and chain of custody?","id":"sample-specimen-dataset-input-fixture-precondition-and-chain-of-custody-q02","kind":"provenance"},{"text":"How is sample, specimen, dataset, input, fixture, precondition and chain of custody validated, accessed, changed, contested, corrected and retained?","id":"sample-specimen-dataset-input-fixture-precondition-and-chain-of-custody-q03","kind":"validation"}]}]},{"id":"environment-equipment-instruments-and-dependencies","name":"Environment, equipment, instruments and dependencies","description":"Records execution conditions and the resources capable of influencing results.","findings":[{"id":"environment-location-time-platform-network-ambient-condition-and-dependency-snapshot","name":"Environment, location, time, platform, network, ambient condition and dependency snapshot","description":"Physical or virtual location, environment profile, platform, operating system, network, dependencies, ambient conditions, clock basis and run-time snapshots.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define environment, location, time, platform, network, ambient condition and dependency snapshot?","id":"environment-location-time-platform-network-ambient-condition-and-dependency-snapshot-q01","kind":"spatial"},{"text":"Which authority, source, method, evidence, event time and knowledge time support environment, location, time, platform, network, ambient condition and dependency snapshot?","id":"environment-location-time-platform-network-ambient-condition-and-dependency-snapshot-q02","kind":"provenance"},{"text":"How is environment, location, time, platform, network, ambient condition and dependency snapshot validated, accessed, changed, contested, corrected and retained?","id":"environment-location-time-platform-network-ambient-condition-and-dependency-snapshot-q03","kind":"validation"}]},{"id":"equipment-instrument-tool-version-calibration-reference-material-and-fixture","name":"Equipment, instrument, tool, version, calibration, reference material and fixture","description":"External resource IDs, tool versions, calibration or validation status, reference materials, fixtures, uncertainty contribution, suitability and availability.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define equipment, instrument, tool, version, calibration, reference material and fixture?","id":"equipment-instrument-tool-version-calibration-reference-material-and-fixture-q01","kind":"measurement"},{"text":"Which authority, source, method, evidence, event time and knowledge time support equipment, instrument, tool, version, calibration, reference material and fixture?","id":"equipment-instrument-tool-version-calibration-reference-material-and-fixture-q02","kind":"provenance"},{"text":"How is equipment, instrument, tool, version, calibration, reference material and fixture validated, accessed, changed, contested, corrected and retained?","id":"equipment-instrument-tool-version-calibration-reference-material-and-fixture-q03","kind":"validation"}]}]}]},{"id":"authorization-conduct-steps-and-timing","name":"Authorization, conduct, steps and timing","description":"Records who or what performed the run, under which authority, and what actually occurred.","layers":[{"id":"roles-authorization-mode-and-safety","name":"Roles, authorization, mode and safety","description":"Makes responsibility, automation and guardrails explicit.","findings":[{"id":"executor-observer-owner-reviewer-agent-delegation-authorization-and-segregation","name":"Executor, observer, owner, reviewer, agent, delegation, authorization and segregation","description":"External actors or agents, run roles, delegated authority, competence assertion, approval boundaries, independence and segregation of duties.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define executor, observer, owner, reviewer, agent, delegation, authorization and segregation?","id":"executor-observer-owner-reviewer-agent-delegation-authorization-and-segregation-q01","kind":"authority"},{"text":"Which authority, source, method, evidence, event time and knowledge time support executor, observer, owner, reviewer, agent, delegation, authorization and segregation?","id":"executor-observer-owner-reviewer-agent-delegation-authorization-and-segregation-q02","kind":"provenance"},{"text":"How is executor, observer, owner, reviewer, agent, delegation, authorization and segregation validated, accessed, changed, contested, corrected and retained?","id":"executor-observer-owner-reviewer-agent-delegation-authorization-and-segregation-q03","kind":"validation"}]},{"id":"manual-automatic-semiautomatic-mode-tool-control-safety-privacy-and-stop-rule","name":"Manual, automatic, semiautomatic mode, tool control, safety, privacy and stop rule","description":"Execution mode, automation tool and controller, human intervention points, safety envelope, privacy constraints, abort triggers and emergency authority.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define manual, automatic, semiautomatic mode, tool control, safety, privacy and stop rule?","id":"manual-automatic-semiautomatic-mode-tool-control-safety-privacy-and-stop-rule-q01","kind":"constraint"},{"text":"Which authority, source, method, evidence, event time and knowledge time support manual, automatic, semiautomatic mode, tool control, safety, privacy and stop rule?","id":"manual-automatic-semiautomatic-mode-tool-control-safety-privacy-and-stop-rule-q02","kind":"provenance"},{"text":"How is manual, automatic, semiautomatic mode, tool control, safety, privacy and stop rule validated, accessed, changed, contested, corrected and retained?","id":"manual-automatic-semiautomatic-mode-tool-control-safety-privacy-and-stop-rule-q03","kind":"validation"}]}]},{"id":"execution-lifecycle-step-occurrences-and-deviations","name":"Execution lifecycle, step occurrences and deviations","description":"Captures the append-only event history and actual ordered conduct.","findings":[{"id":"plan-prepare-start-pause-resume-block-abort-complete-time-and-state-event","name":"Plan, prepare, start, pause, resume, block, abort, complete, time and state event","description":"Typed lifecycle event, prior and next state, actor or agent, authority, rationale, event time with seconds and offset, observed time and evidence.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define plan, prepare, start, pause, resume, block, abort, complete, time and state event?","id":"plan-prepare-start-pause-resume-block-abort-complete-time-and-state-event-q01","kind":"lifecycle"},{"text":"Which authority, source, method, evidence, event time and knowledge time support plan, prepare, start, pause, resume, block, abort, complete, time and state event?","id":"plan-prepare-start-pause-resume-block-abort-complete-time-and-state-event-q02","kind":"provenance"},{"text":"How is plan, prepare, start, pause, resume, block, abort, complete, time and state event validated, accessed, changed, contested, corrected and retained?","id":"plan-prepare-start-pause-resume-block-abort-complete-time-and-state-event-q03","kind":"validation"}]},{"id":"step-occurrence-sequence-input-action-output-duration-log-message-deviation-and-recovery","name":"Step occurrence, sequence, input, action, output, duration, log, message, deviation and recovery","description":"Actual step ID, planned-step link, order and concurrency, inputs, action, outputs, timestamps, messages, deviation, recovery and continuation decision.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define step occurrence, sequence, input, action, output, duration, log, message, deviation and recovery?","id":"step-occurrence-sequence-input-action-output-duration-log-message-deviation-and-recovery-q01","kind":"lifecycle"},{"text":"Which authority, source, method, evidence, event time and knowledge time support step occurrence, sequence, input, action, output, duration, log, message, deviation and recovery?","id":"step-occurrence-sequence-input-action-output-duration-log-message-deviation-and-recovery-q02","kind":"provenance"},{"text":"How is step occurrence, sequence, input, action, output, duration, log, message, deviation and recovery validated, accessed, changed, contested, corrected and retained?","id":"step-occurrence-sequence-input-action-output-duration-log-message-deviation-and-recovery-q03","kind":"validation"}]}]}]},{"id":"observations-measurements-evidence-and-results","name":"Observations, measurements, evidence and results","description":"Separates raw observation from interpretation, verdict and broader assurance claim.","layers":[{"id":"observations-measurements-and-evidence","name":"Observations, measurements and evidence","description":"Preserves source observations and evidence before conclusion.","findings":[{"id":"observation-property-value-unit-scale-time-location-method-quality-and-uncertainty","name":"Observation, property, value, unit, scale, time, location, method, quality and uncertainty","description":"Observed property, value or category, unit and scale, phenomenon and result time, location, procedure, sensor or observer, quality flag, detection limit and uncertainty.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define observation, property, value, unit, scale, time, location, method, quality and uncertainty?","id":"observation-property-value-unit-scale-time-location-method-quality-and-uncertainty-q01","kind":"measurement"},{"text":"Which authority, source, method, evidence, event time and knowledge time support observation, property, value, unit, scale, time, location, method, quality and uncertainty?","id":"observation-property-value-unit-scale-time-location-method-quality-and-uncertainty-q02","kind":"provenance"},{"text":"How is observation, property, value, unit, scale, time, location, method, quality and uncertainty validated, accessed, changed, contested, corrected and retained?","id":"observation-property-value-unit-scale-time-location-method-quality-and-uncertainty-q03","kind":"validation"}]},{"id":"evidence-artifact-pointer-log-trace-image-record-integrity-digest-and-custody","name":"Evidence artifact, pointer, log, trace, image, record, integrity, digest and custody","description":"External artifact identity, relevant pointer, media type, capture event, generating tool or agent, digest, signature, storage, access marking and custody lineage.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define evidence artifact, pointer, log, trace, image, record, integrity, digest and custody?","id":"evidence-artifact-pointer-log-trace-image-record-integrity-digest-and-custody-q01","kind":"evidence"},{"text":"Which authority, source, method, evidence, event time and knowledge time support evidence artifact, pointer, log, trace, image, record, integrity, digest and custody?","id":"evidence-artifact-pointer-log-trace-image-record-integrity-digest-and-custody-q02","kind":"provenance"},{"text":"How is evidence artifact, pointer, log, trace, image, record, integrity, digest and custody validated, accessed, changed, contested, corrected and retained?","id":"evidence-artifact-pointer-log-trace-image-record-integrity-digest-and-custody-q03","kind":"validation"}]}]},{"id":"comparison-verdict-confidence-and-review","name":"Comparison, verdict, confidence and review","description":"Builds bounded result assertions without converting them into unearned compliance claims.","findings":[{"id":"expected-actual-comparator-difference-tolerance-outcome-verdict-and-rationale","name":"Expected, actual, comparator, difference, tolerance, outcome, verdict and rationale","description":"Expected and actual references, comparator and version, difference, tolerance evaluation, outcome vocabulary, verdict issuer, rationale and affected scope.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define expected, actual, comparator, difference, tolerance, outcome, verdict and rationale?","id":"expected-actual-comparator-difference-tolerance-outcome-verdict-and-rationale-q01","kind":"validation"},{"text":"Which authority, source, method, evidence, event time and knowledge time support expected, actual, comparator, difference, tolerance, outcome, verdict and rationale?","id":"expected-actual-comparator-difference-tolerance-outcome-verdict-and-rationale-q02","kind":"provenance"},{"text":"How is expected, actual, comparator, difference, tolerance, outcome, verdict and rationale validated, accessed, changed, contested, corrected and retained?","id":"expected-actual-comparator-difference-tolerance-outcome-verdict-and-rationale-q03","kind":"validation"}]},{"id":"validity-confidence-coverage-review-attestation-signoff-and-compliance-boundary","name":"Validity, confidence, coverage, review, attestation, signoff and compliance boundary","description":"Run validity, confidence, coverage and limitations, reviewer and attestation, signoff authority, disputes and explicit separation from system-level compliance or certification.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define validity, confidence, coverage, review, attestation, signoff and compliance boundary?","id":"validity-confidence-coverage-review-attestation-signoff-and-compliance-boundary-q01","kind":"validation"},{"text":"Which authority, source, method, evidence, event time and knowledge time support validity, confidence, coverage, review, attestation, signoff and compliance boundary?","id":"validity-confidence-coverage-review-attestation-signoff-and-compliance-boundary-q02","kind":"provenance"},{"text":"How is validity, confidence, coverage, review, attestation, signoff and compliance boundary validated, accessed, changed, contested, corrected and retained?","id":"validity-confidence-coverage-review-attestation-signoff-and-compliance-boundary-q03","kind":"validation"}]}]}]},{"id":"anomalies-reruns-review-and-lifecycle","name":"Anomalies, reruns, review and lifecycle","description":"Preserves failed and inconclusive evidence while linking external issue masters and later attempts.","layers":[{"id":"anomaly-failure-incident-defect-and-impact-links","name":"Anomaly, failure, incident, defect and impact links","description":"Records run-local symptoms and source-qualified links to separately governed issue records.","findings":[{"id":"anomaly-failure-error-timeout-inconclusive-blocked-symptom-and-triage","name":"Anomaly, failure, error, timeout, inconclusive, blocked, symptom and triage","description":"Observed anomaly or symptom, failure mode, error and timeout, inconclusive or blocked reason, affected step or subject scope, severity hypothesis and triage state.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define anomaly, failure, error, timeout, inconclusive, blocked, symptom and triage?","id":"anomaly-failure-error-timeout-inconclusive-blocked-symptom-and-triage-q01","kind":"evidence"},{"text":"Which authority, source, method, evidence, event time and knowledge time support anomaly, failure, error, timeout, inconclusive, blocked, symptom and triage?","id":"anomaly-failure-error-timeout-inconclusive-blocked-symptom-and-triage-q02","kind":"provenance"},{"text":"How is anomaly, failure, error, timeout, inconclusive, blocked, symptom and triage validated, accessed, changed, contested, corrected and retained?","id":"anomaly-failure-error-timeout-inconclusive-blocked-symptom-and-triage-q03","kind":"validation"}]},{"id":"defect-incident-risk-nonconformity-link-correlation-causality-status-and-owner","name":"Defect, incident, risk, nonconformity link, correlation, causality, status and owner","description":"External issue IDs, typed relation, correlation evidence, unconfirmed or confirmed causality, source status, owner, disposition and no-cascade rule.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define defect, incident, risk, nonconformity link, correlation, causality, status and owner?","id":"defect-incident-risk-nonconformity-link-correlation-causality-status-and-owner-q01","kind":"relationship"},{"text":"Which authority, source, method, evidence, event time and knowledge time support defect, incident, risk, nonconformity link, correlation, causality, status and owner?","id":"defect-incident-risk-nonconformity-link-correlation-causality-status-and-owner-q02","kind":"provenance"},{"text":"How is defect, incident, risk, nonconformity link, correlation, causality, status and owner validated, accessed, changed, contested, corrected and retained?","id":"defect-incident-risk-nonconformity-link-correlation-causality-status-and-owner-q03","kind":"validation"}]}]},{"id":"rerun-reproducibility-review-correction-and-supersession","name":"Rerun, reproducibility, review, correction and supersession","description":"Relates attempts and protects released evidence from silent mutation.","findings":[{"id":"retry-rerun-repeat-reproduction-replication-delta-and-comparability","name":"Retry, rerun, repeat, reproduction, replication, delta and comparability","description":"New execution ID, predecessor link, reason, controlled and changed factors, procedure and subject equivalence, result delta and bounded reproducibility assessment.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define retry, rerun, repeat, reproduction, replication, delta and comparability?","id":"retry-rerun-repeat-reproduction-replication-delta-and-comparability-q01","kind":"lifecycle"},{"text":"Which authority, source, method, evidence, event time and knowledge time support retry, rerun, repeat, reproduction, replication, delta and comparability?","id":"retry-rerun-repeat-reproduction-replication-delta-and-comparability-q02","kind":"provenance"},{"text":"How is retry, rerun, repeat, reproduction, replication, delta and comparability validated, accessed, changed, contested, corrected and retained?","id":"retry-rerun-repeat-reproduction-replication-delta-and-comparability-q03","kind":"validation"}]},{"id":"review-dispute-invalidate-correct-amend-supersede-release-and-tombstone","name":"Review, dispute, invalidate, correct, amend, supersede, release and tombstone","description":"Review and dispute events, invalidation reason, correction successor, release state, supersession link, residual validity and minimum tombstone.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define review, dispute, invalidate, correct, amend, supersede, release and tombstone?","id":"review-dispute-invalidate-correct-amend-supersede-release-and-tombstone-q01","kind":"lifecycle"},{"text":"Which authority, source, method, evidence, event time and knowledge time support review, dispute, invalidate, correct, amend, supersede, release and tombstone?","id":"review-dispute-invalidate-correct-amend-supersede-release-and-tombstone-q02","kind":"provenance"},{"text":"How is review, dispute, invalidate, correct, amend, supersede, release and tombstone validated, accessed, changed, contested, corrected and retained?","id":"review-dispute-invalidate-correct-amend-supersede-release-and-tombstone-q03","kind":"validation"}]}]}]},{"id":"provenance-interoperability-access-retention-and-agent-operation","name":"Provenance, interoperability, access, retention and agent operation","description":"Supports attributable exchange and safe management of sensitive test evidence.","layers":[{"id":"source-provenance-and-interoperability","name":"Source, provenance and interoperability","description":"Keeps origin and semantic loss visible across projections.","findings":[{"id":"source-assertion-agent-activity-plan-usage-generation-revision-invalidation-and-contradiction","name":"Source assertion, agent, activity, plan, usage, generation, revision, invalidation and contradiction","description":"Assertion identity and source, responsible agent, execution activity and plan, used and generated entities, revision, invalidation, confidence and supporting or contradicting claims.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define source assertion, agent, activity, plan, usage, generation, revision, invalidation and contradiction?","id":"source-assertion-agent-activity-plan-usage-generation-revision-invalidation-and-contradiction-q01","kind":"provenance"},{"text":"Which authority, source, method, evidence, event time and knowledge time support source assertion, agent, activity, plan, usage, generation, revision, invalidation and contradiction?","id":"source-assertion-agent-activity-plan-usage-generation-revision-invalidation-and-contradiction-q02","kind":"provenance"},{"text":"How is source assertion, agent, activity, plan, usage, generation, revision, invalidation and contradiction validated, accessed, changed, contested, corrected and retained?","id":"source-assertion-agent-activity-plan-usage-generation-revision-invalidation-and-contradiction-q03","kind":"validation"}]},{"id":"earl-oscal-oms-prov-robot-opentelemetry-and-domain-crosswalk","name":"EARL, OSCAL, OMS, PROV, Robot, OpenTelemetry and domain crosswalk","description":"Pinned source and target versions, identity, subject, criterion, action, observation, evidence, status and result mappings, omissions, semantic conflicts and round-trip classification.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define earl, oscal, oms, prov, robot, opentelemetry and domain crosswalk?","id":"earl-oscal-oms-prov-robot-opentelemetry-and-domain-crosswalk-q01","kind":"interoperability"},{"text":"Which authority, source, method, evidence, event time and knowledge time support earl, oscal, oms, prov, robot, opentelemetry and domain crosswalk?","id":"earl-oscal-oms-prov-robot-opentelemetry-and-domain-crosswalk-q02","kind":"provenance"},{"text":"How is earl, oscal, oms, prov, robot, opentelemetry and domain crosswalk validated, accessed, changed, contested, corrected and retained?","id":"earl-oscal-oms-prov-robot-opentelemetry-and-domain-crosswalk-q03","kind":"validation"}]}]},{"id":"access-privacy-retention-and-safe-automation","name":"Access, privacy, retention and safe automation","description":"Controls reading, execution, correction and disposition for humans and agents.","findings":[{"id":"role-view-purpose-access-disclosure-redaction-exception-and-audit","name":"Role view, purpose, access, disclosure, redaction, exception and audit","description":"Purpose-bound role views, field-redacted projections, disclosure rules, exception authority, expiry and tamper-evident access events.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define role view, purpose, access, disclosure, redaction, exception and audit?","id":"role-view-purpose-access-disclosure-redaction-exception-and-audit-q01","kind":"access"},{"text":"Which authority, source, method, evidence, event time and knowledge time support role view, purpose, access, disclosure, redaction, exception and audit?","id":"role-view-purpose-access-disclosure-redaction-exception-and-audit-q02","kind":"provenance"},{"text":"How is role view, purpose, access, disclosure, redaction, exception and audit validated, accessed, changed, contested, corrected and retained?","id":"role-view-purpose-access-disclosure-redaction-exception-and-audit-q03","kind":"validation"}]},{"id":"retention-trigger-legal-hold-disposition-tombstone-agent-authority-idempotency-and-post-check","name":"Retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check","description":"Retention class and trigger, hold, deletion eligibility, tombstone, delegated agent scope, preconditions, dry run, idempotency key, expected revision and post-check.","questions":[{"text":"What identities, types, roles, scope, versions and explicit values define retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check?","id":"retention-trigger-legal-hold-disposition-tombstone-agent-authority-idempotency-and-post-check-q01","kind":"retention"},{"text":"Which authority, source, method, evidence, event time and knowledge time support retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check?","id":"retention-trigger-legal-hold-disposition-tombstone-agent-authority-idempotency-and-post-check-q02","kind":"provenance"},{"text":"How is retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check validated, accessed, changed, contested, corrected and retained?","id":"retention-trigger-legal-hold-disposition-tombstone-agent-authority-idempotency-and-post-check-q03","kind":"validation"}]}]}]}]},"agentConduct":{"may":["Execute automated steps and log them with timestamps.","Capture observations and raw evidence artifacts.","Compare observations with the oracle and propose a verdict.","Rerun an execution as a new record with lineage."],"mustNot":["Change a recorded result or evidence after the run.","Report a pass when steps were skipped or the environment was not qualified.","Use uncalibrated or out-of-date equipment without recording it.","Turn a single execution verdict into a certification or compliance claim.","Run tests on production systems or people without authorisation."],"requiresHuman":["Invalidating an execution or waiving a failed criterion.","Accepting results used for certification or safety release."]},"ethics":{"considerations":["Falsified or careless test results can put unsafe products in people's hands.","Tests involving people or animals need ethical approval and consent.","Testers must be free to report failures without pressure."],"affectedParties":["End users of the tested product","Test personnel","Certification bodies and regulators"]},"owners":{"steward":"Dimension identity, owner, testing authority, quality, safety, privacy and records stewards","roles":[{"name":"Test owner or accountable authority","responsibilities":["Own execution purpose, authorization, acceptance boundaries and accountable disposition."]},{"name":"Test designer or procedure steward","responsibilities":["Own reusable case, method, criteria, expected results, oracle and permitted variation."]},{"name":"Executor or automation operator","responsibilities":["Perform authorized steps, record deviations and protect source evidence."]},{"name":"Subject, sample or configuration custodian","responsibilities":["Own subject identity, pedigree, configuration, sample handling and custody assertions."]},{"name":"Environment, equipment and metrology steward","responsibilities":["Own condition, tool, instrument, calibration, reference-material and uncertainty evidence."]},{"name":"Reviewer or assurance authority","responsibilities":["Review validity, independence, evidence sufficiency, verdict scope and signoff without rewriting the run."]},{"name":"Data, privacy, safety and records steward","responsibilities":["Control protected views, safe execution, retention, holds, disposition and auditability."]}],"masterSystems":[]},"relations":[{"target":"Test Case, Test Procedure, Requirement, Criterion and Oracle models","type":"references","note":"Resolve immutable test intent and acceptance logic while keeping the execution occurrence separate."},{"target":"Subject, Product, Configuration, Sample, Dataset, Environment, Resource and Instrument models","type":"references","note":"Bind run-specific snapshots and usage without copying external master lifecycles."},{"target":"Observation, Measurement, Artifact, Defect, Incident, Risk, Assessment and Audit models","type":"references","note":"Link source evidence, issues and broader assurance records while preserving source identity and authority."},{"target":"EARL 1.0 and OSCAL Assessment Results 1.2.0","type":"aligned","note":"Project assertions, subjects, criteria, results, actions, observations, evidence and findings with explicit non-equivalence and loss rules."},{"target":"OGC OMS, W3C PROV-O, Robot Framework 7.4.2 and OpenTelemetry Semantic Conventions 1.44.0","type":"aligned","note":"Project observations, provenance, software-run artifacts and telemetry status through version-pinned profiles with declared semantic loss."},{"target":"Test Case / Procedure / Requirement / Criterion","type":"neighbor","note":"Reusable intent and acceptance logic are external versioned definitions. The execution binds the exact revision and records what actually occurred."},{"target":"Subject / Sample / Environment / Instrument","type":"neighbor","note":"The execution owns source-qualified snapshots and usage assertions while external masters keep identity, lifecycle and authority."},{"target":"Observation / Measurement / Evidence Artifact","type":"neighbor","note":"The execution organizes run-scoped observations and pointers, but source observation and artifact masters retain method, integrity and custody provenance."},{"target":"Assessment / Verification / Validation / Certification","type":"neighbor","note":"A test execution may supply evidence to a broader assessment or assurance claim. Its bounded verdict does not itself establish system compliance, fitness or certification."},{"target":"Defect / Incident / Risk / Nonconformity","type":"neighbor","note":"A failed or anomalous run can link to external issue masters through source-qualified correlation or causality assertions; it does not create or control them automatically."},{"target":"WM-ACT-034","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system test-management or laboratory execution identifier qualified by source and execution class.","Governed globally resolvable execution IRI under a controlled namespace.","Dimension UUID when no authoritative or governed global identifier exists."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A test execution has a test case reference, a subject version, an environment, a timestamp, an executor and a verdict.","It is confused with the test case, a test plan, a defect or a certification."]},"capabilities":{"applicability":"required","items":["Register test execution: Create a stable event identity and classify the source and domain profile.","Bind procedure, criteria and oracles: Freeze the exact definitions against which the run is conducted and interpreted.","Freeze subject, input and environment: Record the tested subject, configuration, inputs and influential conditions.","Qualify resources and authorization: Bind actors, automation, instruments, delegated authority and safety controls.","Execute and log steps: Append actual lifecycle and step occurrences without rewriting the plan.","Capture observations and evidence: Record raw observations, measurements and integrity-protected artifacts before verdict.","Evaluate and assert results: Compare observed and expected states through a pinned oracle and issue bounded verdicts.","Link anomalies and external issues: Connect run-local symptoms to separately governed defects, incidents, risks or nonconformities.","Review, invalidate, correct and rerun: Preserve an immutable attempt while creating reviewed successors or new execution identities.","Project, disclose, retain and audit: Create governed crosswalk views and perform controlled information-lifecycle operations."]},"hazards":{"applicability":"required","items":["Unsafe release on false pass results.","Unrepeatable results when configuration was not frozen.","Damage to equipment or test subjects during destructive tests."]},"interfaces":{"applicability":"required","items":["JUnit XML report format.","Test Anything Protocol (TAP).","ISTQB terminology.","ISO 5725 accuracy of measurement methods and results."]},"context":{"applicability":"required","items":["Accreditation, admissibility, product compliance, clinical or research ethics, workplace safety, privacy, records and disclosure depend on jurisdiction and sector.","NASA guidance informs systems-engineering verification and validation but does not define a universal test execution lifecycle.","OSCAL is a security-assessment profile; EARL is rooted in accessibility and quality reporting; Robot and OpenTelemetry are software-oriented interoperability profiles."]}},"sources":[{"title":"ISO/IEC/IEEE 29119 series: Software and systems engineering, Software testing","url":"https://committee.iso.org/sites/jtc1sc7/home/projects/flagship-standards/isoiecieee-29119-series.html","note":"International Organization for Standardization"},{"title":"ISO/IEC/IEEE 29119-3:2021 Software testing, Part 3: Test documentation","url":"https://www.iso.org/standard/79429.html","note":"International Organization for Standardization"},{"title":"ISO/IEC 17025:2017 General requirements for the competence of testing and calibration laboratories","url":"https://www.iso.org/standard/66912.html","note":"International Organization for Standardization"},{"title":"Evaluation and Report Language (EARL) 1.0 Schema","url":"https://www.w3.org/TR/EARL10-Schema/","note":"World Wide Web Consortium"},{"title":"OSCAL Assessment Layer: Assessment Results Model","url":"https://pages.nist.gov/OSCAL/learn/concepts/layer/assessment/assessment-results/","note":"National Institute of Standards and Technology"},{"title":"OSCAL Assessment Results Model v1.2.0 XML Format Reference","url":"https://pages.nist.gov/OSCAL-Reference/models/v1.2.0/assessment-results/xml-reference/","note":"National Institute of Standards and Technology"},{"title":"Observations, Measurements, and Samples","url":"https://www.ogc.org/standards/om/","note":"Open Geospatial Consortium"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Robot Framework User Guide","url":"https://robotframework.org/robotframework/7.4.2/RobotFrameworkUserGuide.html","note":"Robot Framework Foundation"},{"title":"NASA Systems Engineering Handbook, Appendix I: Verification and Validation Plan Outline","url":"https://www.nasa.gov/reference/system-engineering-handbook-appendix/","note":"National Aeronautics and Space Administration"},{"title":"OpenTelemetry Test Attributes","url":"https://opentelemetry.io/docs/specs/semconv/registry/attributes/test/","note":"OpenTelemetry"},{"title":"NIST Privacy Framework","url":"https://www.nist.gov/privacy-framework","note":"National Institute of Standards and Technology"},{"title":"Disposing of records","url":"https://www.nationalarchives.gov.uk/information-management/manage-information/policy-process/disposal/","note":"The National Archives, United Kingdom"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"Internet Engineering Task Force"}],"openQuestions":["Full-text review of ISO/IEC/IEEE 29119-3:2021 and ISO/IEC 17025:2017 to bind normative test-execution requirements, competence scopes and domain-specific artifact and retention rules.","OpenTelemetry Semantic Conventions maturity and test-attribute expansion roadmap: current development-status test registry is narrower than Vercy cross-domain model; determine stability timeline and compatibility-breaking gates.","Sector-specific validation across accredited laboratories, software, security assessment, clinical research, manufacturing, aerospace and financial services, using newly verified primary standards for each profile rather than importing uncited requirements into this draft.","Relation registry rows for external masters: work with test-case steward, subject steward (product lifecycle, configuration management), observation steward (metrology, sensor calibration), evidence steward (artifact custody, integrity verification), issue steward (defect/incident/risk/nonconformity lifecycle), and assessment steward to define source-qualified binding semantics, approval gates, and cascade policies.","Governed agent operation and automation authority: define delegation scope, safety controls, preconditions, dry-run mode, idempotency keys, expected-revision checks, post-execution validation, and audit-event immutability for unattended test runners, continuous integration systems, and autonomous laboratory information systems in regulated environments.","Redundancy and conflict resolution: clarify Vercy semantics when a single physical test execution is independently reported in Robot Framework output, OSCAL assessment result, EARL accessibility report, OpenTelemetry spans, proprietary LMS export, and ISO/IEC 17025 test record. Define canonical vs. projection identity semantics and round-trip loss-acceptable boundaries.","No successful independent Claude or Grok result was available; laboratory, software, manufacturing, clinical, security, safety-critical, regional and legal review is required before canonical promotion.","Test Execution has no single universal cross-domain vocabulary. This package defines a shared occurrence kernel and requires profile-specific procedures, outcome vocabularies and authority rules.","No approved relation rows were supplied; the registry Assessment / Evaluation parent link and proposed test-definition, subject, observation, evidence, issue and audit relations remain holds.","The ISO/IEC/IEEE 29119-3 and ISO/IEC 17025 pages are public abstracts or summaries, not licensed clause text, so no ISO conformance claim is made.","OpenTelemetry test attributes are development status and currently much narrower than the Vercy cross-domain model.","Sector profiles need their own competence, accreditation, safety, ethics, custody, uncertainty, privacy, retention and signoff rules."],"resources":{"spec":"/models/wm-act-035-test-execution/spec.yaml","agents":"/models/wm-act-035-test-execution/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-035"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-act-035-test-execution/spec.yaml","ver-cy/world-models/card-supplements/wm-act-035-test-execution.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T06:37:07Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}