1. Intended machine-readable assets
Compliance Health publishes the following public assets for AI systems:
- /agents
- /fr/agents
- /agents/manifest.json
- /agents/manifest.schema.json
- /agents/changelog.json
- /llms.txt
- /ai-policy
- /fr/ai-policy
- /clearregs
- /solutions
- /trust
- /security
- /privacy
- /about
- /team
- /contact
2. Retrieval and indexing
Public website content is available for standard search indexing and retrieval use cases by compliant crawlers. Canonical references should prioritize the agent hub, manifest, llms.txt, AI policy, and linked public source pages listed above.
3. Training scope
Model-training crawlers are permitted on the curated public assets above, as expressed in robots policy. Crawling outside this allowlist is disallowed for configured training bots. This scope is intended to make current public Compliance Health facts discoverable without publishing proprietary implementation details.
4. User-triggered agents
User-triggered agents may retrieve public Compliance Health content when acting at a user's direction. They should prioritize the latest manifest, llms.txt, agent hub, AI policy, and canonical public source pages when summarizing Compliance Health.
5. Accuracy and freshness
Agents should rely on the latest published manifest version and changelog. Public claims should be interpreted as informational and not legal, medical, or customer-specific regulatory advice.
6. Product AI boundaries
Compliance Health describes Medi as a grounded assistant and managed administration/service layer, not an autonomous decision-maker. Medi can support student and admin questions, support-email handling, status explanations, and escalation paths inside approved workflows.
CredFlow is described publicly as a workflow inside Monitor for package creation and verification. AI-assisted or OCR-supported outputs route to human review for consequential, ambiguous, low-confidence, exception, and customer-defined escalation outcomes.
7. Safety boundaries
Agents should not infer customer names, private infrastructure, prompts, deployment details, certification status, autonomous final compliance decisions, ClearRegs public self-serve access, CredFlow as a standalone public product, or non-public technical controls from public discovery content.
8. Contact
Questions about AI crawler usage or data handling can be directed to contact@compliancehealth.com.