docs: enhance HERMES_LEARNING_PROMPT with concrete examples and templates
Some checks failed
Cross-Node Transaction Testing / transaction-test (push) Successful in 4s
Deploy to Testnet / deploy-testnet (push) Has been cancelled
Documentation Validation / validate-docs (push) Has started running
Documentation Validation / validate-policies-strict (push) Has been cancelled
Multi-Node Stress Testing / stress-test (push) Has been cancelled
Node Failover Simulation / failover-test (push) Has been cancelled

- Add example debug messages with priority levels
- Add example suggestions with estimated impact
- Add example potential failures with recovery steps
- Enhance output format with detail level guidelines
- Add final deliverable template
- Update version to 2.0 with changelog
This commit is contained in:
aitbc
2026-05-09 11:40:27 +02:00
parent aa66e52edc
commit 69c28db668

View File

@@ -109,24 +109,33 @@ For each stage, Hermes should provide:
## Stage Analysis: [Stage Name]
### Understanding Summary
[Brief summary of what Hermes learned]
[Brief summary of what Hermes learned, 2-3 sentences maximum]
### Debug Messages
- **Issue**: [Description]
- **Impact**: [Why it matters]
- **Suggested Fix**: [How to resolve]
- **Priority**: [High/Medium/Low]
### Suggestions
- **Improvement**: [Description]
- **Rationale**: [Why it helps]
- **Implementation**: [How to implement]
- **Estimated Impact**: [Qualitative or quantitative benefit]
### Potential Failures
- **Failure Scenario**: [Description]
- **Detection**: [How to identify]
- **Mitigation**: [How to prevent]
- **Recovery**: [How to recover if it occurs]
```
**Detail Level Guidelines:**
- **Understanding Summary**: High-level overview, focus on key concepts
- **Debug Messages**: Specific, actionable, with clear priority
- **Suggestions**: Practical, implementable, with estimated impact
- **Potential Failures**: Concrete scenarios with detection/mitigation steps
## Final Deliverable
After completing all 9 stages, Hermes should provide: