Browse A-Z
Alphabetical public term index for this language.
機械支援の翻訳下書き (Japanese) for "Scheduler Resource Quota": Scheduler Resource Quota is a compute limit that sets how much compute a workload may consume for placement of work onto resources. It uses policy, reservations, and usage tracking so teams can protect shared capacity while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Scheduler Resource Quota when the cluster needed to place a job, so the team could protect shared capacity before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Scheduler Runtime Profile": Scheduler Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for placement of work onto resources. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Scheduler Runtime Profile when the cluster needed to place a job, so the team could target optimization work before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Scheduler Workload Priority": Scheduler Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for placement of work onto resources. It uses priority classes, preemption rules, and fairness limits so teams can protect critical paths while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Scheduler Workload Priority when the cluster needed to place a job, so the team could protect critical paths before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Scivias": Scivias is listed by Polymaths as a notable work associated with Hildegard of Bingen, connecting that figure's public legacy to Theology, Music, Medicine.
“例文の下書き: Scivias appears in the Polymaths profile for Hildegard of Bingen.”
機械支援の翻訳下書き (Japanese) for "Search API Contract": The Search API Contract is a interface agreement that describes how search api data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“例文の下書き: The developer checked the Search API Contract before sending article or definition data to PlatPhorm.”
機械支援の翻訳下書き (Japanese) for "Search API Endpoint": The Search API Endpoint is a addressable API route that describes how search api data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“例文の下書き: The developer checked the Search API Endpoint before sending article or definition data to PlatPhorm.”
機械支援の翻訳下書き (Japanese) for "Search API Payload": The Search API Payload is a request or message body that describes how search api data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“例文の下書き: The developer checked the Search API Payload before sending article or definition data to PlatPhorm.”
機械支援の翻訳下書き (Japanese) for "Search API Response": The Search API Response is a returned API object that describes how search api data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“例文の下書き: The developer checked the Search API Response before sending article or definition data to PlatPhorm.”
機械支援の翻訳下書き (Japanese) for "Search API Schema": The Search API Schema is a structured data definition that describes how search api data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“例文の下書き: The developer checked the Search API Schema before sending article or definition data to PlatPhorm.”
機械支援の翻訳下書き (Japanese) for "Search Boost Filter": The Search Boost Filter is a selection constraint for finding search boost information in PlatPhorm News. It improves discovery across article listings, dictionary terms, domains, tags, sources, and AI-readable network metadata.
“例文の下書き: The Search Boost Filter surfaced the most relevant article listing from the PlatPhorm feed.”
機械支援の翻訳下書き (Japanese) for "Search Boost Index": The Search Boost Index is a searchable catalog for finding search boost information in PlatPhorm News. It improves discovery across article listings, dictionary terms, domains, tags, sources, and AI-readable network metadata.
“例文の下書き: The Search Boost Index surfaced the most relevant article listing from the PlatPhorm feed.”
機械支援の翻訳下書き (Japanese) for "Search Boost Query": The Search Boost Query is a search request pattern for finding search boost information in PlatPhorm News. It improves discovery across article listings, dictionary terms, domains, tags, sources, and AI-readable network metadata.
“例文の下書き: The Search Boost Query surfaced the most relevant article listing from the PlatPhorm feed.”
機械支援の翻訳下書き (Japanese) for "Search Boost Ranking": The Search Boost Ranking is a ordering method for finding search boost information in PlatPhorm News. It improves discovery across article listings, dictionary terms, domains, tags, sources, and AI-readable network metadata.
“例文の下書き: The Search Boost Ranking surfaced the most relevant article listing from the PlatPhorm feed.”
機械支援の翻訳下書き (Japanese) for "Search Boost Result": The Search Boost Result is a returned discovery item for finding search boost information in PlatPhorm News. It improves discovery across article listings, dictionary terms, domains, tags, sources, and AI-readable network metadata.
“例文の下書き: The Search Boost Result surfaced the most relevant article listing from the PlatPhorm feed.”
機械支援の翻訳下書き (Japanese) for "Secret Approval Step": Secret Approval Step is a devops workflow control that requires review before a sensitive change proceeds for credential and sensitive configuration. It uses role checks, comments, and audit logs so teams can keep high-risk automation accountable while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Secret Approval Step when a token rotated, so the team could keep high-risk automation accountable before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Secret Artifact Signature": Secret Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for credential and sensitive configuration. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Secret Artifact Signature when a token rotated, so the team could trust deployed packages before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Secret Build Gate": Secret Build Gate is a devops quality gate that blocks promotion when required checks fail for credential and sensitive configuration. It uses tests, lint, security scans, and policy rules so teams can prevent broken releases while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Secret Build Gate when a token rotated, so the team could prevent broken releases before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Secret Config Drift Check": Secret Config Drift Check is a devops consistency check that finds differences between intended and live configuration for credential and sensitive configuration. It uses desired state, live state, and diff reports so teams can avoid surprise environment behavior while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Secret Config Drift Check when a token rotated, so the team could avoid surprise environment behavior before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Secret Incident Timeline": Secret Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for credential and sensitive configuration. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Secret Incident Timeline when a token rotated, so the team could learn from outages without guesswork before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Secret Infra Plan": Secret Infra Plan is a devops change preview that shows expected infrastructure changes before apply for credential and sensitive configuration. It uses resource graphs, policy checks, and cost notes so teams can review platform changes safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Secret Infra Plan when a token rotated, so the team could review platform changes safely before the deployment window opened.”