Rustrootv0.1.0

check-runner

Execution backend and check normalization primitives for forge-engine

View verified registry record ↗Inspect dependency lens ↓

01 · Documented scope

What this package says it does.

check-runner Role Execution backend and check normalization primitives for forge-engine

Package identitycheck-runnerPrimitives/check-runner

rust:check-runner

Contract shapeLibrary

Library target · no binary target

Workspace positionRoot

root · nested-primitives · root member

License declarationMIT

Evidence source: package-manifest

02 · Capability surface

Recorded responsibilities.

These statements are preserved from package metadata and documentation recovered by the audit. They describe intended scope, not independent performance verification.

01
check backend selection
02
process execution and normalization
03
effect signatures
04
optional container lane

03 · Dependency lens

Position in the system.

The graph distinguishes outgoing sibling dependencies, derived inbound dependents, and explicitly recorded related packages. Lines describe catalog relationships—not execution order or runtime activation.

Depends on · 4

check-runner-sysForge repair and causal evaluation
effect-signatureForge repair and causal evaluation
forge-policySecurity and boundaries
sandbox-workspaceSecurity and boundaries

Used by · 4

cea-coreForge repair and causal evaluation
cea-sqliteForge repair and causal evaluation
cea-storeForge repair and causal evaluation
forge-engineForge repair and causal evaluation

Recorded as related · 0

No additional related package was recorded.

04 · Package contract

Features, targets, and workspace state.

Manifest-level facts remain separate from documentation claims and registry observations, keeping each evidence source legible.

A / TARGETSMANIFEST AUDITED

Library target: Yes
Binary target: No
Package README: Yes
Root workspace member: Yes
Root default member: Yes
Excluded from root: No

B / FEATURE GROUPS2 RECORDED

default

Marker feature; no enabled item recorded.

container

Marker feature; no enabled item recorded.

05 · Publication evidence

crates.io release history · manifest publish=false now.

A RecursiveIntell-owned crates.io release exists, while the current audited workspace manifest explicitly disables new publication.

Evidence state key: published-disabledManifest publish: NoCargo publish allowed by default: NoRegistry history present: YesRegistry ownership verified: YesExact-name registry match: Yes

Explicitly non-publishable in Cargo.toml.

06 · Maturity and limits

Signals with their boundaries intact.

Maturity is a catalog status supported by observed signals. It is not a security review, service-level commitment, correctness proof, or suitability determination.

StatusInternal Support

Version 0.1.0.
Package README present.
Included in the root default build set.

Known limitations1 recorded

Primitives/README.md calls these internal support crates and says they have a different quality policy, although the current root manifest now includes them; treat that README position label as stale.

Update evidenceMay 28, 2026

Phase 5: Final audit — cargo fmt cleanup

Method: repository commit search matched the package name
Matched SHA: 0e621009013a7366bb40f6b21274f2aea0fbf1a1

Commit-search evidence is package-name based and may not equal the exact last path modification.

Inspect matched commit ↗

07 · Source trail

Continue the inspection.

RecursiveIntell/Libraries is private; monorepo source links require authorization.

ATLAS EVIDENCE BOUNDARY

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

RESOLVING ROUTEFollowing the evidence boundary…

crates.io release history · manifest publish=false now.

A RecursiveIntell-owned crates.io release exists, while the current audited workspace manifest explicitly disables new publication.

Explicitly non-publishable in Cargo.toml.