LLM Enrichment - Complior

How it works

complior fix --ai

When --ai is used, the document generation pipeline adds an extra step: LLM fills [TO BE COMPLETED] and  markers using passport data as context.

Without `--ai`	With `--ai`
Documents scaffolded with placeholders	LLM fills placeholders (90–95% complete)
Compliance flags already set	Same flags, richer content
25–80% pre-filled from passport	90–95% filled
Instant	+10–30 seconds per document

Safety

The LLM call is wrapped through @complior/sdk proxy with prohibited, sanitize, and rate-limit hooks active. The LLM cannot bypass compliance checks.

LLM does NOT modify passport JSON. It only enriches document markdown files. Compliance flags (fria_completed, policy_generated) are set identically with or without --ai.

Fallback

If LLM call fails (network error, rate limit, invalid key), the fixer returns the document from the scaffold stage — with placeholders but all compliance flags intact. No data loss, no silent failure.

BYOK configuration

Configure your LLM provider in .complior/config.toml:

[llm]
provider = "openai"          # openai, anthropic, openrouter, ollama
model = "gpt-4o"
api_key_env = "OPENAI_API_KEY"  # reads from environment variable

OverviewStandardized AI system identity card — 36 fields, ed25519 signed, 2 generation modes.

​How it works

​Safety

​Fallback

​BYOK configuration

How it works

Safety

Fallback

BYOK configuration