reasonkit 0.1.6

The Reasoning Engine — Complete ReasonKit Suite | Auditable Reasoning for Production AI
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

# Contributing to ReasonKit

Thank you for your interest in contributing to the ReasonKit meta-crate!

This repository serves as the unified entry point for the ReasonKit ecosystem. Most contributions should likely be directed to the specific component repositories:

- [reasonkit-core](https://github.com/reasonkit/reasonkit-core) - The Reasoning Engine
- [reasonkit-mem](https://github.com/reasonkit/reasonkit-mem) - Memory Infrastructure
- [reasonkit-web](https://github.com/reasonkit/reasonkit-web) - Web Sensing Layer
- [reasonkit-org](https://github.com/reasonkit/reasonkit-org) - Task Orchestration

## Quick Start

```bash
# Clone the repository
git clone https://github.com/reasonkit/reasonkit
cd reasonkit

# Run tests
cargo test

# Run clippy
cargo clippy -- -D warnings

# Format code
cargo fmt
```

## The 5 Gates of Quality

All contributions must pass **The 5 Gates of Quality**:

1. **Build**: `cargo build --release` (Exit 0)
2. **Lint**: `cargo clippy -- -D warnings` (0 errors)
3. **Format**: `cargo fmt --check` (Pass)
4. **Test**: `cargo test --all-features` (100% pass)
5. **Bench**: `cargo bench` (No regression > 5%)

## Pull Request Process

1. Fork the repository.
2. Create a feature branch.
3. Make your changes.
4. Ensure all 5 gates pass.
5. Commit with a clear message.
6. Push and open a PR.

## Code Style

- Follow standard Rust conventions.
- Use `cargo fmt`.
- Document public APIs.
- Use `Result` for error handling.

## Questions?

Open an issue or reach out at [team@reasonkit.sh](mailto:team@reasonkit.sh).

---

_Part of the ReasonKit Ecosystem_