{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T09:22:03Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 19.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: 01a094eb-619e-7ca0-9dc8-052c87ae2722\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: dynamic voltage scaling\nSense to describe: (none recorded)\nDomain code: ACT.ACT\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 0", "usd": 0.0, "recall": true }, "codex": { "seconds": 74.7, "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: 01a094eb-61a3-7880-985b-9c729a54f9bb\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: dynamic voltage scaling\nRegistry id: vr.tr.dynamic-voltage-scaling\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded in" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:44:31+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:32+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q632037", "registryId": "vr.tr.dynamic-voltage-scaling", "name": "dynamic voltage scaling", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q632037/", "model": { "registry_id": "vr.tr.dynamic-voltage-scaling", "name": "dynamic voltage scaling", "purpose": "Enable an AI agent to recognise dynamic voltage scaling, assess its operating constraints and effects, and determine which supply-voltage changes are permitted under changing workload or device conditions.", "definition": "Dynamic voltage scaling is a power-management technique that changes an integrated circuit's supply voltage during operation to reduce energy consumption while maintaining the timing and functional requirements of its current workload.", "scope_statement": "This model owns the runtime activity of selecting, applying and evaluating supply-voltage changes for a powered computational circuit or voltage domain, including coordination with frequency when required and explicit recording of implementation-specific constraints.", "in_scope": [ "Identification of the circuit, supply rail and shared voltage domain subject to runtime adjustment", "Supported voltage settings and their dependence on frequency, operating conditions and validation evidence", "Policies that choose voltage changes from workload, timing, power or thermal observations", "Execution, acknowledgement and recovery of voltage transitions", "Evaluation of correctness, performance and energy effects against an explicit baseline" ], "out_of_scope": [ "Dynamic frequency scaling considered independently of supply-voltage changes", "Power gating and the lifecycle of switching an entire domain off or on", "Voltage-regulator circuit design and manufacture", "Static undervolting configuration without runtime voltage selection", "General workload scheduling except where it supplies constraints or signals for voltage decisions", "Whole-device thermal management beyond its constraints on the scaling activity" ], "distinguishing_features": [ "An instance must involve runtime selection or adjustment of a circuit's supply-voltage target; changing only clock frequency does not establish dynamic voltage scaling.", "A fixed undervolted setting alone does not establish dynamic scaling; the model must identify how voltage can change during operation.", "A voltage transition must be distinguishable from uncontrolled rail droop, measurement noise or regulator ripple.", "Switching a domain off is a neighbouring power-gating action; scaling concerns voltage selection for operation, with retention-only states explicitly classified at the boundary.", "When voltage and frequency are jointly controlled, the model identifies dynamic voltage scaling as the voltage component of the combined activity rather than treating DVS and DVFS as automatically interchangeable." ], "characteristics": [ { "name": "Controlled voltage domain", "kind": "relation", "unit_or_values": "Supply rail, powered components and components sharing its voltage setting", "why_it_matters": "A voltage choice must satisfy the constraints of every affected component." }, { "name": "Scaling mechanism", "kind": "category", "unit_or_values": "Discrete operating-point selection, continuously adjustable target, feedback-driven adjustment, or implementation-defined", "why_it_matters": "Determines which actions and observations the agent can represent." }, { "name": "Requested and observed supply voltage", "kind": "measurement", "unit_or_values": "V, with timestamp, measurement location and uncertainty", "why_it_matters": "Separates the commanded target from the voltage delivered to the circuit." }, { "name": "Associated clock frequency", "kind": "measurement", "unit_or_values": "Hz per affected clock domain", "why_it_matters": "Allows voltage choices to be assessed against the implementation's timing constraints." }, { "name": "Validated operating envelope", "kind": "relation", "unit_or_values": "Permitted voltage-frequency combinations linked to temperature, device variation, ageing assumptions and validation evidence", "why_it_matters": "Provides the evidence-backed boundary for permitted operation." }, { "name": "Decision policy", "kind": "relation", "unit_or_values": "Controller, input signals, objective, thresholds, hysteresis and decision interval", "why_it_matters": "Explains why a change was selected and whether the decision can be reproduced." }, { "name": "Performance obligation", "kind": "measurement", "unit_or_values": "Deadline or latency in s, throughput in completed work/s, or an explicitly defined service constraint", "why_it_matters": "Makes performance requirements part of voltage selection and evaluation." }, { "name": "Transition state", "kind": "state", "unit_or_values": "Stable, requested, transitioning, settled, rejected, failed, or recovering", "why_it_matters": "Prevents a request from being mistaken for a completed operating-point change." }, { "name": "Transition duration", "kind": "measurement", "unit_or_values": "s, with separately defined command, ramp, settling and coordination intervals where observable", "why_it_matters": "Determines when the new setting is usable and whether short workload phases justify changing it." }, { "name": "Energy per completed workload", "kind": "measurement", "unit_or_values": "J for a defined workload and measurement boundary", "why_it_matters": "Tests whether scaling improves total energy use after transition costs and execution-time changes are included." }, { "name": "Correctness and timing evidence", "kind": "relation", "unit_or_values": "Validation results, runtime error observations, timing monitors and recovery records", "why_it_matters": "Supports acceptance or rejection of a setting without assuming that an absence of reported errors proves correctness." } ], "affordances": [ "Classify an observed control action as voltage scaling, combined voltage-frequency scaling or a neighbouring mechanism.", "Enumerate permitted target voltages for the current frequency, domain membership and operating conditions.", "Propose or request an authorised voltage transition using the platform's validated coordination procedure.", "Check whether the requested target was reached and invoke a documented recovery action when it was not.", "Compare candidate policies using correctness, workload completion, energy and transition overhead.", "Identify unsupported operating points or missing evidence and withhold their use pending validation." ], "agent_conduct": { "may": [ "Explain how dynamic voltage scaling saves energy and its trade-offs.", "Adjust voltage settings on hardware the agent is authorized to manage, within the manufacturer's limits." ], "must_not": [ "Push voltages outside safe operating ranges on hardware.", "Change power settings on systems the agent does not administer.", "Disable thermal or power protection to gain performance." ], "requires_human": [ "Changing power management on safety-critical or shared systems." ] }, "ethics": { "considerations": [ "Energy efficiency reduces costs and environmental impact.", "Unstable settings can cause data loss for users." ], "affected_parties": [ "Device users", "System operators" ] }, "owners": { "steward": "Nobody owns the technique; the operator of a device answers for its settings.", "master_systems": [] }, "visual_identification": [ "Not visible; observed through voltage and frequency readings in monitoring tools." ], "failure_modes_and_hazards": [ "Too low a voltage causes crashes and data corruption.", "Overvolting causes overheating and shortens hardware life." ], "what_it_is_for": [ "Dynamic voltage scaling is used in processors and other integrated circuits whose workloads and power requirements change during operation.", "Device controllers and operating systems use it to manage energy consumption and heat while respecting supported operating conditions and performance requirements." ], "standards_and_regulation": [ "The Advanced Configuration and Power Interface specification, issued by the UEFI Forum, defines operating-system power and performance management interfaces relevant to platforms that coordinate voltage changes with processor performance states." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q632037: dynamic voltage scaling", "url": "https://www.wikidata.org/wiki/Q632037", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Dynamic voltage scaling", "url": "https://en.wikipedia.org/wiki/Dynamic_voltage_scaling", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "voltage-scaling-identity", "name": "Voltage scaling identity", "description": "Establishes what activity is being modelled and which electrical domain it affects.", "rationale": "DVS must be identifiable independently of frequency changes, static configuration and unrelated rail fluctuations.", "layers": [ { "id": "mechanism-boundary", "name": "Mechanism boundary", "description": "Records the operational meaning of dynamic voltage scaling in the implementation.", "findings": [ { "id": "runtime-voltage-selection", "name": "Runtime voltage selection", "description": "Establish whether an identifiable mechanism changes the supply-voltage target during operation and how its terminology relates to DVS, DVFS and adaptive voltage scaling.", "questions": [ { "text": "What runtime behaviour qualifies as dynamic voltage scaling in this implementation?", "kind": "definition", "id": "runtime-voltage-selection-q01" }, { "text": "Which observations distinguish target changes from static undervolting, frequency-only changes and uncommanded voltage variation?", "kind": "boundary", "id": "runtime-voltage-selection-q02" } ] } ] }, { "id": "electrical-control-domain", "name": "Electrical control domain", "description": "Identifies the supply being adjusted and all consumers constrained by its setting.", "findings": [ { "id": "shared-rail-membership", "name": "Shared rail membership", "description": "Record the controlled rail, its consumers and any coupling that prevents independent voltage selection.", "questions": [ { "text": "Which processors, memories, accelerators or other circuits share the adjusted voltage?", "kind": "boundary", "id": "shared-rail-membership-q01" }, { "text": "Which hardware documentation or inspected configuration establishes rail membership and control ownership?", "kind": "provenance", "id": "shared-rail-membership-q02" } ] } ] } ] }, { "id": "permitted-voltage-envelope", "name": "Permitted voltage envelope", "description": "Represents supported settings and the conditions under which they are valid.", "rationale": "A voltage target cannot be judged independently of timing requirements, shared consumers and the evidence supporting its limits.", "layers": [ { "id": "supported-operating-points", "name": "Supported operating points", "description": "Captures selectable voltages and their relationships to clocks and other component constraints.", "findings": [ { "id": "voltage-frequency-permissions", "name": "Voltage-frequency permissions", "description": "Record discrete operating points or a validated selection rule, including limits imposed by every affected consumer.", "questions": [ { "text": "Which voltage targets or ranges are permitted at each relevant clock frequency?", "kind": "measurement", "id": "voltage-frequency-permissions-q01" }, { "text": "What evidence authorises these combinations, and does it permit interpolation between listed points?", "kind": "provenance", "id": "voltage-frequency-permissions-q02" } ] } ] }, { "id": "condition-dependent-validity", "name": "Condition-dependent validity", "description": "Records where operating-point evidence applies and what may invalidate it.", "findings": [ { "id": "margins-and-device-conditions", "name": "Margins and device conditions", "description": "Associate voltage limits and margins with the implementation's stated temperature, variation, ageing and supply-delivery assumptions.", "questions": [ { "text": "For which device revisions, temperatures and lifetime assumptions has the operating envelope been validated?", "kind": "provenance", "id": "margins-and-device-conditions-q01" }, { "text": "What action is required when a monitored condition leaves that envelope or cannot be measured reliably?", "kind": "action", "id": "margins-and-device-conditions-q02" } ] } ] } ] }, { "id": "voltage-selection-policy", "name": "Voltage selection policy", "description": "Explains how observations and obligations produce a proposed target.", "rationale": "The model needs to distinguish an available voltage from a justified decision to use it.", "layers": [ { "id": "workload-and-service-constraints", "name": "Workload and service constraints", "description": "Relates voltage decisions to work that must be completed and constraints that must be preserved.", "findings": [ { "id": "decision-objective-and-obligations", "name": "Decision objective and obligations", "description": "Record whether the controller seeks energy reduction, power limitation, thermal relief or another objective, together with binding performance requirements.", "questions": [ { "text": "What objective selects among permitted targets, and over what workload or time horizon is it evaluated?", "kind": "definition", "id": "decision-objective-and-obligations-q01" }, { "text": "Which deadlines, latency bounds or throughput requirements must a proposed change preserve?", "kind": "measurement", "id": "decision-objective-and-obligations-q02" } ] } ] }, { "id": "feedback-and-decision-timing", "name": "Feedback and decision timing", "description": "Captures the observations and temporal rules used to select targets.", "findings": [ { "id": "controller-inputs-and-stability", "name": "Controller inputs and stability", "description": "Record signal freshness, prediction assumptions, thresholds and mechanisms that limit excessive switching or conflicting requests.", "questions": [ { "text": "Which utilisation, queue, timing, power or temperature signals drive voltage selection, and how fresh must they be?", "kind": "measurement", "id": "controller-inputs-and-stability-q01" }, { "text": "What hysteresis, minimum residence time or arbitration rule governs repeated or conflicting target requests?", "kind": "action", "id": "controller-inputs-and-stability-q02" } ] } ] } ] }, { "id": "voltage-transition-execution", "name": "Voltage transition execution", "description": "Represents the path from an authorised target request to a verified operating state.", "rationale": "A permitted endpoint does not by itself establish that the transition path is permitted or complete.", "layers": [ { "id": "transition-coordination", "name": "Transition coordination", "description": "Captures the implementation-specific ordering of voltage, clock and dependent-component changes.", "findings": [ { "id": "validated-transition-procedure", "name": "Validated transition procedure", "description": "Record the required sequence, intermediate-state constraints and authority responsible for applying the transition.", "questions": [ { "text": "What documented sequence coordinates voltage and clock changes for each transition direction?", "kind": "action", "id": "validated-transition-procedure-q01" }, { "text": "Which intermediate settings, slew limits and shared-domain dependencies constrain that sequence?", "kind": "boundary", "id": "validated-transition-procedure-q02" } ] } ] }, { "id": "completion-and-recovery", "name": "Completion and recovery", "description": "Distinguishes request acceptance, electrical settling and successful operation.", "findings": [ { "id": "target-verification-and-fallback", "name": "Target verification and fallback", "description": "Identify the evidence for completion, timeout conditions and a validated recovery route.", "questions": [ { "text": "What acknowledgement or measurement demonstrates that the target voltage has settled within its required tolerance?", "kind": "measurement", "id": "target-verification-and-fallback-q01" }, { "text": "Which recovery procedure applies to rejection, timeout, unexpected rail behaviour or a detected execution error?", "kind": "action", "id": "target-verification-and-fallback-q02" } ] } ] } ] }, { "id": "scaling-outcome-evidence", "name": "Scaling outcome evidence", "description": "Assesses whether voltage scaling achieved its objective while preserving required operation.", "rationale": "Lower voltage alone is insufficient evidence of lower workload energy or acceptable execution.", "layers": [ { "id": "energy-and-performance-accounting", "name": "Energy and performance accounting", "description": "Defines a fair comparison of scaling policies or operating choices.", "findings": [ { "id": "workload-normalised-comparison", "name": "Workload-normalised comparison", "description": "Compare equivalent completed work using explicit energy boundaries, execution time and transition overhead.", "questions": [ { "text": "What baseline, workload and measurement boundary support the energy comparison?", "kind": "measurement", "id": "workload-normalised-comparison-q01" }, { "text": "Does the accounting include transition energy, changed execution duration and regulator losses where they fall within that boundary?", "kind": "boundary", "id": "workload-normalised-comparison-q02" } ] } ] }, { "id": "correctness-and-evidence-limits", "name": "Correctness and evidence limits", "description": "Records observed failures and the limits of successful validation.", "findings": [ { "id": "validated-results-and-detection-coverage", "name": "Validated results and detection coverage", "description": "Link outcome claims to validation workloads, error-detection coverage and the conditions actually tested.", "questions": [ { "text": "Which tests and runtime monitors support correctness and timing claims at the selected voltages?", "kind": "provenance", "id": "validated-results-and-detection-coverage-q01" }, { "text": "Which workloads, device conditions or silent-error modes remain outside the evidence?", "kind": "boundary", "id": "validated-results-and-detection-coverage-q02" } ] } ] } ] }, { "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": [ "Terminology overlaps: some publications use DVS for techniques that also change frequency.", "For CMOS switching power, the familiar proportionality to voltage squared assumes other factors are held constant; total task energy also depends on leakage, execution time, and transition costs.", "This description is recalled knowledge, not source-verified research; device-specific voltage limits and transition procedures require documentation." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of dynamic voltage scaling 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": [ "Workload-driven voltage scaling", "Feedback-controlled adaptive voltage scaling", "Independent voltage scaling of multiple power domains" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of dynamic voltage scaling this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "Technical abbreviation", "value_or_pattern": "DVS", "note": "Common abbreviation for dynamic voltage scaling; not a unique registry identifier." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of dynamic voltage scaling 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": [ "Reducing processor energy consumption in mobile and embedded devices", "Adjusting CPU and GPU operating voltages as performance demand changes", "Managing power and thermal limits in systems on chips", "Reducing energy use in digital signal processors and hardware accelerators" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of dynamic voltage scaling 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": "Supply voltage", "typical_range": "Device-specific operating limits; no universal range", "unit": "V" }, { "quantity": "Voltage-transition latency", "typical_range": "Depends on voltage regulator, transition size, and settling requirements", "unit": "s" }, { "quantity": "Energy per completed task", "typical_range": "Workload-dependent; compared with operation at a fixed voltage", "unit": "J" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of dynamic voltage scaling 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 voltage for the selected clock frequency causes timing violations and potentially incorrect computation.", "Supply droop or regulator transients can push a circuit below its safe operating voltage.", "Poorly coordinated voltage and frequency transitions can temporarily create an unsafe operating point.", "Transition overhead or increased execution time can erase expected energy savings.", "Voltage limits that ignore temperature, manufacturing variation, or aging can compromise reliability." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of dynamic voltage scaling 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": "Dynamic voltage and frequency scaling", "difference": "DVFS explicitly adjusts both supply voltage and clock frequency; DVS names the voltage adjustment, although usage sometimes overlaps." }, { "name": "Dynamic frequency scaling", "difference": "Changes clock frequency without necessarily changing supply voltage." }, { "name": "Adaptive voltage scaling", "difference": "Uses feedback or device-specific information to determine the needed voltage; it can overlap with DVS, which emphasizes changes during operation." }, { "name": "Power gating", "difference": "Disconnects power from an inactive circuit block rather than adjusting its powered operating voltage." }, { "name": "Clock gating", "difference": "Suppresses clock transitions in inactive circuitry without necessarily changing its supply voltage." }, { "name": "Undervolting", "difference": "Sets voltage below a reference or default value and may be static; DVS requires voltage changes during operation." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of dynamic voltage scaling this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which authoritative sources should establish the registry definition and the relationship among DVS, DVFS and adaptive voltage scaling?", "Should this entry include runtime voltage adjustment of non-computational circuits, or should its scope remain computational voltage domains?", "Should transitions into retention-only voltage states count as DVS here or belong entirely to a neighbouring power-state model?", "How should intentionally error-tolerant voltage scaling be represented when detected errors and recovery are part of the operating policy?", "What minimum validation and telemetry evidence should an agent require before recommending or applying an operating point on a particular platform?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 27 } }