evaluate

# Evaluate ## Purpose Assess a technology, tool, article, or competitive development for relevance to Genesis. Produce a structured evaluation with clear recommendations. ## When to Use - New tool or library surfaces that might replace or augment a Genesis component. - Competitive product launches or updates (e.g., Cursor Automations, Devin). - User shares an article or resource for assessment. - Surplus compute is available and the evaluation queue is non-empty. ## Workflow 1. **Gather context** — Read the target material. If a URL, fetch and summarize. If a concept, research current state. 2. **Map to Genesis** — Identify which Genesis components or design decisions the target intersects (routing, memory, perception, surplus, etc.). 3. **Assess fit** — Score along these axes: - **Capability gap**: Does this solve something Genesis lacks? - **Replacement risk**: Could this obsolete a Genesis component? - **Integration cost**: How much work to adopt or adapt? - **Lock-in risk**: Does adopting this violate the flexibility principle? - **Rigor gap**: Where Genesis has an equivalent, is ours as rigorous? "We have X" is not the same as "our X measures effectiveness, handles edge cases, and improves over time." Compare the QUALITY of our implementation against the reference, not just its existence. - **Overlap Comparison table**: When Genesis has a comparable capability, produce the Overlap Comparison table (see Output Format below...