Git Identity

How Soma enforces git attribution. This behavior is built into soma-guard.ts — editing this file won't change the enforcement. This protocol helps you understand and configure it.

TL;DR

The guard watches your git commits. If the email doesn't match what's in settings.guard.gitIdentity.email, you get a warning before it goes through. This prevents committing as the wrong identity — especially in multi-project setups where global and project git configs conflict. Set your expected email(s) in settings.json once and forget about it.

How It Works

The guard extension (soma-guard.ts) intercepts bash commands. When it detects git commit:

1. Reads git config user.email from the current repo
2. Compares against settings.guard.gitIdentity.email
3. If empty → warns "git user.email is not set"
4. If mismatch → warns with expected vs actual
5. Warning fires once per session (not on every commit)

This runs automatically — no protocol loading needed.

Settings

// Single email — warns if current git email differs
{
  "guard": {
    "gitIdentity": {
      "email": "you@example.com"
    }
  }
}

// Multiple emails — warns if current email isn't in the list
// Useful when you switch between accounts (personal + work)
{
  "guard": {
    "gitIdentity": {
      "email": ["you@personal.com", "you@company.com"]
    }
  }
}

// Disable — only warns if email is completely empty
{
  "guard": {
    "gitIdentity": null
  }
}

Project settings override global. Set different emails for different contexts:

Project	Email(s)	settings.json
Personal	you@gmail.com	~/projects/blog/.soma/settings.json
Work	you@company.com	~/work/app/.soma/settings.json
Mixed (collab)	["you@gmail.com", "you@company.com"]	~/shared/project/.soma/settings.json
Global default	you@personal.com	~/.soma/settings.json
No enforcement	null	any settings.json

Identity Zones

Define your zones — each maps to a name/email pair:

Zone	When	Example
Personal	Your own projects, open source	Your Name <you@example.com>
Business	Client work, company repos	Company <team@company.com>
Agent	Autonomous commits only (CI, auto-update)	Agent <agent@example.com>

Agent-Assisted vs Autonomous

• Human directs agent → human identity. You're the author, agent is the tool.
• Agent acts alone (scheduled, auto-maintenance) → agent identity with Co-authored-by: Human <email>.

Fix Misattribution

Before push: git commit --amend --author="Name <email>" --no-edit

Source

• Guard enforcement: extensions/soma-guard.ts (line ~337)
• Settings: core/settings.ts → guard.gitIdentity
• Default: null (no check until configured)

---

Git Identity Protocol

TL;DR

Identity zones: personal, business, agent — each maps to name/email. Check git config user.email before first commit. Fix: git commit --amend --author.

Rule

Every commit must be attributed to the correct identity. Define your zones:

Identity	When	Example
personal	Your own projects, open source	Your Name <you@example.com>
business	Client work, company repos	Company <team@company.com>
agent	Autonomous commits only (CI, auto-update)	Agent <agent@example.com>

Before First Commit

git config user.email
# If wrong:
git config user.name "Your Name"
git config user.email "you@example.com"

Agent-Assisted vs Autonomous

• Human directs agent → human identity. You're the author, agent is the tool.
• Agent acts alone (scheduled, auto-maintenance) → agent identity with Co-authored-by: Human <email>.
• Never commit as agent when a human is driving the session.

Fix Misattribution

Before push: git commit --amend --author="Name <email>" --no-edit

After push: git filter-branch + force-push (solo repos only — never on shared branches).

When to Apply

• First commit in any repo
• After cloning a new repo
• After noticing wrong author in git log
• When setting up CI/CD commit identity

When NOT to Apply

• Third-party repos where you're using their contribution identity
• Forks where upstream expects a specific email

---

Git Identity Protocol

TL;DR

• Define identity zones: personal, business, agent — each maps to a name/email
• Check git config user.email before first commit in any repo
• Human drives → human identity. Agent acts alone → agent identity with Co-authored-by
• Fix before push: git commit --amend --author="Name <email>" --no-edit

Rule

Every commit must be attributed to the correct identity. Define your zones:

Identity	When	Example
personal	Your own projects, open source	Your Name <you@example.com>
business	Client work, company repos	Company <team@company.com>
agent	Autonomous commits only (CI, auto-update)	Agent <agent@example.com>

Before First Commit

git config user.email
# If wrong:
git config user.name "Your Name"
git config user.email "you@example.com"

Agent-Assisted vs Autonomous

• Human directs agent → human identity. You're the author, agent is the tool.
• Agent acts alone (scheduled, auto-maintenance) → agent identity with Co-authored-by: Human <email>.
• Never commit as agent when a human is driving the session.

Fix Misattribution

Before push: git commit --amend --author="Name <email>" --no-edit

After push: git filter-branch + force-push (solo repos only — never on shared branches).

When to Apply

• First commit in any repo
• After cloning a new repo
• After noticing wrong author in git log
• When setting up CI/CD commit identity

When NOT to Apply

• Third-party repos where you're using their contribution identity
• Forks where upstream expects a specific email