{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T09:12:59Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 26.5, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a094e3-2b94-7932-954b-8cf2092fdd49\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: direct numerical simulation\nSense to describe: (none recorded)\nDomain code: ACT.ACT\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Bat", "usd": 0.0, "recall": true }, "codex": { "seconds": 68.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a094e3-2b91-7b63-9147-1327c97c6401\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: direct numerical simulation\nRegistry id: vr.tr.direct-numerical-simulation\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames f" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:43:47+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:25+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1227572", "registryId": "vr.tr.direct-numerical-simulation", "name": "direct numerical simulation", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1227572/", "model": { "registry_id": "vr.tr.direct-numerical-simulation", "name": "direct numerical simulation", "purpose": "Enable an agent to recognise a direct numerical simulation, assess whether its claimed physical scales are resolved, and judge which analyses its results support.", "definition": "Direct numerical simulation (DNS) is a computational approach to turbulent flow that solves the governing fluid equations without a turbulence closure model, resolving the dynamically relevant spatial and temporal scales down to those at which molecular dissipation acts.", "scope_statement": "This model owns direct numerical simulation as a computational activity, especially the simulation of turbulent flow without turbulence closure, including its physical formulation, resolution evidence, execution and limits of interpretation.", "in_scope": [ "The physical equations, flow regime and scales covered by a DNS claim", "Distinction between DNS, large-eddy simulation and Reynolds-averaged simulation", "Spatial and temporal resolution of dynamically relevant flow scales", "Numerical accuracy, execution integrity and reproducibility", "Statistical adequacy and permitted interpretation of simulation outputs" ], "out_of_scope": [ "General computational fluid dynamics methods independent of a DNS claim", "Development and calibration of turbulence closure models", "Computing hardware and cluster administration", "Experimental measurement apparatus and procedures", "The complete theory of turbulence", "Direct numerical solution of arbitrary equations where no DNS-specific resolution claim is made" ], "distinguishing_features": [ "The calculation evolves instantaneous flow fields rather than solving only for turbulence-averaged quantities.", "A turbulent-flow DNS claim requires evidence that the relevant turbulent spatial and temporal scales are resolved without a turbulence closure model.", "Omitting an explicit subgrid model is insufficient: a calculation that relies on numerical dissipation to represent unresolved turbulence does not thereby establish DNS.", "Resolution must be justified for the particular flow, location and observable; a large mesh or successful solver completion alone does not establish DNS.", "DNS remains a numerical solution of selected governing equations and physical assumptions; it does not imply atomistic resolution or the absence of every constitutive model." ], "characteristics": [ { "name": "DNS claim status", "kind": "state", "unit_or_values": "claimed; supported within stated scope; contested; insufficiently evidenced", "why_it_matters": "Separates the simulation's label from the evidence supporting it." }, { "name": "Physical formulation", "kind": "category", "unit_or_values": "Governing equations, compressibility treatment, constitutive assumptions and coupled transport equations", "why_it_matters": "Defines which physical processes the direct-resolution claim actually covers." }, { "name": "Reynolds number and convention", "kind": "measurement", "unit_or_values": "Dimensionless, with the velocity, length and viscosity definitions recorded", "why_it_matters": "Characterises the flow regime and allows meaningful comparison of resolution demands." }, { "name": "Spatial resolution relative to physical scales", "kind": "measurement", "unit_or_values": "Local mesh-spacing-to-scale ratios or spectral cutoff-to-scale products; wall units where applicable", "why_it_matters": "Tests whether the discretisation captures relevant small scales throughout the domain." }, { "name": "Temporal resolution", "kind": "measurement", "unit_or_values": "Time step in seconds or declared nondimensional units, with ratios to relevant physical timescales", "why_it_matters": "A stable time step can still be too coarse to represent the dynamics accurately." }, { "name": "Domain extent and boundary conditions", "kind": "relation", "unit_or_values": "Domain dimensions relative to flow scales, linked to each imposed boundary condition", "why_it_matters": "Identifies confinement, periodicity and boundary effects that can alter the simulated flow." }, { "name": "Turbulence closure and numerical dissipation", "kind": "category", "unit_or_values": "Declared turbulence closures, filters, stabilisation and dissipation mechanisms", "why_it_matters": "Exposes mechanisms that may substitute for resolving turbulent dynamics." }, { "name": "Sampling support", "kind": "measurement", "unit_or_values": "Transient exclusion, sampling duration, output cadence, independent realisations and observable-specific uncertainty", "why_it_matters": "Determines whether reported statistics are adequately supported." } ], "affordances": [ "Assess a DNS claim against its equations, closure choices and resolution evidence.", "Identify locations, scales or observables needing mesh, time-step or domain refinement.", "Design convergence checks and comparisons with applicable reference cases.", "Extract flow structures, spectra, budgets and statistics within the output's sampling limits.", "Determine whether a dataset supports turbulence-model assessment or a proposed physical inference.", "Specify a reproducible continuation or rerun with targeted changes." ], "agent_conduct": { "may": [ "Run or analyze direct numerical simulations on computing resources the agent is authorized to use.", "Report simulation parameters, resolution and validation alongside results." ], "must_not": [ "Present underresolved simulations as direct numerical simulation.", "Extrapolate results to conditions the simulation did not cover without warning.", "Consume shared computing resources beyond the allocation granted.", "Fabricate or alter simulation data." ], "requires_human": [ "Using simulation results for safety-critical engineering decisions." ] }, "ethics": { "considerations": [ "Simulation results inform designs that affect safety.", "Large simulations use significant energy and shared resources." ], "affected_parties": [ "Engineers and designers", "Research users", "Users of shared computing" ] }, "owners": { "steward": "Nobody owns the method; the research group answers for each simulation.", "master_systems": [] }, "visual_identification": [ "Results appear as detailed visualizations of turbulent eddies and vortices across many scales." ], "failure_modes_and_hazards": [ "Insufficient resolution produces misleading results.", "Overconfidence in simulations without experimental validation." ], "what_it_is_for": [ "Direct numerical simulation is used in fluid dynamics research to study turbulent flow while resolving its dynamically relevant scales.", "Its detailed flow fields support analysis of turbulence mechanisms and evaluation of simplified turbulence models.", "Computational cost generally restricts its use to flow conditions and domains that available computing resources can resolve." ], "standards_and_regulation": [ "ASME V&V 20, issued by the American Society of Mechanical Engineers, provides a verification and validation framework for computational fluid dynamics and heat transfer that can be applied to direct numerical simulation." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1227572: direct numerical simulation", "url": "https://www.wikidata.org/wiki/Q1227572", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Direct numerical simulation", "url": "https://en.wikipedia.org/wiki/Direct_numerical_simulation", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "dns-claim-and-physical-scope", "name": "DNS claim and physical scope", "description": "Establishes what is being simulated directly and which approximations remain.", "rationale": "The DNS label is meaningful only relative to a stated physical formulation and resolution claim.", "layers": [ { "id": "governing-flow-problem", "name": "Governing flow problem", "description": "Identifies the equations, regime and conditions defining the calculation.", "findings": [ { "id": "equations-and-regime", "name": "Equations and regime", "description": "Record the instantaneous equations, material assumptions, forcing and nondimensional parameters with their conventions.", "questions": [ { "text": "Which governing equations and constitutive assumptions define the flow, and which physical processes are omitted?", "kind": "definition", "id": "equations-and-regime-q01" }, { "text": "How are Reynolds number and any additional controlling parameters defined and measured for this case?", "kind": "measurement", "id": "equations-and-regime-q02" } ] } ] }, { "id": "direct-resolution-boundary", "name": "Direct-resolution boundary", "description": "Separates resolved turbulent motion from explicitly or implicitly represented unresolved processes.", "findings": [ { "id": "closure-and-label", "name": "Closure and label", "description": "Record the basis of the DNS designation, including turbulence closures, filters and any narrower scope of direct resolution.", "questions": [ { "text": "Which turbulent motions are claimed to be resolved, and does any closure or numerical mechanism stand in for unresolved turbulence?", "kind": "boundary", "id": "closure-and-label-q01" }, { "text": "Which publication or run documentation supports the DNS designation and states its limitations?", "kind": "provenance", "id": "closure-and-label-q02" }, { "text": "For coupled scalar, reacting or multiphase physics, which processes are resolved directly and which remain modelled?", "kind": "boundary", "id": "closure-and-label-q03" } ] } ] } ] }, { "id": "scale-and-domain-resolution", "name": "Scale and domain resolution", "description": "Captures evidence that the calculation represents the relevant small scales, large structures and time evolution.", "rationale": "DNS credibility depends on adequate resolution across the physical domain and relevant scale range.", "layers": [ { "id": "small-scale-spatial-resolution", "name": "Small-scale spatial resolution", "description": "Assesses local and directional resolution against appropriate physical scales.", "findings": [ { "id": "local-resolution-evidence", "name": "Local resolution evidence", "description": "Record mesh or spectral resolution, its spatial variation and the diagnostics used to justify adequacy.", "questions": [ { "text": "Which small-scale criteria apply to this flow, and how do local grid spacings or spectral cutoffs compare with them?", "kind": "measurement", "id": "local-resolution-evidence-q01" }, { "text": "Where do walls, intermittency or coupled transport introduce resolution demands that a domain-average criterion could conceal?", "kind": "boundary", "id": "local-resolution-evidence-q02" }, { "text": "Which refinement comparisons or spectral diagnostics support resolution of the observables being reported?", "kind": "provenance", "id": "local-resolution-evidence-q03" } ] } ] }, { "id": "time-and-domain-coverage", "name": "Time and domain coverage", "description": "Checks temporal accuracy and whether domain boundaries constrain relevant flow structures.", "findings": [ { "id": "temporal-and-domain-adequacy", "name": "Temporal and domain adequacy", "description": "Record time-step evidence, domain dimensions and boundary sensitivity separately from solver stability.", "questions": [ { "text": "What time-step refinement evidence demonstrates accuracy for the fastest relevant dynamics and target observables?", "kind": "measurement", "id": "temporal-and-domain-adequacy-q01" }, { "text": "How do domain-size checks, correlations or boundary-sensitivity studies establish that important structures are accommodated?", "kind": "measurement", "id": "temporal-and-domain-adequacy-q02" }, { "text": "Which time-step, domain or boundary changes should be tested before accepting the DNS claim?", "kind": "action", "id": "temporal-and-domain-adequacy-q03" } ] } ] } ] }, { "id": "numerical-fidelity-and-run-evidence", "name": "Numerical fidelity and run evidence", "description": "Connects discretisation choices and executed-run records to the accuracy of the flow solution.", "rationale": "Nominal resolution cannot compensate for uncontrolled numerical error or an untraceable calculation.", "layers": [ { "id": "discretisation-and-error-control", "name": "Discretisation and error control", "description": "Examines numerical mechanisms that can distort resolved turbulence.", "findings": [ { "id": "numerical-error-budget", "name": "Numerical error budget", "description": "Record spatial and temporal schemes, solver tolerances, applicable aliasing control and numerical contributions to flow budgets.", "questions": [ { "text": "Which discretisations, tolerances, filters and aliasing controls were used, and how could they affect small-scale motion?", "kind": "definition", "id": "numerical-error-budget-q01" }, { "text": "What applicable conservation, constraint or energy-budget checks quantify residual numerical error?", "kind": "measurement", "id": "numerical-error-budget-q02" }, { "text": "How is artificial dissipation distinguished from the physical dissipation represented by the governing equations?", "kind": "measurement", "id": "numerical-error-budget-q03" } ] } ] }, { "id": "executed-run-traceability", "name": "Executed-run traceability", "description": "Links reported results to the actual solver configuration, initial state and execution history.", "findings": [ { "id": "reproducible-flow-realisation", "name": "Reproducible flow realisation", "description": "Record the software version, inputs, initialisation, forcing, restarts and verification evidence needed to reconstruct the calculation.", "questions": [ { "text": "Which versioned code, configuration, initial conditions and forcing records identify the executed run?", "kind": "provenance", "id": "reproducible-flow-realisation-q01" }, { "text": "What verification cases or convergence results support the solver for the equations and boundary conditions used here?", "kind": "provenance", "id": "reproducible-flow-realisation-q02" }, { "text": "What must be preserved to reproduce the setup and statistically comparable results despite chaotic trajectory divergence?", "kind": "action", "id": "reproducible-flow-realisation-q03" } ] } ] } ] }, { "id": "statistical-evidence-and-use", "name": "Statistical evidence and use", "description": "Determines what the resolved flow record can support as a statistical or physical conclusion.", "rationale": "A well-resolved trajectory can still provide inadequate sampling or support claims beyond the simulated regime.", "layers": [ { "id": "sampling-and-observables", "name": "Sampling and observables", "description": "Relates transient handling, averaging and stored outputs to each reported quantity.", "findings": [ { "id": "observable-specific-sampling", "name": "Observable-specific sampling", "description": "Record how statistics are formed and whether their temporal, spatial or ensemble support is adequate.", "questions": [ { "text": "Which transient intervals are excluded, and what supports stationarity or the chosen treatment of a nonstationary flow?", "kind": "measurement", "id": "observable-specific-sampling-q01" }, { "text": "How are correlations, averaging assumptions and effective sample counts reflected in uncertainty for each target statistic?", "kind": "measurement", "id": "observable-specific-sampling-q02" }, { "text": "Does the saved field resolution and output cadence support the proposed spectra, gradients or event analysis?", "kind": "action", "id": "observable-specific-sampling-q03" } ] } ] }, { "id": "comparison-and-transfer", "name": "Comparison and transfer", "description": "Constrains validation, model assessment and generalisation to cases supported by the simulation.", "findings": [ { "id": "supported-inference", "name": "Supported inference", "description": "Record reference comparisons, mismatched conditions and limits on treating DNS outputs as evidence for other regimes.", "questions": [ { "text": "Which experimental or reference datasets provide relevant comparisons, and how closely do their parameters and boundary conditions match?", "kind": "provenance", "id": "supported-inference-q01" }, { "text": "Which conclusions are confined to this Reynolds number, geometry, forcing and physical formulation?", "kind": "boundary", "id": "supported-inference-q02" }, { "text": "What additional checks or simulations are required before using these outputs to assess a closure model or generalise a physical claim?", "kind": "action", "id": "supported-inference-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The conventional sense is turbulence simulation in fluid mechanics; the registry supplies no narrower sense.", "Resolution targets are methodological guidance, not universal acceptance criteria; convergence and adequacy must be checked for the quantities being studied.", "Reacting, scalar-transport and multiphase simulations can require scales smaller than the velocity dissipation scale; the label DNS should specify which physics is resolved and which remains modelled." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of direct numerical simulation this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Incompressible-flow DNS", "Compressible-flow DNS", "Wall-bounded turbulence DNS", "Homogeneous turbulence DNS", "Reacting-flow DNS", "Multiphase-flow DNS" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of direct numerical simulation this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Investigating turbulence production, energy transfer and dissipation.", "Generating reference data for developing and evaluating turbulence models.", "Studying wall friction and heat or mass transfer.", "Investigating interactions between turbulence and chemical reactions.", "Testing flow-control strategies in computational experiments." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of direct numerical simulation this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Reynolds number", "typical_range": "Case dependent; the velocity and length scales defining it must be specified.", "unit": "dimensionless" }, { "quantity": "Grid spacing relative to the Kolmogorov length scale", "typical_range": "Order unity or smaller is a common resolution target in incompressible turbulence; adequacy depends on the numerical method and observable.", "unit": "dimensionless" }, { "quantity": "Maximum resolved wavenumber multiplied by the Kolmogorov length scale", "typical_range": "Values around 1-2 are common resolution targets in spectral simulations of homogeneous incompressible turbulence, with stricter requirements possible.", "unit": "dimensionless" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of direct numerical simulation this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Insufficient spatial or temporal resolution can suppress dissipation-scale dynamics while producing apparently plausible large-scale flow.", "Numerical dissipation, dispersion or aliasing can distort energy transfer and turbulence statistics.", "An undersized computational domain or inappropriate boundary conditions can constrain the flow artificially.", "Insufficient averaging time or too few independent samples can produce unreliable statistics.", "Resolving turbulence does not remove uncertainty from chemical kinetics, interface models, material properties or the governing physical assumptions." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of direct numerical simulation this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Computational fluid dynamics", "difference": "CFD is the broader family of numerical fluid-flow methods; DNS specifically resolves turbulent scales without a turbulence closure." }, { "name": "Large-eddy simulation", "difference": "LES resolves larger turbulent motions while representing the effects of unresolved motions through a subgrid treatment; DNS aims to resolve the dissipation scales." }, { "name": "Reynolds-averaged Navier-Stokes simulation", "difference": "RANS solves averaged equations with turbulence closures rather than resolving the full time-dependent turbulent velocity field." }, { "name": "Implicit large-eddy simulation", "difference": "Implicit LES uses numerical dissipation to represent unresolved-scale effects; the absence of an explicit turbulence model alone does not establish that a simulation is DNS." }, { "name": "Direct simulation Monte Carlo", "difference": "DSMC statistically simulates molecular motion and collisions, principally for rarefied gases; conventional turbulence DNS solves continuum fluid equations." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of direct numerical simulation this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend the conventional turbulent-flow meaning of direct numerical simulation, or also established uses in other disciplines?", "Which flow-specific resolution criteria and acceptance evidence should the model require for wall-bounded, compressible, reacting and multiphase cases?", "How should borderline calculations with appreciable filtering or stabilisation be classified when the authors call them DNS?", "What minimum evidence should distinguish a supported DNS claim from a designation whose underlying run data are unavailable?", "Which observable-specific uncertainty and sampling requirements should govern reuse of DNS datasets for model assessment?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 14, "questions": 29 } }