Skip to content

Boundary strict policy

boundaryPolicyStrict is the most conservative boundary‑decision preset.

It forces strict acceptance rules, treats every issue as fatal, and hides nothing from the event or issue streams. This preset is designed for compliance‑grade environments where any deviation must result in rejection.

Signature

export const boundaryPolicyStrict: BoundaryDecideConfig

Behavior

Acceptance mode

  • accept: strict

Strict acceptance means:

  • No issues are tolerated.
  • All fields must be accepted.
  • Any boundary‑level issue forces rejection.

This is the highest enforcement level available.

Reject configuration

  • reject: ["*"]

A wildcard reject pattern means:

  • Every issue code is treated as a reject condition.
  • Any event emitted by parsing, validation, or boundary rules becomes fatal.
  • Contributors cannot accidentally bypass enforcement.

Review configuration

  • review: []

No event codes trigger review.

Strict mode does not defer decisions to human review — it rejects immediately.

Visibility configuration

  • hideEvents: []
  • hideIssues: []

Nothing is hidden:

  • All events remain visible.
  • All issues remain visible.
  • Contributors get full transparency into why the boundary was rejected.

This is essential for compliance and auditing.

Design rationale

  • Provides maximum enforcement at the boundary level.
  • Ensures that any issue — structural, semantic, or relational — results in rejection.
  • Avoids ambiguity by disabling review and hiding nothing.
  • Ideal for regulated domains, high‑assurance systems, and strict API contracts.
  • Keeps contributor expectations clear: if anything is wrong, the boundary fails.

When to use

Use boundaryPolicyStrict when:

  • You need compliance‑grade enforcement.
  • No issues of any kind should be tolerated.
  • You want deterministic, fail‑fast behavior.
  • You want full visibility into event and issue streams.

This enforces strict, zero‑tolerance boundary behavior.