AN OPEN MODEL FOR CODE

Code has more than
one way to move.

Keystones is a new home for software projects. It replaces branch-shaped habits with a clear system of states, paths, changes, and decisions.

SPACE / 001keystones-protocol
01Corestable line
02Sideparallel path
03Changeintentional edits
04Frameimmutable state
CANOPY: 42 PIECESCORE STABLE
01 / THE PRINCIPLE

Version control should describe the work people actually do — not force every idea through the same old vocabulary.

( intent + context ) → a verifiable state
02 / THE SYSTEM

Seven keystones.
One complete picture.

Every object has a human meaning, a stable identifier, and a structured API representation. Nothing is hidden behind shell syntax.

01

Space

A project home with its own access rules and activity trail.

02

Core

The stable center of a Space; the state everyone can rely on.

03

Side

A parallel direction for focused work, not a permanent branch.

04

Frame

An immutable view of a Canvas at an exact point in time.

05

Change

A deliberate set of Pieces that move together.

06

Proposal

A reviewable request for a Change to become part of Core.

07

Beacon

A published, named state ready to share with the world.

03 / MACHINE-READABLE BY DEFAULT

Designed for tools.
Not dependent on them.

Keystones does not contain an AI assistant. It exposes clear resources and actions so any agent, connector, or MCP client can inspect a Space and make authorized changes.

KEYSTONES / MCP● ● ●
tools/list space.inspect canopy.read side.open change.create proposal.submit verdict.issue beacon.publish All output is structured.