| Filename | Latest commit message | Latest commit date |
|---|---|---|
d14f583d92
The repository tracks the latest stable Rust, pinned at the root. A
`rust-version` key states a *floor* -- the oldest toolchain a crate supports --
which is a different promise, and one this repository does not make. It also
said 1.97 while the pin was 1.98.0 and nothing verified it, so it was a claim in
the wrong direction and unchecked in both.
So it goes, everywhere:
59 rust-version = "1.97" (workspace and package declarations)
417 rust-version.workspace = true (members inheriting them)
476 files, 476 deletions, 0 insertions
The 417 are why this is not the sixty-file change it looks like from a grep for
the value. A member inheriting a key that no longer exists does not fall back to
a default -- its manifest stops resolving. Removing the declarations without the
inherits would have broken every workspace that has members.
Deliberately untouched: `joule-code-rs/vendor/wtransport/Cargo.toml`. That is a
vendored third-party crate declaring a floor about itself, not about us, and our
pin is above it. Editing vendored source to satisfy our own policy would make
the copy diverge from upstream for no benefit.
Verified rather than assumed:
- all 493 `Cargo.toml` files in the tree parse (`tomllib`)
- `cargo metadata --no-deps --locked` resolves on `joule-code-rs`, `wai-rs`,
`openpay`, `mesh-rs`, `sandbox-rs` and `jcp-rs` -- the check that actually
exercises workspace inheritance, which a TOML parse does not
- no `Cargo.lock` changed; `rust-version` is not lockfile state
`wai/wai-verify/Cargo.toml` already carried a comment saying it omits
`rust-version` on purpose, so this makes the rest of the tree agree with the one
crate that had already decided.
What this gives up, stated plainly: cargo can no longer greet an older
toolchain with "requires rustc 1.97" and will instead fail wherever the code
first needs something newer. That is the cost of not maintaining a floor, and
it is the right cost when the floor was fiction.
Co-Authored-By: Claude Opus 5 <[email protected]>
|
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
jouleclaw-otel-genai
Scope: Typed reference of the OTel GenAI gen_ai.* semantic
conventions + JouleClaw jouleclaw.* extensions. Data types
only.
Relation to jouleclaw-otel
This crate and jouleclaw-otel overlap by design:
| Crate | Layer | Surface |
|---|---|---|
jouleclaw-otel-genai (this crate) |
Typed-attribute reference | GenAiOperation, GenAiSystem, GenAiSpanAttrs, JouleclawSpanAttrs, OperationSpan |
jouleclaw-otel |
Projection layer | receipt_to_span(...), verdict_to_span(...), emits SpanData with the same attribute names as raw strings |
jouleclaw-otel predates this crate and is the projection
authority — it knows how to walk every JouleClaw receipt shape
and emit a span. This crate is the namespace authority —
upstream callers (e.g. jouleclaw-openinference)
who need typed safety on gen_ai.* keys use this crate's enums
to avoid string typos.
Both can coexist because their consumers are different:
- A direct OTel emitter consumes
jouleclaw-oteland never sees typedGenAiOperation. - An OpenInference / Arize / Phoenix superset emitter consumes this crate's types and emits its own attribute pairs.
Neither crate should be deleted; the duplication risk is the
attribute names drifting between the two. The convention: when
you add a new gen_ai.* key, add it to this crate's enums first,
then mirror it as a string in jouleclaw-otel.
Honest scope
This crate ships:
GenAiOperation { Chat | TextCompletion | Embeddings | ToolCall | Code | ImageGen | Speech }GenAiSystem { OpenAi | Anthropic | Google | Cohere | Mistral | Meta | Jouleclaw | Other(String) }GenAiSpanAttrswith builder +to_otel_attrs() -> Vec<(String, Value)>JouleclawSpanAttrs(tier, joules_uj, energy_provenance, receipt.schema, receipt.content_hash, oracle.verdict, cascade.depth, cache.hit)OperationSpancombining both namespaces
All tests pass.