- Introduced AGENTS.md, README.md, TASKS.md, and implementation_plan.md for Vexer, detailing mission, responsibilities, key components, and operational notes. - Established similar documentation structure for Vulnerability Explorer and Zastava modules, including their respective workflows, integrations, and observability notes. - Created risk scoring profiles documentation outlining the core workflow, factor model, governance, and deliverables. - Ensured all modules adhere to the Aggregation-Only Contract and maintain determinism and provenance in outputs.
		
			
				
	
	
		
			8 lines
		
	
	
		
			514 B
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			8 lines
		
	
	
		
			514 B
		
	
	
	
		
			Markdown
		
	
	
	
	
	
| # CI Recipes architecture
 | |
| 
 | |
| > Reference the AOC guardrails, export workflows, and notification patterns documented in the Authority, Export Center, and Notify module guides when designing CI templates.
 | |
| 
 | |
| This placeholder summarises the planned architecture for CI Recipes. Consolidate design details from implementation plans and upcoming epics before coding.
 | |
| 
 | |
| Refer to the module README and implementation plan for immediate context, and update this document once component boundaries and data flows are finalised.
 |