Annotation Forwarding
Uniform model
Holding Document → Forwarding Annotation → Nexter Colony
A forwarding annotation declares where held data continues. It is not an executable command, capability grant, or deployment authorization.
Required behavior
- Parse the annotation.
- Validate destination syntax.
- Resolve the declared Nexter Colony.
- Check policy and capability.
- Check resource and forwarding limits.
- Detect cycles and forwarding loops.
- Preserve trace and source metadata.
- Forward data unchanged unless the destination contract explicitly permits a documented transformation.
- Record success or rejection.
- Emit an observable diagnostic when forwarding cannot complete.
Failure modes
Malformed destination: reject. Unauthorized capability: reject. Unknown Nexter Colony: unresolved. Loop or hop-limit violation: reject. Resource limit: reject. Accepted destination: forward and record success.
Example: @next system/network/transport. The document is the Holding Document; system/network/transport is its Nexter Colony.