Extends thegent governance base. See platforms/thegent/dotfiles/governance/CLAUDE.base.md for canonical definitions.
- Name: heliosCLI
- Description: Rust-based CLI for managing Helios CLI applications with multi-backend support and sandboxing.
- Location: repo-relative — this checkout (
./). SeeAGENTS.mdfor the dual-workspace map (crates/harness workspace + vendoredcodex-rs/). - Language Stack: Rust (root edition 2021; vendored codex-rs edition 2024)
- Published: Internal
All work MUST be tracked in AgilePlus:
- Reference: a sibling checkout of the AgilePlus repo (e.g.
$HOME/AgilePlusor a sibling directory — never a machine-specific path) - CLI:
cd <agileplus-checkout> && agileplus <command>
- Check for AgilePlus spec before implementing
- Create spec for new work:
agileplus specify --title "<feature>" --description "<desc>" - Update work package status:
agileplus status <feature-id> --wp <wp-id> --state <state> - No code without corresponding AgilePlus spec
- Feature branches in
repos/worktrees/<project>/<category>/<branch> - Canonical repository tracks
mainonly - Return to
mainfor merge/integration checkpoints
All markdown files must use UTF-8.
From this repository root:
cargo test --all
cargo clippy --all-targets -- -D warnings
cargo fmt --checkAll tests MUST reference a Functional Requirement (FR):
// Traces to: FR-HELIOS-NNN
#[test]
fn test_feature_name() {
// Test body
}Verification:
- Every FR in FUNCTIONAL_REQUIREMENTS.md MUST have >=1 test
- Every test MUST reference >=1 FR
- Run:
cargo testto verify
heliosCLI provides a comprehensive CLI for Helios CLI application management with multiple execution backends:
src/
├── main.rs # CLI entrypoint
├── commands/ # Command handlers
├── config/ # Configuration loading
├── execution/ # Backend executors (Docker, Kubernetes, Local)
├── app/ # Core application logic
├── models/ # Data models
└── utils/ # Utilities
# Build release binary
cargo build --release
# Run with help
./target/release/helios-cli --help
# Run in development
cargo run -- <command>- Multi-backend execution support (Docker, Kubernetes, Local, Sandbox)
- TUI-based application management and monitoring
- Comprehensive logging and error handling
- Type-safe configuration management
- All CLI commands derive from
clapwith subcommands - Error types use
thiserrorfor clear error propagation - Async runtime:
tokiofor concurrent operations - All public types are documented with examples
- Tests are inline with source files
- Command Pattern: Each CLI command is a self-contained handler
- Builder Pattern: Configuration builders for complex types
- Strategy Pattern: Pluggable execution backends
- Adapter Pattern: Backend-specific implementations
| Principle | Description | Application |
|---|---|---|
| SOLID | Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion | Commands are single-purpose; backends implement trait interface |
| DRY | Don't Repeat Yourself | Shared utilities in src/utils/ |
| KISS | Keep It Simple, Stupid | Clear command structure, minimal abstractions |
| YAGNI | You Aren't Gonna Need It | Build features as needed |
See thegent governance base for:
- Complete CI completeness policy
- Phenotype Git and Delivery Workflow Protocol
- Phenotype Org Cross-Project Reuse Protocol
- Phenotype Long-Term Stability and Non-Destructive Change Protocol
- Worktree Discipline guidelines
Location: platforms/thegent/dotfiles/governance/CLAUDE.base.md