hyphae-pliegors 0.1.0

Optional public-contract adapter between PliegoRS and Hyphae.
Documentation 
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

<p align="center"><a href="https://hyphae.dev"><img alt="Hyphae" src="https://raw.githubusercontent.com/celiumsai/hyphae/main/.github/assets/hyphae-lockup.svg" width="320"></a></p>

# hyphae-pliegors

[![crates.io](https://img.shields.io/crates/v/hyphae-pliegors?logo=rust)](https://crates.io/crates/hyphae-pliegors)
[![docs.rs](https://img.shields.io/docsrs/hyphae-pliegors)](https://docs.rs/hyphae-pliegors)

Optional public-contract adapter between PliegoRS applications and the
[Hyphae](https://hyphae.dev) `/v1` API.

```toml
[dependencies]
hyphae-pliegors = "0.1.0"
```

The crate depends on `hyphae-client`, not PliegoRS internals or Hyphae storage.
Omit it and the host application continues to build and run without Hyphae.

When neither `HYPHAE_BASE_URL` nor `HYPHAE_BEARER_TOKEN` exists,
`PliegoHyphaeConfig::from_env()` returns `Ok(None)`. A PliegoRS application can
therefore keep Hyphae completely absent. When enabled, the application owns
the decision to place the cloneable `PliegoHyphae` value into its public state
mechanism.

This crate intentionally does not prescribe or copy a PliegoRS internal state
API. It imports no private PliegoRS API and never opens a Hyphae data directory.

Apache-2.0. Source and integration boundary:
[`celiumsai/hyphae`](https://github.com/celiumsai/hyphae).