Override
An override is an explicitly supplied setting or action that changes or supersedes default behavior within a defined scope.
Machine Learning System Design
An explicitly configured result or behavior that supersedes an automated system decision for specified inputs.
- How it is used
- Provides a manual or rule-based correction when a model prediction is unsuitable or fails in a specific scenario.
- How deep it goes
- Explains prediction thresholds, temporary rules, tracking, and follow-up, but does not specify an implementation.
- Examples
- Uses low-confidence or out-of-range predictions and a customer-reported failure as cases for applying an override.
- What you can do after
- Operate overrides by tracking manual adjustments and planning how to replace temporary rules with a lasting fix.
Effective Platform Engineering
A tool parameter override is a caller-supplied value that changes a shared pipeline's default arguments for a tool.
- How it is used
- Customizes shared CircleCI jobs without changing their reusable implementation or waiting for shared-code approval.
- How deep it goes
- Explains argument injection, validation guardrails, and Terraform command syntax, while stopping short of a complete validation implementation.
- Examples
- Uses Terraform init and plan additional arguments, variable-file settings, output paths, and optional post-checkout or post-plan steps.
- What you can do after
- Apply it via CircleCI job parameters to adapt shared Terraform commands without editing the shared job.
The Art of AI Product Development
A manual override is a user-provided change that supersedes or adjusts an automated system output.
- How it is used
- Uses manual adjustments to help users manage forecast errors and retain control.
- How deep it goes
- Explains how to spot, adjust, and report forecast errors, but does not detail override implementation.
- Examples
- Demonstrates adjusting a forecast when it conflicts with local insight and flagging the problem for review.
- What you can do after
- Apply it by adjusting mismatched predictions and reporting errors through the forecasting interface.
Read how The Art of AI Product Development explains override →
Automating API Delivery
A Spectral override is a configuration that changes rule applicability or severity for selected API documents or objects.
- How it is used
- Customizes lint-rule applicability or severity for selected OpenAPI documents and objects during gradual API standardization.
- How deep it goes
- Explains file globs, JSON Pointers, percent encoding, severities, ruleset configuration, and CLI results.
- Examples
- Uses a User API and targets missing operationId values on PUT and DELETE operations.
- What you can do after
- Configure Spectral overrides and interpret selective lint warnings or suppressed violations.
Authorization in Action
A policy override is a rule or configuration that applies a local exception to an otherwise applicable authorization policy without modifying the base policy.
- How it is used
- Handles resource-, workspace-, or customer-specific authorization exceptions alongside template-generated policies.
- How deep it goes
- Defines additional Cedar policies, contrasts them with global constraints, and demonstrates a scoped forbid rule.
- Examples
- Uses stricter customer sharing, temporary contractor editing, and a sensitive legal workspace as examples.
- What you can do after
- Operate/configure Cedar by adding a scoped exception without editing the originating template.
Related concepts
- Spectralimplemented by · Spectral is an open-source linter that applies configurable rules to JSON, YAML, and structured API description documents.
- rulesetconfigures · A ruleset is an organized collection of rules applied together to evaluate inputs, guide decisions, or govern behavior.
- fallbackkind of · A fallback is an alternative behavior, result, resource, or processing path selected when a preferred option fails, is unavailable, or cannot handle a situation.
- retention policyconfigures · A retention policy is a rule specifying what data or records are preserved, for how long, and under what conditions they may be archived, deleted, or otherwise disposed of.
- policyuses · A policy is a rule, strategy, or mapping that governs or determines decisions, actions, permissions, or behavior under specified conditions.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.