<?xml version="1.0" encoding="UTF-8"?>
<spec xmlns="https://vibevm.org/spec/1">
  <title id="root">Package manifest</title>
  <status stage="doc" state="work" audience="user,dev"/>
  <p p="1">What `org.vibevm.world/git-atomic-commits@1.0.0` declares about itself. Everything on this page is the package's own manifest, read and shown — nothing here is an opinion about the package.</p>
  <table p="2">
    <tr>
      <td>Field</td>
      <td>Value</td>
    </tr>
    <tr>
      <td>Coordinate</td>
      <td>`org.vibevm.world/git-atomic-commits`</td>
    </tr>
    <tr>
      <td>Version</td>
      <td>`1.0.0`</td>
    </tr>
    <tr>
      <td>Kind</td>
      <td>`flow`</td>
    </tr>
    <tr>
      <td>Licence</td>
      <td>UPL-1.0</td>
    </tr>
    <tr>
      <td>Summary</td>
      <td>Atomic commits discipline: one commit = one logical idea — how to split a mixed working tree, when to batch, and why atomicity matters more in a human-AI team (the message FORMAT is the separate conventional-commits flow)</td>
    </tr>
    <tr>
      <td>Authors</td>
      <td>Oleg Chirukhin</td>
    </tr>
    <tr>
      <td>Keywords</td>
      <td>git, commits, atomicity, discipline, splitting</td>
    </tr>
  </table>
  <section id="dependants" title="Depended on by">
    <p p="3">Packages that require this one, as the catalog holds them now.</p>
    <table p="4">
      <tr>
        <td>Standing</td>
        <td>Title</td>
        <td>Coordinate</td>
        <td>Publisher and language</td>
      </tr>
      <tr>
        <td>community</td>
        <td>git-practices</td>
        <td>`org.vibevm.world/git-practices@1.0.0`</td>
        <td>org.vibevm.world · en</td>
      </tr>
    </table>
  </section>
  <section id="the-manifest" title="The manifest">
    <fence lang="toml" p="5">[package]
name = "git-atomic-commits"
group = "org.vibevm.world"
kind = "flow"
version = "1.0.0"
epoch = 1
format = "normal"
authors = ["Oleg Chirukhin"]
license = "UPL-1.0"
description = "Atomic commits discipline: one commit = one logical idea — how to split a mixed working tree, when to batch, and why atomicity matters more in a human-AI team (the message FORMAT is the separate conventional-commits flow)"
keywords = ["git", "commits", "atomicity", "discipline", "splitting"]

[compatibility]
min_vibe_version = "0.1.0"
requires_kinds = []

[boot_snippet]
source = "vibevm/vibespecs/boot/30-flow-atomic-commits.xml"
category = "flow"
# A non-negotiable commit rule — suggest the inline priority lane (PROP-009 §2.4).
link = "static"
</fence>
  </section>
</spec>
