Cohesive is a library suite for semantic system definition and orchestration of existing infrastructure. It favors defining the meaning of a system first, then attaching interpretations for storage, APIs, presentation, workflows, AI, training, and provider-specific infrastructure.

System-wide architectural documentation starts at the Cohesive documentation index. Detailed package docs live beside each package under src/*/README.md and are included in the corresponding NuGet package.

For a concise account of the adoption cost, incremental entry points, and compounding benefits across blocks, see Why Use Cohesive Blocks?.

The Execution Kernel compatibility inventory records the current Transitions and Processes behavior against the normative EK-01 through EK-09 scenarios.

The Execution Kernel adoption and migration guide maps package ownership, the canonical execution lifecycle, executable examples, and replacements for retired execution surfaces.

TypeScript packages live under src/frontend/* and publish under the @cohesivesystems/* npm scope. See src/frontend/README.md for package details.

• .NET SDK 10 (net10.0)
• Node.js 24
• pnpm 11 through Corepack

dotnet restore Cohesive.sln
dotnet build Cohesive.sln -c Release
dotnet test Cohesive.sln

corepack enable
corepack prepare pnpm@11.1.3 --activate
corepack pnpm install --frozen-lockfile
corepack pnpm frontend:build
corepack pnpm frontend:test

Create local NuGet packages for downstream applications:

./eng/pack-local.sh

The script writes a uniquely versioned 0.1.0-dev.<timestamp> package set to the shared sibling feed at .feeds/nuget/cohesive-local. Pass an explicit version as the first argument when needed. Local packages include portable PDBs beside their assemblies, allowing IDE navigation to resolve back to the editable files in this checkout.

Point downstream applications at the local NuGet feed:

dotnet nuget add source ../.feeds/nuget/cohesive-local --name cohesive-local

Reference Cohesive packages with the floating development version 0.1.0-dev.*. After changing Cohesive, package it again and force downstream restore evaluation so NuGet selects the new immutable package version:

./eng/pack-local.sh
dotnet restore /path/to/Consumer.sln --force-evaluate

Do not overwrite an existing local package version. NuGet caches restored packages by ID and version, so a new version is required for source and binary changes to propagate reliably.

Start a local npm feed in one terminal:

corepack pnpm npm:feed

Publish local npm packages from another terminal:

corepack pnpm npm:publish-local 0.1.0-dev.local

Point the downstream app at the local npm feed:

@cohesivesystems:registry=http://localhost:4873/

The public package repository itself should keep .npmrc pointed at https://registry.npmjs.org/. Local feed routing belongs in consuming app repositories.

Use one repo-wide version for NuGet and npm packages until the package graph needs independent release lines.

corepack pnpm version:set 0.1.0-alpha.2

Version conventions:

The release-packages workflow publishes packages from a tag such as v0.1.0-alpha.2 or from a manual workflow run with the version input 0.1.0-alpha.2.

• NuGet packages publish with NuGet trusted publishing through NuGet/login.
• npm packages are packed with pnpm, then published to npmjs.org with npm trusted publishing.
• npm prerelease dist-tags map as follows: alpha.* to alpha, preview.* to preview, rc.* to rc, and other prereleases to next.
• Stable npm versions publish with the latest dist-tag.

Required GitHub secret:

NUGET_USER=<nuget.org trusted-publishing policy creator username>

The NuGet trusted publishing policy should use repository owner cohesivesystems, repository cohesive, workflow file release-packages.yml, and a blank environment unless the workflow later adds an explicit GitHub environment.

Before the first npm trusted-publishing release, each @cohesivesystems/* package must already exist on npmjs.com. Bootstrap each package once with a temporary/manual publish, then configure npm trusted publishing for the cohesivesystems/cohesive repository and release-packages.yml workflow.

Apache-2.0