keystone:new-guide

Automating rule guide creation in Keystone involves scaffolding markdown files with canonical frontmatter and cross-links, while simultaneously generating a paired corpus stub for reasoning and references to standardize charter engineering workflows.

Charter engineering standardizes software development rules using structured markdown. You need a paired corpus stub when creating a new rule guide to provide a dedicated space for reasoning, references, and topic activation paths.

To scaffold a new guide and corpus, trigger the automation with a specific topic path like 'process/release'. This generates paired markdown files with canonical frontmatter and customizable activation paths for ambient or phase-based triggering.

Yes, you can customize activation paths based on topic directories. This supports both ambient and phase-based triggering, allowing the generated rule guide and corpus stub to activate correctly within your specific software development workflow.

No dependencies or existing components are required. The automation operates independently to generate the necessary markdown files, canonical frontmatter, and cross-links directly within your Keystone environment.

The best way to reduce manual setup is using automated charter generation. It instantly scaffolds a comprehensive rule guide and its paired corpus stub, eliminating manual configuration and standardizing the markdown structure for your domain.