kb

Automating knowledge-base maintenance involves running scheduled scans to detect new research materials, ingesting them into the repository, and generating indexes. This ensures documents remain accessible and up-to-date without manual file transfers.

A knowledge-base health check validates the integrity and coverage of your document collections by scanning for errors and producing statistical reports. It helps identify missing indexes, broken references, or uningested files within the repository.

Running knowledge-base indexing and linting requires defining a script execution path (KB_SCRIPTS_PATH) and ensuring script dependencies are installed. The environment uses structured commands like scan, apply, lint, and index to manage repository operations.

Yes, knowledge-base maintenance supports research libraries, document collections, and knowledge graphs. It handles regular scans, ingestion, validation, and indexing, making it suitable for maintaining research notes and graph structures.

The best way to perform a first-time sync on a research library is to execute a scan for new materials, followed by the apply command to ingest them, and finally generate the index. This establishes the baseline repository structure.

Knowledge-base ingestion may fail to pick up files if the scan command does not cover the target directory, or if frontmatter-driven discovery requirements are not met. Run a health check to validate coverage and ensure files have the correct metadata.