receipt-benchrust:receipt-bench
RESOLVING ROUTEFollowing the evidence boundary…
Replayable benchmark substrate for semantic search, compression, and memory operations
receipt-bench Replayable benchmark substrate for Rust projects. Captures structured receipts timestamped and keyed to commit hash + machine fingerprint, enabling diffs between runs.
receipt-benchrust:receipt-bench
Library target · no binary target
root · root member
Evidence source: package-manifest
These statements are preserved from package metadata and documentation recovered by the audit. They describe intended scope, not independent performance verification.
replayable benchmark suites
machine and commit fingerprints
structured benchmark receipts
receipt diffs
The graph distinguishes outgoing sibling dependencies, derived inbound dependents, and explicitly recorded related packages. Lines describe catalog relationships—not execution order or runtime activation.
No direct sibling dependency was declared.
No inbound sibling dependency was derived from this catalog.
No additional related package was recorded.
Manifest-level facts remain separate from documentation claims and registry observations, keeping each evidence source legible.
No named Cargo feature groups were recorded.
The exact package name appears in the observed RecursiveIntell crates.io owner inventory.
No publish=false gate is declared; this does not prove the package is published to crates.io.
Maturity is a catalog status supported by observed signals. It is not a security review, service-level commitment, correctness proof, or suitability determination.
No package-specific limitation was recorded. That absence is not evidence of readiness, correctness, or zero risk.
Phase 5: Final audit — cargo fmt cleanup
0e621009013a7366bb40f6b21274f2aea0fbf1a1Commit-search evidence is package-name based and may not equal the exact last path modification.
Inspect matched commit ↗RecursiveIntell/Libraries is private; monorepo source links require authorization.
Package manifests, package READMEs, crate-level docs, workspace status files, and package-name commit search. No source implementation bodies or secrets are reproduced.
p32-schema-compat / 011027f77fc7a53c6ecb05300d5c34144370fa3b