Published

Test Execution

vr.wm-act-035 · wm-act-035-test-execution

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.

World Models Activities and processes ACT.TST

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 24 findings · 72 questions

Execution identity, definition and procedure Defines the event root and binds it to reusable test intent without copying the test specification.

Execution definition, identity and lineage

Pins the event boundary, source profile, identity and attempt lineage.

Test execution definition, profile, classification and neighbor boundary

Source-qualified execution type, domain profile, inclusion and exclusion rules, and distinctions from test case, assessment, experiment, inspection, monitoring and verification claim.

What identities, types, roles, scope, versions and explicit values define test execution definition, profile, classification and neighbor boundary? classification
Which authority, source, method, evidence, event time and knowledge time support test execution definition, profile, classification and neighbor boundary? provenance
How is test execution definition, profile, classification and neighbor boundary validated, accessed, changed, contested, corrected and retained? validation

Execution identifier, name, attempt, version, source, predecessor, rerun and lineage

Stable execution identity, source run ID, attempt number, schema and profile version, prior execution link, rerun reason and correction or supersession lineage.

What identities, types, roles, scope, versions and explicit values define execution identifier, name, attempt, version, source, predecessor, rerun and lineage? identity
Which authority, source, method, evidence, event time and knowledge time support execution identifier, name, attempt, version, source, predecessor, rerun and lineage? provenance
How is execution identifier, name, attempt, version, source, predecessor, rerun and lineage validated, accessed, changed, contested, corrected and retained? validation

Test definition, criterion, procedure, expectation and oracle

Binds the occurrence to the exact reusable definitions used at run time.

Test case, procedure, method, revision, step plan, parameter and applicability binding

External test definition and procedure IDs, immutable revision or digest, method, ordered planned steps, parameters, applicability and permitted variation.

What identities, types, roles, scope, versions and explicit values define test case, procedure, method, revision, step plan, parameter and applicability binding? requirement
Which authority, source, method, evidence, event time and knowledge time support test case, procedure, method, revision, step plan, parameter and applicability binding? provenance
How is test case, procedure, method, revision, step plan, parameter and applicability binding validated, accessed, changed, contested, corrected and retained? validation

Requirement, criterion, expected result, acceptance rule, tolerance and oracle

External requirement and test criterion, expected value or behavior, acceptance rule, tolerance, oracle type, comparator revision and ambiguity handling.

What identities, types, roles, scope, versions and explicit values define requirement, criterion, expected result, acceptance rule, tolerance and oracle? requirement
Which authority, source, method, evidence, event time and knowledge time support requirement, criterion, expected result, acceptance rule, tolerance and oracle? provenance
How is requirement, criterion, expected result, acceptance rule, tolerance and oracle validated, accessed, changed, contested, corrected and retained? validation

Subject, configuration, environment and resources Freezes what was tested and the conditions and means of the run.

Subject, sample, input and configuration

Identifies the tested thing and its run-specific state without taking ownership of the subject master.

Subject identity, type, version, build, pedigree, configuration, state and scope

External subject ID and type, version or build, provenance or test-article pedigree, frozen configuration, initial state, tested boundary and excluded portions.

What identities, types, roles, scope, versions and explicit values define subject identity, type, version, build, pedigree, configuration, state and scope? identity
Which authority, source, method, evidence, event time and knowledge time support subject identity, type, version, build, pedigree, configuration, state and scope? provenance
How is subject identity, type, version, build, pedigree, configuration, state and scope validated, accessed, changed, contested, corrected and retained? validation

Sample, specimen, dataset, input, fixture, precondition and chain of custody

External sample or dataset identity, selection and preparation, fixture input, preconditions, custody, integrity, representativeness and consumption state.

What identities, types, roles, scope, versions and explicit values define sample, specimen, dataset, input, fixture, precondition and chain of custody? evidence
Which authority, source, method, evidence, event time and knowledge time support sample, specimen, dataset, input, fixture, precondition and chain of custody? provenance
How is sample, specimen, dataset, input, fixture, precondition and chain of custody validated, accessed, changed, contested, corrected and retained? validation

Environment, equipment, instruments and dependencies

Records execution conditions and the resources capable of influencing results.

Environment, location, time, platform, network, ambient condition and dependency snapshot

Physical or virtual location, environment profile, platform, operating system, network, dependencies, ambient conditions, clock basis and run-time snapshots.

What identities, types, roles, scope, versions and explicit values define environment, location, time, platform, network, ambient condition and dependency snapshot? spatial
Which authority, source, method, evidence, event time and knowledge time support environment, location, time, platform, network, ambient condition and dependency snapshot? provenance
How is environment, location, time, platform, network, ambient condition and dependency snapshot validated, accessed, changed, contested, corrected and retained? validation

Equipment, instrument, tool, version, calibration, reference material and fixture

External resource IDs, tool versions, calibration or validation status, reference materials, fixtures, uncertainty contribution, suitability and availability.

What identities, types, roles, scope, versions and explicit values define equipment, instrument, tool, version, calibration, reference material and fixture? measurement
Which authority, source, method, evidence, event time and knowledge time support equipment, instrument, tool, version, calibration, reference material and fixture? provenance
How is equipment, instrument, tool, version, calibration, reference material and fixture validated, accessed, changed, contested, corrected and retained? validation

Authorization, conduct, steps and timing Records who or what performed the run, under which authority, and what actually occurred.

Roles, authorization, mode and safety

Makes responsibility, automation and guardrails explicit.

Executor, observer, owner, reviewer, agent, delegation, authorization and segregation

External actors or agents, run roles, delegated authority, competence assertion, approval boundaries, independence and segregation of duties.

What identities, types, roles, scope, versions and explicit values define executor, observer, owner, reviewer, agent, delegation, authorization and segregation? authority
Which authority, source, method, evidence, event time and knowledge time support executor, observer, owner, reviewer, agent, delegation, authorization and segregation? provenance
How is executor, observer, owner, reviewer, agent, delegation, authorization and segregation validated, accessed, changed, contested, corrected and retained? validation

Manual, automatic, semiautomatic mode, tool control, safety, privacy and stop rule

Execution mode, automation tool and controller, human intervention points, safety envelope, privacy constraints, abort triggers and emergency authority.

What identities, types, roles, scope, versions and explicit values define manual, automatic, semiautomatic mode, tool control, safety, privacy and stop rule? constraint
Which authority, source, method, evidence, event time and knowledge time support manual, automatic, semiautomatic mode, tool control, safety, privacy and stop rule? provenance
How is manual, automatic, semiautomatic mode, tool control, safety, privacy and stop rule validated, accessed, changed, contested, corrected and retained? validation

Execution lifecycle, step occurrences and deviations

Captures the append-only event history and actual ordered conduct.

Plan, prepare, start, pause, resume, block, abort, complete, time and state event

Typed lifecycle event, prior and next state, actor or agent, authority, rationale, event time with seconds and offset, observed time and evidence.

What identities, types, roles, scope, versions and explicit values define plan, prepare, start, pause, resume, block, abort, complete, time and state event? lifecycle
Which authority, source, method, evidence, event time and knowledge time support plan, prepare, start, pause, resume, block, abort, complete, time and state event? provenance
How is plan, prepare, start, pause, resume, block, abort, complete, time and state event validated, accessed, changed, contested, corrected and retained? validation

Step occurrence, sequence, input, action, output, duration, log, message, deviation and recovery

Actual step ID, planned-step link, order and concurrency, inputs, action, outputs, timestamps, messages, deviation, recovery and continuation decision.

What identities, types, roles, scope, versions and explicit values define step occurrence, sequence, input, action, output, duration, log, message, deviation and recovery? lifecycle
Which authority, source, method, evidence, event time and knowledge time support step occurrence, sequence, input, action, output, duration, log, message, deviation and recovery? provenance
How is step occurrence, sequence, input, action, output, duration, log, message, deviation and recovery validated, accessed, changed, contested, corrected and retained? validation

Observations, measurements, evidence and results Separates raw observation from interpretation, verdict and broader assurance claim.

Observations, measurements and evidence

Preserves source observations and evidence before conclusion.

Observation, property, value, unit, scale, time, location, method, quality and uncertainty

Observed property, value or category, unit and scale, phenomenon and result time, location, procedure, sensor or observer, quality flag, detection limit and uncertainty.

What identities, types, roles, scope, versions and explicit values define observation, property, value, unit, scale, time, location, method, quality and uncertainty? measurement
Which authority, source, method, evidence, event time and knowledge time support observation, property, value, unit, scale, time, location, method, quality and uncertainty? provenance
How is observation, property, value, unit, scale, time, location, method, quality and uncertainty validated, accessed, changed, contested, corrected and retained? validation

Evidence artifact, pointer, log, trace, image, record, integrity, digest and custody

External artifact identity, relevant pointer, media type, capture event, generating tool or agent, digest, signature, storage, access marking and custody lineage.

What identities, types, roles, scope, versions and explicit values define evidence artifact, pointer, log, trace, image, record, integrity, digest and custody? evidence
Which authority, source, method, evidence, event time and knowledge time support evidence artifact, pointer, log, trace, image, record, integrity, digest and custody? provenance
How is evidence artifact, pointer, log, trace, image, record, integrity, digest and custody validated, accessed, changed, contested, corrected and retained? validation

Comparison, verdict, confidence and review

Builds bounded result assertions without converting them into unearned compliance claims.

Expected, actual, comparator, difference, tolerance, outcome, verdict and rationale

Expected and actual references, comparator and version, difference, tolerance evaluation, outcome vocabulary, verdict issuer, rationale and affected scope.

What identities, types, roles, scope, versions and explicit values define expected, actual, comparator, difference, tolerance, outcome, verdict and rationale? validation
Which authority, source, method, evidence, event time and knowledge time support expected, actual, comparator, difference, tolerance, outcome, verdict and rationale? provenance
How is expected, actual, comparator, difference, tolerance, outcome, verdict and rationale validated, accessed, changed, contested, corrected and retained? validation

Validity, confidence, coverage, review, attestation, signoff and compliance boundary

Run validity, confidence, coverage and limitations, reviewer and attestation, signoff authority, disputes and explicit separation from system-level compliance or certification.

What identities, types, roles, scope, versions and explicit values define validity, confidence, coverage, review, attestation, signoff and compliance boundary? validation
Which authority, source, method, evidence, event time and knowledge time support validity, confidence, coverage, review, attestation, signoff and compliance boundary? provenance
How is validity, confidence, coverage, review, attestation, signoff and compliance boundary validated, accessed, changed, contested, corrected and retained? validation

Anomalies, reruns, review and lifecycle Preserves failed and inconclusive evidence while linking external issue masters and later attempts.

Anomaly, failure, incident, defect and impact links

Records run-local symptoms and source-qualified links to separately governed issue records.

Anomaly, failure, error, timeout, inconclusive, blocked, symptom and triage

Observed anomaly or symptom, failure mode, error and timeout, inconclusive or blocked reason, affected step or subject scope, severity hypothesis and triage state.

What identities, types, roles, scope, versions and explicit values define anomaly, failure, error, timeout, inconclusive, blocked, symptom and triage? evidence
Which authority, source, method, evidence, event time and knowledge time support anomaly, failure, error, timeout, inconclusive, blocked, symptom and triage? provenance
How is anomaly, failure, error, timeout, inconclusive, blocked, symptom and triage validated, accessed, changed, contested, corrected and retained? validation

Defect, incident, risk, nonconformity link, correlation, causality, status and owner

External issue IDs, typed relation, correlation evidence, unconfirmed or confirmed causality, source status, owner, disposition and no-cascade rule.

What identities, types, roles, scope, versions and explicit values define defect, incident, risk, nonconformity link, correlation, causality, status and owner? relationship
Which authority, source, method, evidence, event time and knowledge time support defect, incident, risk, nonconformity link, correlation, causality, status and owner? provenance
How is defect, incident, risk, nonconformity link, correlation, causality, status and owner validated, accessed, changed, contested, corrected and retained? validation

Rerun, reproducibility, review, correction and supersession

Relates attempts and protects released evidence from silent mutation.

Retry, rerun, repeat, reproduction, replication, delta and comparability

New execution ID, predecessor link, reason, controlled and changed factors, procedure and subject equivalence, result delta and bounded reproducibility assessment.

What identities, types, roles, scope, versions and explicit values define retry, rerun, repeat, reproduction, replication, delta and comparability? lifecycle
Which authority, source, method, evidence, event time and knowledge time support retry, rerun, repeat, reproduction, replication, delta and comparability? provenance
How is retry, rerun, repeat, reproduction, replication, delta and comparability validated, accessed, changed, contested, corrected and retained? validation

Review, dispute, invalidate, correct, amend, supersede, release and tombstone

Review and dispute events, invalidation reason, correction successor, release state, supersession link, residual validity and minimum tombstone.

What identities, types, roles, scope, versions and explicit values define review, dispute, invalidate, correct, amend, supersede, release and tombstone? lifecycle
Which authority, source, method, evidence, event time and knowledge time support review, dispute, invalidate, correct, amend, supersede, release and tombstone? provenance
How is review, dispute, invalidate, correct, amend, supersede, release and tombstone validated, accessed, changed, contested, corrected and retained? validation

Provenance, interoperability, access, retention and agent operation Supports attributable exchange and safe management of sensitive test evidence.

Source, provenance and interoperability

Keeps origin and semantic loss visible across projections.

Source assertion, agent, activity, plan, usage, generation, revision, invalidation and contradiction

Assertion identity and source, responsible agent, execution activity and plan, used and generated entities, revision, invalidation, confidence and supporting or contradicting claims.

What identities, types, roles, scope, versions and explicit values define source assertion, agent, activity, plan, usage, generation, revision, invalidation and contradiction? provenance
Which authority, source, method, evidence, event time and knowledge time support source assertion, agent, activity, plan, usage, generation, revision, invalidation and contradiction? provenance
How is source assertion, agent, activity, plan, usage, generation, revision, invalidation and contradiction validated, accessed, changed, contested, corrected and retained? validation

EARL, OSCAL, OMS, PROV, Robot, OpenTelemetry and domain crosswalk

Pinned source and target versions, identity, subject, criterion, action, observation, evidence, status and result mappings, omissions, semantic conflicts and round-trip classification.

What identities, types, roles, scope, versions and explicit values define earl, oscal, oms, prov, robot, opentelemetry and domain crosswalk? interoperability
Which authority, source, method, evidence, event time and knowledge time support earl, oscal, oms, prov, robot, opentelemetry and domain crosswalk? provenance
How is earl, oscal, oms, prov, robot, opentelemetry and domain crosswalk validated, accessed, changed, contested, corrected and retained? validation

Access, privacy, retention and safe automation

Controls reading, execution, correction and disposition for humans and agents.

Role view, purpose, access, disclosure, redaction, exception and audit

Purpose-bound role views, field-redacted projections, disclosure rules, exception authority, expiry and tamper-evident access events.

What identities, types, roles, scope, versions and explicit values define role view, purpose, access, disclosure, redaction, exception and audit? access
Which authority, source, method, evidence, event time and knowledge time support role view, purpose, access, disclosure, redaction, exception and audit? provenance
How is role view, purpose, access, disclosure, redaction, exception and audit validated, accessed, changed, contested, corrected and retained? validation

Retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check

Retention class and trigger, hold, deletion eligibility, tombstone, delegated agent scope, preconditions, dry run, idempotency key, expected revision and post-check.

What identities, types, roles, scope, versions and explicit values define retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check? retention
Which authority, source, method, evidence, event time and knowledge time support retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check? provenance
How is retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check validated, accessed, changed, contested, corrected and retained? validation

Classifiers Filled

Family: World Models
Category: Activities and processes
Entry kind: event
Navigation path: NAV.ACT.TST
Domain: ACT.TST
Industry: Cross-industry
Tags: testexecutionact.tst

What it is Filled

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.

In scope

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 of scope

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

Why it exists Filled

Distinguishing features Filled

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.

What robots and AI may and may not do Filled

Must not

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.

Only with a human decision

Invalidating an execution or waiving a failed criterion.
Accepting results used for certification or safety release.

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.

Moral aspects Filled

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.

Who is affected

End users of the tested product
Test personnel
Certification bodies and regulators

Owners Filled

Steward

Dimension identity, owner, testing authority, quality, safety, privacy and records stewards

Roles

Test owner or accountable authority: Own execution purpose, authorization, acceptance boundaries and accountable disposition.
Test designer or procedure steward: Own reusable case, method, criteria, expected results, oracle and permitted variation.
Executor or automation operator: Perform authorized steps, record deviations and protect source evidence.
Subject, sample or configuration custodian: Own subject identity, pedigree, configuration, sample handling and custody assertions.
Environment, equipment and metrology steward: Own condition, tool, instrument, calibration, reference-material and uncertainty evidence.
Reviewer or assurance authority: Review validity, independence, evidence sufficiency, verdict scope and signoff without rewriting the run.
Data, privacy, safety and records steward: Control protected views, safe execution, retention, holds, disposition and auditability.

Links to other meta-models Filled

references

Test Case, Test Procedure, Requirement, Criterion and Oracle models - Resolve immutable test intent and acceptance logic while keeping the execution occurrence separate.
Subject, Product, Configuration, Sample, Dataset, Environment, Resource and Instrument models - Bind run-specific snapshots and usage without copying external master lifecycles.
Observation, Measurement, Artifact, Defect, Incident, Risk, Assessment and Audit models - Link source evidence, issues and broader assurance records while preserving source identity and authority.

aligned

EARL 1.0 and OSCAL Assessment Results 1.2.0 - Project assertions, subjects, criteria, results, actions, observations, evidence and findings with explicit non-equivalence and loss rules.
OGC OMS, W3C PROV-O, Robot Framework 7.4.2 and OpenTelemetry Semantic Conventions 1.44.0 - Project observations, provenance, software-run artifacts and telemetry status through version-pinned profiles with declared semantic loss.

neighbor

Test Case / Procedure / Requirement / Criterion - Reusable intent and acceptance logic are external versioned definitions. The execution binds the exact revision and records what actually occurred.
Subject / Sample / Environment / Instrument - The execution owns source-qualified snapshots and usage assertions while external masters keep identity, lifecycle and authority.
Observation / Measurement / Evidence Artifact - The execution organizes run-scoped observations and pointers, but source observation and artifact masters retain method, integrity and custody provenance.
Assessment / Verification / Validation / Certification - 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.
Defect / Incident / Risk / Nonconformity - 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.

parent

WM-ACT-034

What else AI and robots need to interact with it Filled

Sources Filled

ISO/IEC/IEEE 29119 series: Software and systems engineering, Software testing - International Organization for Standardization
ISO/IEC/IEEE 29119-3:2021 Software testing, Part 3: Test documentation - International Organization for Standardization
ISO/IEC 17025:2017 General requirements for the competence of testing and calibration laboratories - International Organization for Standardization
Evaluation and Report Language (EARL) 1.0 Schema - World Wide Web Consortium
OSCAL Assessment Layer: Assessment Results Model - National Institute of Standards and Technology
OSCAL Assessment Results Model v1.2.0 XML Format Reference - National Institute of Standards and Technology
Observations, Measurements, and Samples - Open Geospatial Consortium
PROV-O: The PROV Ontology - World Wide Web Consortium
Robot Framework User Guide - Robot Framework Foundation
NASA Systems Engineering Handbook, Appendix I: Verification and Validation Plan Outline - National Aeronautics and Space Administration
OpenTelemetry Test Attributes - OpenTelemetry
NIST Privacy Framework - National Institute of Standards and Technology
Disposing of records - The National Archives, United Kingdom
Date and Time on the Internet: Timestamps - Internet Engineering Task Force

Open questions

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.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-act-035-test-execution/spec.yaml, ver-cy/world-models/card-supplements/wm-act-035-test-execution.json