Problem
Intent is repeated
Domain meaning is copied into several layers. Each copy can drift.
Cohesive Systems
Cohesive is a semantic compilation platform for authoring durable system meaning as readable artifacts and accumulating it into an executable semantic system graph.
Building Blocks
Each Cohesive block contributes capabilities to the system graph (state transitions, relations, workflows, APIs, UIs, infrastructure, agent context, etc).
public sealed class ShipmentShape : Shape
{
public ShipmentShape()
{
Identity(nameof(Shipment.Id));
Field<TenantId>(nameof(Shipment.TenantId));
Field<ShipmentStatus>(nameof(Shipment.Status));
}
}The problem
Modern systems express the same decisions in many places: schemas, services, APIs, interfaces, jobs, and documentation.
As the system evolves, those expressions drift apart and the reasoning that connects them disappears into files, frameworks, and conventions. AI increases the pace of change without making the resulting system easier to understand.
Problem
Domain meaning is copied into several layers. Each copy can drift.
Problem
Behavior hides in framework conventions and local assumptions. The system's semantics are hard to inspect.
Problem
Without explicit semantic source, agents infer intent from code, tests, documentation, and conventions. Those signals may be incomplete, stale, or contradictory.
Cohesive captures system meaning in a directly inspectable graph authored through readable semantic artifacts. The graph expresses structure, behavior, constraints, interfaces, runtime requirements, and agent context. A deterministic compiler turns that model into supported code and runtime artifacts.
Together, the artifacts form a connected graph that people, agents, and compilers can inspect through views suited to their work.
Step 1
Define accepted system meaning, including its constraints and operational obligations, through modular, readable, and reviewable Cohesive artifacts.
Step 2
Resolve identities and relationships across the graph, then evaluate dependencies, consistency, capability requirements, and affected regions.
Step 3
Compile the graph into supported executable artifacts and compare those realizations with their semantic requirements.
Graph-first
Code-derived graphs help navigation, but they are still reverse engineering. They explain code after it already exists.
Cohesive artifacts are authored first. They carry explicit semantics and compile into a graph that can generate or check code and runtime artifacts.
Code-derived graph
Inferred graphs help humans navigate code, but they remain downstream and inherit its gaps.
Cohesive source
Readable semantic artifacts compile into graph state that can check constraints, guide change, and drive supported projections.
Migration can start from existing code, but the destination is not a permanent mirror. The destination is explicit semantic source whose accumulated graph can govern implementation.
Agents use the same graph at build time and runtime.
Build time
Use the graph as structured context for generating, refactoring, and testing code from declared semantics.
Runtime
Use the graph to understand allowed actions, effects, permissions, evidence, approval boundaries, and recovery paths.
Semantic layer
Cohesive does not replace your database, cloud, frontend, workflow engine, IDE, or agent tool. It defines the semantic layer they can read from and write back to.
The graph describes what the system is; the compiler projects it into the technologies teams already use.
Explore
Start with the building blocks and see graph-authored semantics become code and runtime artifacts.
Direction
Read how semantic system graphs change authoring, operations, and AI context.
Contact
Share what you are building or ask about applying Cohesive to an existing system.