npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@x12i/graphenix-executable-contracts

v2.16.0

Published

Shared executable graph contracts: types, constants, error codes, and lightweight utilities.

Downloads

8,097

Readme

@x12i/graphenix-executable-contracts

Shared contracts for the Graphenix executable graph lifecycle: TypeScript types, constants, error codes, and lightweight utilities.

No validators, compilers, or adapters — only the shared vocabulary other lifecycle packages build on.

Naming policy: NAMING.md — npm scope @x12i/* vs JSON identifiers graphenix.*.

Who should use this

| Role | Use this package? | | ---- | ----------------- | | Library author needing types only | Yes | | Graph designer / Studio | Prefer @x12i/graphenix-authoring-format | | Engine | Prefer @x12i/graphenix-plan-format + @x12i/graphenix-trace-format |

Install

npm install @x12i/graphenix-executable-contracts @x12i/graphenix-core

Type index (primary)

| Domain | Key types / constants | | ------ | --------------------- | | Authoring | AuthoringGraphDocument, GraphProjectDocument | | Plan v2 | ExecutableGraphPlanV2, NodeExecutionPlan, ExecutionUnitPlan, EXECUTABLE_PLAN_FORMAT_V2 | | Plan v1 | ExecutableGraphPlan, EXECUTABLE_PLAN_FORMAT (legacy) | | Trace v2 | GraphExecutionTraceV2, TraceEvent, EXECUTION_TRACE_FORMAT_V2 | | Trace v1 | GraphExecutionTrace, EXECUTION_TRACE_FORMAT (legacy) | | Runtime | GraphRuntimeObject, StudioExecuteRequest | | Model config | AiModelSelection, CaseCondition, ModelConfigTriplet | | Units | ExecutionUnitKindV2, InvokeContract, ModelSlot | | Fact-guard | FactGuardStepConfig, AuditFactGuardConfig, AuthoringFactGuardConfig, FACT_GUARD_POLICY_IDS |

Example

import {
  EXECUTABLE_PLAN_FORMAT_V2,
  EXECUTION_TRACE_FORMAT_V2,
  type ExecutableGraphPlanV2,
  type GraphExecutionTraceV2,
  type NodeExecutionPlan,
  type CaseCondition,
  type AiModelSelection,
  execError
} from "@x12i/graphenix-executable-contracts";

Key exports

  • Constants — format ids, TASK_NODE_KIND, AI_MODEL_SLOTS, profile namespace
  • Types — authoring graph, executable plan, execution trace, case conditions, model config, runtime
  • UtilitiesisRecord, execError, getExecutableProfile, isExecutableTaskNode, …
  • Hashingsha256Hash, defaultHashFunction
  • Schemaschema/graphenix-executable-format-1.0.0.schema.json (published with package)

Dependencies

  • Peer: @x12i/graphenix-core ^2.4.0

Error codes (synthesis)

| Code | When | | ---- | ---- | | LEGACY_PRE_INPUT_STRATEGY | Authoring still has preInputStrategy / synthesisInputStrategy (warn on normalize; reject preInputStrategy on validate) | | LEGACY_SYNTHESIS_INPUT_STRATEGY_ON_PLAN | Plan unit has unitParams.synthesisInputStrategyremove; re-compile (validation fails until removed) |

Empty invokeContract.reads and unitParams.memoryPaths on PRE synthesis units is valid — runtime applies DEFAULT_PRE_SYNTHESIS_READ_PATHS (jobVariables, taskVariables, input). Layer-1 hints (narrix, webScope) are not PRE read scope.

Synthesis unitParams (plan wire)

PRE synthesis externalPreUtility units carry paths only:

{
  "memoryPaths": [],
  "autoEnableContext": true
}

When aiTaskProfile.inputSynthesis.sources is authored, compiler emits identical paths on invokeContract.reads and memoryPaths. When omitted, both are [] and ai-tasks applies the default trio at runtime.

No plan field for synthesis template key — runtime resolves from skill catalog. Future explicit per-node override (multi-template skills, P2 FR): invokeContract.synthesisContextStrategyKey (not synthesisInputStrategy).

Related packages

Part of the Graphenix Format monorepo. Lifecycle status: GAP-ANALYSIS.md.