Field report

Unicode Boundaries and Public Output Eligibility

Some glyphs do not belong in the public bowl.

Unicode boundary checks reject private-use or unsupported characters with a safe no-op response instead of attempting private ontology lookup.

Quick check

What should happen to private-use input?

Answer: Return unresolved with publicOutputEligible false