ac-qu-ai-nt is a project I'm working on, using artificial intelligence to break down the user's query, acquire knowledge, and transfer insights to the user('s mind).

This is a placeholder while I take small steps to build out the project.

Contributing

This is a summary of the crates I expect to be in this project and how they are used:

flowchart TD
core --> cli-clap
core --> gui-eframe
core --> tui-ratatui
cli-clap --> multibinary
gui-eframe --> multibinary
tui-ratatui --> multibinary

Versioning

This project aims to adhere to semantic versioning using Conventional Commits, conducted by Release-plz.

To be more specific about what a breaking change could entail:

a previously successful compilation now failing
the program (wrongly) exiting, panicking, reporting an error, etc, where it didn't previously
changing the expected result of an existing integration test (not sure if unit tests would count)

All the crates in this project have a minimum supported Rust version (MSRV) of 1.76, the release succeeding the one that stabilized async fn in traits (which the core crate of this project is expected to make use of). I intend to test this in CI (GitHub Actions) in the future to identify if it ever gets raised by changes but I have not set this up yet. Raising the MSRV will be considered a breaking change --- my justification is that it seems more appropriate for an application like this. This may be reconsidered if Cargo's MSRV-aware resolver is stabilized.