epistemic-beliefs

You can capture epistemic beliefs by running the belief-creation script to generate a formal statement with an id, evidence links, and relationship metadata. This ensures your design decisions are stored with traceable justification for future reference.

Epistemic beliefs are formal representations of project decisions, design patterns, and recurring principles stored with evidence and linked relationships. They provide traceable justification for why specific technical choices were made over time.

You can link related project decisions by using the belief-creation workflow to connect new beliefs to existing ones through evidence links and wikilinks. This supports mapping relationships between beliefs and attacks for comprehensive justification.

Yes, the belief-management workflow integrates with the Patina scrape pipeline to compute metrics and validate truth across sessions. This integration ensures formal beliefs are tracked and evaluated continuously within your project environment.

You should persist session learnings as formal beliefs when you identify recurring design patterns or principles that require evidence linking and relationship mapping. This ensures decisions remain traceable and justifiable rather than static documentation.

Revision history tracking for epistemic beliefs depends on the Patina scrape pipeline and frontmatter metadata structure. Limitations arise if evidence links or relationship mappings are incomplete, which can affect metric computation and cross-session validation accuracy.