Knowledge_baseDevelopment
Vitruvyan Docs
Docs Federation Operations
Last Updated: February 26, 2026
Objective
Allow docs authored on any VPS to converge into the official core KB (MkDocs hub) while keeping clear separation between:
- core docs (domain-agnostic),
- vertical docs (domain-specific).
Topology
- Producer VPS example:
161.xxx.xxx.xxx(mercator+ local core copy) - Hub VPS example:
144.xxx.xxx.xxx(officialvitruvyan-core+ MkDocs)
Producer Setup (161...)
Set environment variables and publish:
Optional:
DOCS_CHANGED_ONLY=falseto publish full markdown corpus.DOCS_INCLUDE_UNCOMMITTED=truefor local unstaged drafts.
Hub Setup (144...)
In official vitruvyan-core repo:
Ingestion call (normally invoked by producer via SSH):
What it does:
- Routes docs to
docs/knowledge_base/federated/... - Refreshes federated index pages
- Ensures MkDocs nav block exists
- Builds MkDocs (if command available)
- Runs optional KB ingestion command (
DOCS_KB_INGEST_CMD)
Recommended Automation
- Producer cron every 5 minutes or post-merge hook:
- publish only when
docs/**/*.mdchanged.
- publish only when
- Hub systemd path/timer:
- ingest new bundles from
incoming_docs/.
- ingest new bundles from
Contract
Use metadata rules from:
docs/contracts/platform/DOCS_FEDERATION_CONTRACT_V1.md