Orchestrata Ultimate / RTM / 061-cheetahclaws-volk
RTM: 061-cheetahclaws-volk
Requirement to symbol to test rows for 061-cheetahclaws-volk: CheetahClaws Volk Agent Integration.
At a glance
| Item | Value |
|---|---|
| Requirement IDs | 50 |
Traced from src/ |
0 (0.0%) |
| Untraced | 50 |
Cited from tests/ |
0 (0.0%) |
Traced in src/ but not cited from tests/ |
0 |
Reading this matrix
This matrix lists each of the 50 requirement IDs of spec 061-cheetahclaws-volk with the src/ symbols that cite it and the tests that cite it. 0 of them (0.0%) have at least one citing symbol and 50 have none.
0 requirements are also cited from tests/, and 0 are traced in code but never named by a test. A test citation is a @traces on a test function; it shows intent to cover, not that the test runs or reaches the symbol.
Rows showing none in the symbols column are the gaps to close first. The densest untraced groups are REQ-061-* (50).
Requirement to symbols to tests
| Requirement | Symbols in src/ |
Tests citing it |
|---|---|---|
REQ-061-001 All CheetahClaws slash commands SHALL be available through Orchestrata. |
none | none |
REQ-061-002 The integration SHALL render diffs in real time. |
none | none |
REQ-061-003 The integration SHALL support multi-file edits. |
none | none |
REQ-061-004 Results produced by agents working in parallel SHALL be aggregated correctly. |
none | none |
REQ-061-005 Checkpoint metadata SHALL be persisted. |
none | none |
REQ-061-006 The CheetahClaws Volk SHALL be configured by a CheetahClawsConfig object that... |
none | none |
REQ-061-007 A Checkpoint SHALL be an object that requires id (string), files (array of... |
none | none |
REQ-061-008 The CheetahClaws TUI SHALL launch via Orchestrata. (FR-001, P0) |
none | none |
REQ-061-009 File edit commands SHALL route to CheetahClaws. (FR-002, P0) |
none | none |
REQ-061-010 The checkpoint system SHALL be functional. (FR-003, P0) |
none | none |
REQ-061-011 Rollback SHALL restore files. (FR-004, P0) |
none | none |
REQ-061-012 The Volk SHALL integrate with the CXP protocol. (FR-005, P1) |
none | none |
REQ-061-013 Multi-agent coordination SHALL be supported. (FR-006, P1) |
none | none |
REQ-061-014 Model selection SHALL be configurable. (FR-007, P2) |
none | none |
REQ-061-015 On an edit of a non-existent file (E-001, file not found) the system SHALL return an... |
none | none |
REQ-061-016 When there is no write access (E-002, permission denied) the system SHALL show a... |
none | none |
REQ-061-017 When a path contains ../ (E-003, path traversal) the system SHALL reject it with a... |
none | none |
REQ-061-018 When a file is larger than 10MB (E-004, file too large) the system SHALL reject it... |
none | none |
REQ-061-019 On an attempt to edit a binary file (E-005) the system SHALL reject it by binary... |
none | none |
REQ-061-020 When a checkpoint file is corrupted (E-006, checkpoint corrupt) the system SHALL... |
none | none |
REQ-061-021 When an external API is unavailable (E-007, network failure) the system SHALL retry... |
none | none |
REQ-061-022 When the requested model is not available (E-008, model unavailable) the system SHALL... |
none | none |
REQ-061-023 When an agent exceeds its timeout (E-009, agent timeout) the system SHALL return... |
none | none |
REQ-061-024 When old_string does not match (E-010, invalid edit) the system SHALL show the... |
none | none |
REQ-061-025 The CheetahClawsService interface SHALL expose `edit_file(path: string, old_string:... |
none | none |
REQ-061-101 File edits SHALL complete in under 100ms. (Performance) |
none | none |
REQ-061-102 The integration SHALL sustain 99.9% uptime. (Reliability) |
none | none |
REQ-061-103 Path validation SHALL be required. (Security) |
none | none |
REQ-061-104 The integration SHALL provide rich diff rendering. (Usability) |
none | none |
REQ-061-026 File-system access SHALL go through sandboxed operations. |
none | none |
REQ-061-027 The model provider SHALL be OpenRouter. |
none | none |
REQ-061-028 An API key SHALL be required for model access. |
none | none |
REQ-061-029 Authentication SHALL be session-based. |
none | none |
REQ-061-030 Authorization SHALL be governed by the permission mode (ask, bypass or strict). |
none | none |
REQ-061-031 File operation policies SHALL be enforced. |
none | none |
REQ-061-032 All file operations SHALL be logged. |
none | none |
REQ-061-033 Checkpoint history SHALL be maintained. |
none | none |
REQ-061-034 File operations SHALL be subject to an approval policy point. |
none | none |
REQ-061-035 Dangerous commands SHALL be blocked. |
none | none |
REQ-061-036 Requests SHALL be rate-limited per user. |
none | none |
REQ-061-037 The CheetahClawsTUI class SHALL expose the async operations... |
none | none |
REQ-061-038 Unit tests SHALL cover file edit operations, checkpoint creation/rollback, and path... |
none | none |
REQ-061-039 Integration tests SHALL cover the CXP protocol and multi-agent coordination. |
none | none |
REQ-061-040 E2E tests SHALL cover the full edit workflow and the checkpoint/rollback flow. |
none | none |
REQ-061-105 Critical paths SHALL have 100% test coverage. |
none | none |
REQ-061-106 Component logging SHALL log all major operations with appropriate log levels, include... |
none | none |
REQ-061-107 Performance metrics SHALL comprise operation duration histograms, request/error rate... |
none | none |
REQ-061-108 Distributed tracing SHALL propagate traces across component boundaries, carry span... |
none | none |
REQ-061-109 Critical alerts SHALL fire on error rate spikes, performance degradation, resource... |
none | none |
REQ-061-110 The operational dashboard SHALL present real-time system health, performance trends,... |
none | none |