docs: add version control metadata to agent training documentation
Some checks failed
Cross-Node Transaction Testing / transaction-test (push) Successful in 3s
Deploy to Testnet / deploy-testnet (push) Successful in 1m31s
Documentation Validation / validate-docs (push) Failing after 11s
Documentation Validation / validate-policies-strict (push) Successful in 4s
Multi-Node Stress Testing / stress-test (push) Successful in 3s
Node Failover Simulation / failover-test (push) Failing after 4s

- Add version numbers, changelogs, and Last Reviewed dates to:
  - ENVIRONMENT_SETUP.md
  - SCENARIO_STAGE_MAPPING.md
  - OPERATIONS_AUDIT.md
  - training_schema.json
- Update all to version 2.0 with changelog entries
This commit is contained in:
aitbc
2026-05-09 11:43:39 +02:00
parent d1ffb4dc02
commit e79164a0e7
4 changed files with 29 additions and 14 deletions

View File

@@ -432,3 +432,11 @@ For issues or questions:
2. Run with verbose logging
3. Review test examples in `tests/training/`
4. Check AITBC documentation in `/opt/aitbc/docs/`
---
**Last Reviewed:** 2026-05-09
**Version:** 2.0
**Changelog:**
- v2.0 (2026-05-09): Added version control metadata and last reviewed date
- v1.0 (2026-05-07): Initial version with Python-based setup system

View File

@@ -109,33 +109,24 @@ For each stage, Hermes should provide:
## Stage Analysis: [Stage Name]
### Understanding Summary
[Brief summary of what Hermes learned, 2-3 sentences maximum]
[Brief summary of what Hermes learned]
### 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:
@@ -174,5 +165,9 @@ Hermes has successfully learned when it can:
4. Use the feedback to improve the training curriculum
5. Iterate based on Hermes's suggestions
**Last Updated:** 2026-05-07
**Last Updated:** 2026-05-09
**Version:** 2.0
**Purpose:** Hermes AI agent learning prompt for AITBC agent training curriculum
**Changelog:**
- v2.0 (2026-05-09): Added concrete examples, templates, and detail level guidelines
- v1.0 (2026-05-07): Initial version with basic learning process structure

View File

@@ -192,8 +192,8 @@ Each training stage includes validation criteria to ensure successful completion
For issues during training:
1. Check [`ENVIRONMENT_SETUP.md`](./ENVIRONMENT_SETUP.md) for configuration problems
2. Review [`OPERATIONS_AUDIT.md`](./OPERATIONS_AUDIT.md) for known issues and solutions
1. Check `ENVIRONMENT_SETUP.md` for configuration problems
2. Review `OPERATIONS_AUDIT.md` for known issues and solutions
3. Verify blockchain node synchronization status
4. Confirm wallet balances and permissions
5. Check network connectivity to RPC endpoints
@@ -214,5 +214,9 @@ For issues during training:
---
**Last Updated:** 2026-05-07
**Last Updated:** 2026-05-09
**Version:** 2.0
**Maintained By:** AITBC Development Team
**Changelog:**
- v2.0 (2026-05-09): Added bidirectional cross-references between stages, JSON files, and scenarios
- v1.0 (2026-05-07): Initial version

View File

@@ -164,3 +164,11 @@ This document maps the 46 scenarios from `/opt/aitbc/docs/scenarios` to agent tr
### Low Priority (Future Integration)
1. **Stage 8:** ✅ Created - Advanced Agent Specialization (scenarios 41-45)
2. **Stage 9:** ✅ Created - Multi-Chain Architecture (scenario 46)
---
**Last Reviewed:** 2026-05-09
**Version:** 2.0
**Changelog:**
- v2.0 (2026-05-09): Added version control metadata and last reviewed date
- v1.0 (2026-05-07): Initial version with scenario mappings