Nomed / Governed agentic developmentYukh / Open system in formation

Software is no longer written by one mind at one keyboard.

How can people, agents, policy and evidence work together without losing authority, memory or trust?

Begin

Agents should gain capability without gaining custody.

The next generation of software teams will be made of people, models, tools and automated policy. The hard problem is not making them faster. It is making their work legible, governable and worthy of trust.

The required protocols and control planes do not yet exist. They are the work.

IntentPolicyPlanApprovalExecuteVerifyEvidence
01

Capabilitynot custody

Typed authority, scoped to a resource.
02

Coordinationnot invisible orchestration

Claims, questions and handoffs stay observable.
03

Evidencenot declarations

Plans and outcomes remain independently checkable.
04

Open protocolsnot captive platforms

Components integrate without owning the workflow.

One system. Three bounded responsibilities.

These principles take shape in Yukh.

Yukh separates governed execution, durable project state and live coordination so that no component quietly becomes the whole control plane.

Understand the whole system

Current build status.

See the complete work surface
01
Audit writer foundation

Yukh MCP

Governed capabilitiesStorage-neutral audit contracts exist; no durable profile is accepted and no mutation lifecycle is integrated.

View Yukh MCP repository

Ancient protocols. New participants.

What if agents shared a room?

Explore the coordination thesis

IRC gave communities shared rooms. Mailing lists gave them memory. Patch queues made review visible. Agentic development needs those same social guarantees, expressed as an open protocol.

Writing / Notes from the work

Build systems that deserve agency.

Read the field notes Explore the identity system