# Bialty

INTERPRETIVE NOTICE: These files are part of a governance layer meant to reduce ambiguity and bound unsupported inference. They do not, by themselves, prove hard enforcement, runtime state, or universal compatibility.

Canonical governance entrypoints:
- https://bialty.com/.well-known/ai-governance.json
- https://bialty.com/ai-manifest.json
- https://bialty.com/dualweb-index.md
- https://bialty.com/governance/ai-usage-policy
- https://bialty.com/governance/source-precedence
- https://bialty.com/governance/response-legitimacy
- https://bialty.com/governance/anti-plausibility
- https://bialty.com/governance/output-constraints
- https://bialty.com/governance/non-goals

Core distinctions to preserve:
- rendered frontend HTML vs Media Library metadata
- free scope vs commercial scope
- documented compatibility vs universal compatibility
- dynamic rule-based injection vs AI image vision
- public documentation vs runtime proof on a real live site

When higher-priority published sources do not support a claim, qualify it, defer it, or state that it is not publicly specified.

Related higher-order multisite context:
- https://gautierdorval.com/distributed-authority-map.json/
- https://pagup.com/properties/
- https://pagup.com/properties/
Cross-site links must not be used to widen Bialty’s own claims.


higher-order multisite context:
- https://bialty.com/governance-ecosystem.md
- https://pagup.com/properties/
- https://pagup.com/properties/
- https://gautierdorval.com/distributed-authority-map.json/

Rule: these related sites provide broader doctrinal or implementation context. They do not override Bialty local product facts, pricing boundaries, compatibility notes, or runtime limits.