GitHub - u2up/coordination-repository-pattern: 'Coordination Repository Pattern' home · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
Uh oh!
There was an error while loading. Please reload this page.
u2up
coordination-repository-pattern
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>5 Commits<br>5 Commits
docs
docs
LICENSE
LICENSE
README.md
README.md
View all files
Repository files navigation
Projects Have Memory Too
A Git-native architectural pattern for separating project coordination state<br>from implementation state.
Projects should own their durable coordination state, independently of the<br>agents, models, and tools that participate in the work.
This matters especially in agentic coding. Today's AI coding agents have tools,<br>memory, and orchestration.
Projects need something different:<br>durable, shared, reviewable coordination state.
The Coordination Repository Pattern does this using a dedicated Git repository.
At a glance
Humans · automation · AI agents<br>Coordination Repository<br>requirements · decisions · work status · evidence<br>links to / governs<br>Implementation Ecosystem<br>code repositories · reviews · CI · releases · docs
Why a separate repository?
A separate repository gives coordination state an independent lifecycle:
coordination changes can be reviewed without touching source branches;
one coordination domain can span one or many implementation repositories;
access, history, retention, and sensitivity rules can differ from code;
durable project state remains portable outside any one hosted tool.
Read next
Why? Agentic Coding Needs Durable Coordination State
How? Coordination Repository Pattern
Compare: Related practices and alternatives
Implementation: pi-env
About
'Coordination Repository Pattern' home
Resources
Readme
License
CC-BY-4.0 license
Uh oh!
There was an error while loading. Please reload this page.
Activity
Custom properties
Stars
stars
Watchers
watching
Forks
forks
Report repository
Releases
tags
Contributors
Uh oh!
There was an error while loading. Please reload this page.
You can’t perform that action at this time.