registryctl.authoring.diagnostics.truncated
At most 64 diagnostics are returned in deterministic order.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- aggregation
- Rule
diagnostic_limit- Safe remediation
- Fix the reported diagnostics and run the check again.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
registryctl.authoring.entity.invalid
A declared entity id and shape must match the project contract.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- semantic validation
- Rule
entity_contract- Safe remediation
- Correct the entity declaration with the entity schema and its project alias.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
<entity-file>#<field>
registryctl.authoring.environment.invalid
Environment bindings must match declared products, integrations, identities, origins, and bounded generations.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- semantic validation
- Rule
environment_binding- Safe remediation
- Align the selected environment with the declared project contract.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
environments/<id>.yaml#<field>
registryctl.authoring.file.too_large
Authored files must remain below their documented fixed byte bound.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- safe input
- Rule
authored_file_size- Safe remediation
- Reduce the file below its documented maximum size.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
<project-relative-file>#<field>
registryctl.authoring.file.unreadable
A regular file inside the project root must be readable.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- safe input
- Rule
authored_file_readability- Safe remediation
- Restore a readable regular project-relative file.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
<project-relative-file>#<field>
registryctl.authoring.fixture.invalid
Fixtures must be deterministic, bounded, and satisfy the integration contract without live values.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- semantic validation
- Rule
fixture_contract- Safe remediation
- Correct the fixture declaration and its closed interaction contract.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
integrations/<id>/fixtures/<fixture>.yaml#<field>
registryctl.authoring.fixture.reserved_body_field
A fixture body object may use `file` only as the closed body-file reference shape.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- syntax
- Rule
fixture_body_file_reference- Safe remediation
- Use the documented body-file reference shape or an inline JSON body.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- received type only
- Lifecycle
- unreleased, not released
- Static address pattern
integrations/<id>/fixtures/<fixture>.yaml#<field>
registryctl.authoring.integration.invalid
An integration alias, capability, and declared contract must be internally consistent.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- semantic validation
- Rule
integration_contract- Safe remediation
- Correct the integration declaration with the integration schema.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
integrations/<id>/integration.yaml#<field>
registryctl.authoring.path.unsafe
Paths must be normalized project-relative paths to regular non-symlink entries.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- safe input
- Rule
project_relative_path- Safe remediation
- Use a normalized project-relative regular file path.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
<project-relative-file>#<field>
registryctl.authoring.project.invalid
Project services, entities, integrations, and references must form a closed valid graph.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- semantic validation
- Rule
project_contract- Safe remediation
- Align the project declaration and referenced contracts.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
registry-stack.yaml#<field>
registryctl.authoring.project.scope_collision
Effective authorization scopes must be distinct across records API and attribute-release access.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- semantic validation
- Rule
authorization_scope_uniqueness- Safe remediation
- Assign distinct scopes to each authorization purpose.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
registry-stack.yaml#<field>
registryctl.authoring.script.closed_contract_violation
Scripts must use the released bounded Script contract and module rules.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- script validation
- Rule
released_script_contract- Safe remediation
- Use only the released bounded Script contract.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
<script-file>#<location>
registryctl.authoring.script.invalid_signature
The Script entrypoint must be exactly `consult(context)`.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- script validation
- Rule
script_entrypoint_signature- Safe remediation
- Define the exact released entrypoint signature.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
<script-file>#<location>
registryctl.authoring.script.syntax_error
The Script source must parse under the released runtime.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- script validation
- Rule
script_syntax- Safe remediation
- Correct the Script syntax at the reported location.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
<script-file>#<location>
registryctl.authoring.script.unknown_function
The Script must define the released `consult(context)` entrypoint.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- script validation
- Rule
script_entrypoint- Safe remediation
- Define consult(context) as the Script entrypoint.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- no received value
- Lifecycle
- unreleased, not released
- Static address pattern
<script-file>#<location>
registryctl.authoring.yaml.invalid_syntax
YAML must parse as the selected closed authoring document shape.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- syntax
- Rule
closed_yaml_document- Safe remediation
- Correct the YAML with the matching authoring schema.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- received type only
- Lifecycle
- unreleased, not released
- Static address pattern
<project-relative-yaml-file>#<field>
registryctl.authoring.yaml.unknown_field
Only documented fields in the closed authoring schema are accepted.
- Family
- authoring validation
- Product and owner
- registryctl; registryctl
- Phase
- syntax
- Rule
closed_yaml_unknown_field- Safe remediation
- Remove the unsupported field or replace it with its documented field.
- Evidence scope
- offline authored project files selected for registryctl check
- Evidence limitation
- Static authoring evidence does not prove live source or deployment compatibility.
- Value policy
- received type only
- Lifecycle
- unreleased, not released
- Static address pattern
<project-relative-yaml-file>#<field>