Anyam design philosophy.

Keep Git honest

Repositories, commits, branches, tags, clone, fetch, push, diff, and merge keep their Git meanings. Anyam adds a term only when the Project needs a meaning Git does not own.

A Pull Request is a compatibility view over a Change. A merge can participate in Landing. A check summarizes Evidence.

Put the Project above one repository

A Project can contain several repositories, Source Spaces, modules, Artifacts, Releases, and Targets. A repository stores Git objects. It does not decide which source is visible, who may change it, or what may reach production.

Make disclosure structural

Public and private source live in separate Source Spaces. A public Project View contains a real public Git lineage. It does not contain private objects, paths, identifiers, history, or activity.

Anyam verifies disclosure integrity. It does not claim that every public projection is functionally complete.

Separate editing from authority

An editor or coding agent works in an isolated Workspace. The agent can publish a Change Revision, but it cannot write canonical Project state. Landing checks policy, review, and Evidence before the canonical revision moves.

Build → Artifact
Artifact + Evidence + policy → Release
Release + Target → Promotion

Treat Evidence as a claim with a receipt

A Run uses exact source, dependency, toolchain, environment, and policy inputs. It produces Evidence with a digest and a validity rule. A green badge, agent summary, or human assertion is not Evidence by itself.

Give every actor narrow authority

The authority chain is explicit:

Principal → Actor → Session → Task → Capability Grant

Human and agent operations use the same policy model. Credentials have an audience, a resource, an operation, and an expiry.

Stay open and portable

The complete first-party product is open source. Customer-operated mode runs in the customer's Cloudflare account, and Project history remains exportable if a provider changes or disappears.

Prefer the obvious path

The routine path should be clear to a developer and to an agent:

create or import → inspect → change → verify → review → land → release → promote

When policy blocks an operation, the error names the rule, the current state, the missing requirement, and the next permitted action.