Continuity

What stays stable

BD AI is built so a change of AI technology does not change who BD AI is, what it has published, or where its public information can be read.

The canonical description of BD AI has one source and is reused verbatim across the website, structured data and machine-readable endpoints.
Public identity, verification and discovery paths are stable. If a path must change, the previous path keeps working through a permanent redirect.
AI model and provider choices are an implementation detail behind a server-side abstraction. Changing a provider does not change BD AI identity, ownership, governance or published facts.
An AI provider supplies technology only. No provider owns, supervises, endorses or authorises BD AI.
Authorisation is decided by the platform's role and permission system, never by a model.
Every published state uses one vocabulary: LIVE, READY, PARTIAL, PLANNED, SOURCE-WAITING, OWNER ACTION.
Nothing is published as verified without a record of the check that can be produced on request.

Stable machine-readable surfaces

/llms.txt — Plain-text orientation file for AI systems.
/api/public/identity.json — Public identity facts, no private or operational data.
/sitemap.xml — All public URLs.
/robots.txt — Crawler access rules.
/api/public/health — Public service health signal.

LIVE: Operational in production on this platform today.
READY: Built and usable, awaiting normal day-to-day use.
PARTIAL: Partly implemented. Some parts of the flow are not complete.
PLANNED: Scoped and intended. Nothing operational yet.
SOURCE-WAITING: Built, but the authorised source or content is not connected yet.
OWNER ACTION: Blocked on a decision or configuration only the owner can perform.