oxios 1.0.0

Oxios Agent OS — Agent Operating System powered by oxi-sdk
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

# Contributing to Oxios

Thank you for your interest in contributing to Oxios! This guide will help you get started.

## Development Setup

```bash
# Build everything
cargo build

# Run all tests
cargo test --workspace

# Check formatting
cargo fmt --all -- --check

# Run clippy
cargo clippy --workspace -- -D warnings

# Security audit
cargo audit
```

## Architecture

Oxios is an **Agent Operating System** in Rust. Key components:

| Crate | Purpose |
|-------|---------|
| `oxios-kernel` | Core: supervisor, scheduler, event bus, tools, memory |
| `oxios-ouroboros` | Spec-first protocol: interview → seed → execute → evaluate → evolve |
| `oxios-gateway` | Channel-agnostic message hub |
| `oxios-web` | Web dashboard (Axum backend + Dioxus/WASM frontend) |
| `oxios-cli` | CLI channel |
| `oxios-telegram` | Telegram channel |

**Dependency graph:** `oxios → oxios-kernel → oxi-sdk (crates.io)`

## Code Conventions

- **Language:** Code, comments, docs, commits — English. User-facing messages — Korean.
- **Rust:** `#![warn(missing_docs)]` on public crates. `anyhow` for apps, `thiserror` for libs.
- **Error handling:** Use `?` operator or `.context()?`. Avoid `.unwrap()` in production code — use `.expect("invariant description")` only for provably-safe cases.
- **Naming:** Crates `oxios-<component>`, public API `verb_noun`.
- **Testing:** Unit tests in `#[cfg(test)] mod tests`. Integration tests in `tests/` per crate.
- **Commits:** `<type>(<scope>): <description>` — scopes: kernel, ouroboros, gateway, web, cli, docs.

## Adding a New Tool

1. Define in `crates/oxios-kernel/src/tools/<name>_tool.rs`
2. Register in `tools/kernel_bridge.rs::register_all_kernel_tools()`
3. Test with `cargo test -p oxios-kernel`
4. Audit the execution path in `access_manager/` if sensitive

## Pull Request Process

1. Ensure `cargo fmt --all -- --check` passes
2. Ensure `cargo clippy --workspace -- -D warnings` passes
3. Ensure `cargo test --workspace` passes
4. Ensure `cargo audit` has no unfixed vulnerabilities
5. Update CHANGELOG.md if applicable

## Getting Help

- Open an issue on GitHub
- Read `docs/ARCHITECTURE.md` for system design
- Read `AGENTS.md` for the full codebase overview