kb-update

To add customer insights to a knowledge base without duplicates, the system checks existing entries before creation. It enforces structured templates and cross-links new knowledge directly to supporting source files in the raw or canon directories.

The best way to structure knowledge base entries for playbooks and decisions is by using predefined templates. This ensures consistency by enforcing specific formatting, slug generation, and source attribution for durable knowledge.

You link raw meeting notes to a new knowledge base entry through mandatory source attribution. The system requires linking newly created knowledge directly to its supporting files located within your raw or canon directories.

Yes, you can classify different knowledge types when writing to a knowledge base directory. The process requires classifying the knowledge type, such as customer data or patterns, before generating slugs and applying specific content guidelines.

Writing knowledge base entries requires source attribution to ensure traceability and prevent unverified information. Linking new entries back to raw or canon data validates the durable knowledge and maintains structural integrity across the directory.