Use this catalog for the safe error codes produced by Registryctl’s offline synthetic fixture
harness. These entries describe bounded fixture evidence. They do not prove that a live source is
reachable, compatible, or authorized.
Run registryctl project diagnostics --catalog fixture --format json for the exact
workspace-independent machine catalog. The command does not open a country project, contact a
runtime, or read environment variables and secrets.
This page is generated from product-owned static definitions. It does not inspect a project, environment variables, secrets, runtime configuration, source responses, or country values.
- Catalog
- fixture
- Schema
registryctl.fixture_error_reference.v1- Entries
- 16
- Runtime value reads
- None
Download the machine-readable fixture diagnostic catalog. Entries are ordered by family, product, and code. An unreleased entry has no release attribution; its introduced_in value remains null until a product owner records a released lifecycle.
authorization.denied
Authorization denied fixture execution before source access.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
authorization_before_source- Safe remediation
- Align the fixture identity and authorization expectation with the compiled policy.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
failure.subject_mismatch
The source observation did not preserve the requested subject binding.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
subject_binding- Safe remediation
- Correct the synthetic subject evidence or the reviewed subject comparison.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
fixture.execution_contract_invalid
Fixture execution violated the compiled offline plan contract.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
compiled_execution_contract- Safe remediation
- Align the fixture with the exact compiled integration plan.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
fixture.profile_not_found
The fixture profile pin did not select one exact compiled plan.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
profile_pin- Safe remediation
- Select one compiled integration profile.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
fixture.request_mismatch
The rendered request or call order did not match the fixture expectation.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
request_authority_and_order- Safe remediation
- Align the fixture request expectation with the compiled plan.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
fixture.source_operation_unknown
The fixture named a source operation outside the compiled plan.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
source_operation_closure- Safe remediation
- Use only source operations declared by the compiled plan.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
input.pattern_mismatch
A synthetic fixture input did not satisfy its compiled contract.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
compiled_input_contract- Safe remediation
- Correct the synthetic input shape.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
redacted_unclassified_error
An error outside the reviewed safe allow-list was redacted.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
safe_error_allow_list- Safe remediation
- Use classified fixture evidence or inspect private local logs without publishing values.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
source.call_budget_exceeded
Fixture execution exceeded the compiled source-call budget.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
source_call_budget- Safe remediation
- Reduce source calls or revise the reviewed bounded plan.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
source.cardinality_violation
The synthetic source response violated the compiled cardinality contract.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
source_cardinality- Safe remediation
- Correct the synthetic response cardinality.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
source.deadline_exceeded
The synthetic source interaction exceeded its deadline.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
source_deadline- Safe remediation
- Align the timeout fixture with the compiled deadline behavior.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
source.response_malformed
The synthetic source response violated its closed response contract.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
source_response_contract- Safe remediation
- Correct the synthetic response shape.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
source.response_too_large
The synthetic source response exceeded its compiled byte bound.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
source_response_byte_bound- Safe remediation
- Reduce the synthetic response below the compiled bound.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
source.status_rejected
The synthetic source returned a status outside the accepted mapping.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
source_status_mapping- Safe remediation
- Use a reviewed status mapping or correct the fixture status.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
source.unavailable
The synthetic source was unavailable.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
source_availability- Safe remediation
- Correct the offline source observation for the intended availability case.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released
source_unavailable
The synthetic source was unavailable under the retained legacy code.
- Family
- fixture execution
- Product and owner
- registryctl relay offline harness; registryctl
- Phase
- offline execution
- Rule
legacy_source_availability- Safe remediation
- Prefer source.unavailable for new fixtures while retaining compatible evidence.
- Evidence scope
- offline synthetic fixture execution
- Evidence limitation
- Offline synthetic evidence does not prove live source compatibility.
- Value policy
- no runtime values
- Lifecycle
- unreleased, not released