Skip to content

Boundary lax policy

boundaryPolicyLax is the most permissive boundary‑decision preset.

It accepts any field combination, ignores all events, hides all event and issue output, and applies no automatic rejects or reviews. This preset is designed for development, experimentation, and scenarios where strict boundary enforcement is unnecessary or undesirable.

Signature

export const boundaryPolicyLax: BoundaryDecideConfig

Behavior

Acceptance mode

  • accept: any

“Any” acceptance means:

  • The boundary is accepted as long as at least one field is accepted.
  • Boundary‑level issues do not affect acceptance.
  • Structural or semantic problems do not automatically cause rejection.

This is the most permissive acceptance mode.

Ignore configuration

  • ignore: ["*"]

A wildcard ignore pattern means:

  • All event codes are ignored.
  • No event contributes to rejection, review, or visibility.
  • Boundary rules and validators can still emit events, but policy discards them.

Visibility configuration

  • hideEvents: ["*"]
  • hideIssues: ["*"]

Everything is hidden:

  • No events are surfaced.
  • No issues are surfaced.
  • Contributors see no boundary‑level output.

This creates a silent, low‑noise environment.

Reject configuration

  • reject: []

No event codes automatically cause rejection.

Combined with ignore: ["*"], this means nothing can trigger a boundary‑level reject.

Review configuration

  • review: []

No event codes trigger review.

Lax mode never escalates to human review.

Design rationale

  • Provides a silent, permissive environment for development and prototyping.
  • Eliminates noise by hiding all events and issues.
  • Ensures that boundaries are accepted unless explicitly rejected by field‑level decisions.
  • Allows contributors to focus on field‑level behavior without boundary interference.
  • Ideal for early schema design, debugging, or non‑critical data flows.

When to use

Use boundaryPolicyLax when:

  • You want maximum permissiveness.
  • You want to suppress all boundary‑level noise.
  • You are experimenting with new boundaries.
  • You want to observe field‑level behavior without boundary constraints.
  • You are working in a non‑strict or exploratory environment.

This applies a permissive, silent boundary‑decision preset.