Rustrootv0.1.0

verification-policy

Canonical verification policy and approval artifacts

View verified registry record ↗Inspect dependency lens ↓

01 · Documented scope

What this package says it does.

verification-policy Canonical verification policy, approval, and execution-permit artifacts.

Package identityverification-policyverification-policy

rust:verification-policy

Contract shapeLibrary

Library target · no binary target

Workspace positionRoot

root · 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
policy decisions
02
execution permits and commit tokens
03
approval artifacts
04
citation context

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 · 3

llm-tool-runtimeLLM and model integrations
stack-idsContracts, schemas, and identity
verification-controlVerification, governance, and authority

Used by · 7

forge-pilotAgent orchestration and execution
contract-schema-genContracts, schemas, and identity
kernel-conformanceInference kernel and constraints
aidens-integration-testsSupporting library infrastructure
aidens-governance-kitVerification, governance, and authority
profile-runtimeVerification, governance, and authority
verification-adjudicationVerification, governance, and authority

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 GROUPS0 RECORDED

No named Cargo feature groups were recorded.

05 · Publication evidence

RecursiveIntell-owned crates.io release.

The exact package name appears in the observed RecursiveIntell crates.io owner inventory.

Evidence state key: publishedManifest publish: Not applicable / not establishedCargo publish allowed by default: YesRegistry history present: YesRegistry ownership verified: YesExact-name registry match: Yes

No publish=false gate is declared; this does not prove the package is published to crates.io.

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.

StatusEarly Development

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

Known limitations0 recorded

No package-specific limitation was recorded. That absence is not evidence of readiness, correctness, or zero risk.

Update evidenceJul 16, 2026

Fix/hostile remediation 20260715 (#2)

Method: repository commit search matched the package name
Matched SHA: 011027f77fc7a53c6ecb05300d5c34144370fa3b

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…

RecursiveIntell-owned crates.io release.

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.