Sign In

@decantr/core

Package Overview
Dependencies
Maintainers
1
Versions
34
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@decantr/core - npm Package Compare versions

Comparing version
3.9.4
 to
3.10.0
+2
-2
package.json

@@ -7,3 +7,3 @@ {

"dependencies": {
"@decantr/content": "3.9.4",
"@decantr/content": "3.10.0",
"@decantr/essence-spec": "3.8.1"

@@ -73,3 +73,3 @@ },

"types": "dist/index.d.ts",
"version": "3.9.4"
"version": "3.10.0"
}
+7
-4
README.md

@@ -10,2 +10,4 @@ # @decantr/core

Decantr 3.10.0 is the current stable line, centered on **Observe -> Prepare -> Verify -> Report**. Core graph and pack primitives support that work, but a graph, route rank, or larger context pack does not by itself prove production authority or model improvement. Routes are one UI surface among layouts, components, stories, overlays, flows, packages, runtime states, and exact source files.
## Install

@@ -33,3 +35,3 @@

The graph exports establish the storage boundary, typed schema shape, temporal snapshot/diff shape, payload-filterable node queries, hybrid route-context ranking, hybrid node/source impact traversal, and provider-neutral contract capsule shape for CLI, MCP, verifier, Studio, and CI integration. Ranking blends deterministic weighted traversal with local personalized PageRank and optional task-text boosts, so central graph nodes and task-relevant nodes both surface without introducing a graph database dependency. Behavior obligations remain app-owned local law in `.decantr/local-patterns.json`; higher-level packages project accepted obligations into existing `LocalRule` graph nodes with `payload.kind = "behavior-obligation"` instead of adding a new graph node type. Evidence Bundles, runtime probes, visual manifests, repair plans, and proof reports are ingested through existing graph node/edge shapes where possible; generated health-baseline diffs are excluded to avoid circular graph invalidation, and `TEST_COVERS_NODE` edges act as verification hints rather than proof of production UI behavior. The capsule keeps the contract cache key stable while listing bounded SourceArtifact paths agents can use for file-impact follow-up queries. The core package remains pure library code: filesystem graph persistence belongs in higher-level packages such as the CLI.
The graph exports establish the storage boundary, typed schema shape, temporal snapshot/diff shape, payload-filterable node queries, route-context ranking, node/source impact traversal, and provider-neutral contract capsule shape for higher-level integrations. Ranking is deterministic supporting evidence; it cannot promote an inferred, ambiguous, test-only, generated, or stale source into production authority. Behavior obligations remain app-owned local law in `.decantr/local-patterns.json`. Evidence Bundles, runtime probes, visual manifests, repair plans, and proof reports reuse existing graph shapes where possible; generated health-baseline diffs are excluded to avoid circular graph invalidation, and `TEST_COVERS_NODE` edges are verification hints rather than proof of production UI behavior. The core package remains pure library code: filesystem graph persistence belongs in higher-level packages such as the CLI.

@@ -41,5 +43,6 @@ ## FAQ

```bash
npx @decantr/cli new my-app
npx @decantr/cli analyze
npx @decantr/cli check
npx @decantr/cli scan
npx @decantr/cli adopt --yes # only after reviewing the observed authority
npx @decantr/cli task /known-route "describe the UI change"
npx @decantr/cli verify
```

@@ -46,0 +49,0 @@