Reject Unsupported Shapes
BOUNDARY-REJECT-UNSUPPORTED-SHAPES
Summary
Fail unsupported names, values, TTLs, targets, record families, protocols, or modes at the boundary with clear errors. Preserve unknown data only when compatibility requires round-tripping and the system can do so safely.
Rule
Reject unsupported shapes early with clear errors.
Why
Unsupported names, values, TTLs, targets, record families, protocols, or config modes should fail at the boundary with a clear error. Letting them pass inward creates later failures that are harder to connect to the original input.
Helps
- Makes unsupported behavior explicit and prevents partial internal handling of invalid shapes.
Limits
Preserve unknown inputs when compatibility requires round-tripping. Reject inputs when the system cannot safely preserve, ignore, or act on them.
Agent Instruction
Reject unsupported shapes early with clear errors because unsupported names, values, TTLs, targets,
record families, protocols, or config modes should fail at the boundary with a clear error.Mechanisms
Supported by validation errors, capability checks, parser fixtures, schema tests, and docs that list unsupported shapes.