vole

Clone

Read only, no credentials:

https://rodent.software/git/vole.git

Write over SSH with a registered key:

git clone ssh://git@0.0.0.0:2222/vole.git

A free and open-source forge that lives in your Git repo.

Identify accounts by their registered name

62576fa8157d431dcf2d360f3ebe481de77bda03 · Keenan Nemetz · 14d ago · parent 642e5994

Identify accounts by their registered name

Drop the internal account id and display name. Users, keys, passkeys,
invites, sessions, ACL entries, approvals, locks and CI records now all
use the registered name as the single identity.

The roster migrates in place: old id-keyed tables are rebuilt around the
name, and access-rule/lock references are rewritten through the same
mapping. Display-name editing and whoami --id are removed.

docs/architecture.md +4−5

@@ -16,10 +16,9 @@ Vole uses one rule everywhere:
	16	16	> A credential proves which account you are. Vole checks every change before
	17	17	> accepting it, and records the decision in `data/audit.log`.
	18	18
	19		There are two credentials, and they resolve to the same account: a name fixed
	20		at creation, which contributor branches and metadata authors are written with, and
	21		an internal id, which access rules and approval files are keyed by. A
	22		display name is a third, purely presentational label that anyone may change.
		19	There are two credentials, and they resolve to the same account: the name
		20	fixed at creation. Contributor branches and metadata authors are written with it,
		21	and access rules, approval files, locks and CI records are keyed by it.
	23	22
	24	23	- an SSH key for Git over SSH, administration, and CI;
	25	24	- a passkey for browser sessions.
@@ -76,7 +75,7 @@ issues/<ulid>/issue.md
	76	75	issues/<ulid>/comments/<ulid>.md
	77	76	requests/<ulid>/request.md
	78	77	requests/<ulid>/comments/<ulid>.md
	79		requests/<ulid>/approvals/<account-id>.md
		78	requests/<ulid>/approvals/<account-name>.md
	80	79	releases/<tag>/<artifact>
	81	80	runs/<run-id>/<attempt>/...
	82	81	```