Boundary default policy¶
boundaryPolicyDefault is the neutral, low‑interference boundary‑decision preset.
It accepts all fields by default, applies no automatic rejects or reviews, and hides nothing from the event or issue streams. This preset is designed to provide predictable, transparent behavior without enforcing strict structural rules.
Signature¶
export const boundaryPolicyDefault: BoundaryDecideConfig
Behavior¶
Acceptance mode¶
accept:all
“All” acceptance means:
- All fields must be accepted for the boundary to be accepted.
- Issues do not automatically cause rejection.
- Acceptance is determined strictly by field‑level decisions.
This is the baseline, non‑strict mode.
Ignore configuration¶
ignore:[]
No event codes are ignored.
Every event is surfaced and available for policy interpretation.
Reject configuration¶
reject:[]
No event codes automatically cause rejection.
Boundary‑level issues do not become fatal unless a rule explicitly emits a reject‑severity event.
Review configuration¶
review:[]
No event codes trigger review.
The boundary is either accepted or rejected based solely on field decisions and explicit boundary rules.
Visibility configuration¶
hideEvents:[]hideIssues:[]
Nothing is hidden:
- All events remain visible.
- All issues remain visible.
This ensures full transparency during development and debugging.
Design rationale¶
- Provides a neutral baseline for boundaries.
- Avoids surprising behavior by disabling automatic rejects, reviews, and hiding.
- Ensures contributors see the complete event and issue streams.
- Keeps the boundary decision process simple and predictable.
- Ideal for development, testing, and contributor onboarding.
When to use¶
Use boundaryPolicyDefault when:
- You want predictable, low‑interference boundary behavior.
- You are building or testing new boundaries.
- You want full visibility into events and issues.
- You want to layer custom boundary rules on top of a clean slate.
This applies the neutral, transparent default boundary‑decision behavior.