One pipeline, four stages

Docsloth is not an MDX theme and not a chatbot. It reads your software, keeps a versioned document program, and renders that one program for humans and agents alike.

1. Knowledge

Onboarding asks for source access, selected repositories, the AI funding route and the deployment mode — nothing else.

• Release vectors are manifests across repositories, not a single branch hash.
• Facts carry evidence: static analysis, declared architecture, instrumented runs or owner sources.
• Coverage is measured. A stack we cannot parse says so instead of improvising.

2. Content

A document program compiles to every representation from one atomic release.

3. Components

48 first-party components with real states and capability-gated execution; Web Component and sandboxed-iframe bridges for other frameworks.

• Connected components ask for a scoped capability and show permission_required when refused.
• Media requires captions or a transcript; graphs ship an accessible table alternative.
• Third-party hosts render unknown components with a labelled fallback instead of crashing.

4. Maintenance

Source changes produce impact analysis before any prose changes.

• Protected human writing (company/*, legal/*) requires an explicit approval decision.
• Publication is an atomic compare-and-swap; old releases keep their own semantics.
• Rollback repoints a manifest without re-running generation.

Actions