Rustrootv0.2.0

forge-engine

Causal edit attribution and structured patch evaluation engine

View verified registry record ↗Inspect dependency lens ↓

01 · Documented scope

What this package says it does.

forge-engine Causal edit attribution and structured patch evaluation engine.

Package identityforge-engineliving-memory/living-memory

rust:forge-engine

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
compile mindstate
02
validate and apply structured patches
03
run and score checks
04
persist operational evidence and causal attribution

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

cea-coreForge repair and causal evaluation
cea-sqliteForge repair and causal evaluation
cea-storeForge repair and causal evaluation
check-runnerForge repair and causal evaluation
claim-ledgerMemory, knowledge, and provenance
effect-signatureForge repair and causal evaluation
forge-memory-bridgeMemory, knowledge, and provenance
forge-policySecurity and boundaries
llm-tool-runtimeLLM and model integrations
mindstate-coreForge repair and causal evaluation
sandbox-workspaceSecurity and boundaries
semantic-memoryMemory, knowledge, and provenance
semantic-memory-forgeMemory, knowledge, and provenance
stabilizer-coreForge repair and causal evaluation
stack-idsContracts, schemas, and identity
typed-patchForge repair and causal evaluation

Used by · 3

forge-pilotAgent orchestration and execution
kernel-conformanceInference kernel and constraints
llm-pipelineLLM and model integrations

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.

danger-sm-write

Marker feature; no enabled item 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.

StatusActive Development

Version 0.2.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-head fallback; no package-name commit-search result
Matched SHA: 011027f77fc7a53c6ecb05300d5c34144370fa3b

This proves the audited branch snapshot date, not that this package changed in the head commit.

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.