.boundary-allowlist

# .boundary-allowlist
#
# Files in this list are exempt from scripts/check-public-boundary.sh.
# Each entry MUST include a one-line comment explaining why the file
# legitimately needs to contain something that matches a denylist pattern.
#
# Format: one path per line, glob patterns allowed.
# Empty lines and lines starting with # are ignored.
#
# See docs/strategy/public-boundary-STRATEGY.md for the rules.

# The CI script itself contains the denylist regexes, which include the
# patterns we are forbidding elsewhere.
scripts/check-public-boundary.sh

# README has a single "this is NOT Optiscan's deployment" framing
# clarifying audience scope. The reference is intentional and clarifies
# that this repo is the harness-agnostic reference server, not any one
# organization's private deployment.
README.md

# Design doc references Optiscan in the scope-clarification banner
# ("Production deployment specifics for any organization (Optiscan
# or otherwise) — those live in private deployment repos"). The
# naming is intentional and clarifies the doc's audience.
docs/design/api-and-spa-DESIGN.md