The Groundhog Autonomous Zone (“GAZ”) is an unincorporated association operating under these directives (“GAZ Directives”).

The GAZ centers Black liberation and Indigenous sovereignty (“purpose of the GAZ”, “GAZ’s purpose”).

The GAZ does [de|anti]colonial land stewardship.

The GAZ educates about colonialsm and how to act against it.

The GAZ provides ways of living that are not supportive of colonialism.

The GAZ holds these things and the acts and artifacts they cause and create as having value (“GAZ Values”). {#gaz-values}

People are identified with one or more labels based on their relationship with the GAZ and/or colonialism

Members of the GAZ are called Groundhogs.

  1. The Documentation Department maintains a list of members (“GAZ Membership List”)

    1. The GAZ Membership List is maintained as an Org-mode file (“GAZ Membership List file,” gaz-members.org{.verbatim}) controlled by a Git repository (“GAZ Membership List repository”, members.git{.verbatim}), and hosted on a Git forge (“GAZ Membership List forge”, https://source.gaz.community/gaz/members).

    2. The GAZ Membership List contains each members’:

      1. Name

      2. Discord username

      3. xDai address

      4. Email

      5. Hive username

  2. The Accounting Department maintains accounts in the GAZ ledger corresponding to the GAZ Membership List

    1. Members are recorded under the Assets:Governance:Members{.verbatim} account, under the Active{.verbatim} and Inactive{.verbatim} subaccounts.

      1. Each member is recorded as a new commodity type.
  3. The Warp Department maintains the Burrow{.verbatim} channel category on the GAZ Discord.

    1. Only Groundhogs are allowed to join channels in the Burrow.

    2. The Warp Department maintains the #den{.verbatim} channel in the Burrow{.verbatim}.

      1. The #den{.verbatim} is for general congregation of Groundhogs.

      2. Everything said in the #den{.verbatim} is private to that space.

    3. The Warp Department maintains the #announcements{.verbatim} channel in the Burrow{.verbatim}.

    4. Any Groundhog may privately message emsenn to resolve an immediate conduct problem in the Burrow{.verbatim}.

Groundhogs may nominate a Duckling as a Gopher.

  1. A nominated Gopher must receive no objection from all Groundhogs before being approved.

  2. An approved Gopher may be nominated to work in a specific capacity.

  3. Groundhogs may be paid in GAZ by groundhogs for their work.

  4. Groundhogs will not be paid directly from the GAZ Colony or any GAZ Colony Team.

Groundhogs recognize the “Black, Indigenous, Person of Color” (“BIPOC”) label.

Groundhogs maintain the GAZ Directives.

The GAZ Directives are maintained as an Org-mode file (“GAZ Directives file”, gaz-directives.org{.verbatim}) controlled by a Git repository (“GAZ Directives repository”, directives.git{.verbatim}), and hosted on a Git forge (“GAZ Directives forge”, https://source.gaz.community/gaz/directives).

The GAZ Directives support the GAZ’s purpose

The GAZ Directives are versioned (“GAZ Directive versioning”):

  1. Given a version number MAJOR.MINOR.PATCH

    1. Increment the MAJOR version when the decision-making model is changed.

    2. Increment the MINOR version when a decision is made.

    3. Increment the PATCH version when a typographical error is fixed.

  2. The GAZ Directive versioning is recorded as annotations on the GAZ Directives repository.

    1. [TODO]{.todo .TODO} Step-by-step??
  3. The GAZ Directives use some specific vocabulary and grammar.

    1. Present-tense for things that have operations in-place, future/passive for things that don’t or are on-going obligations to revisit?
  4. GAZ Directives are changed through a consent-based decision-making model.

The GAZ Directives are private to Groundhogs.

  1. Groundhogs may share GAZ Directives with Gophers if it is deemed necessary.

    1. [TODO]{.todo .TODO} Any share of the Directives must be recorded. Where, how?

The GAZ Directives can be changed.

  1. Any Groundhog can propose new directives, changes to existing directives, or to remove existing directives.

  2. A change to the GAZ directives require consent of all Groundhogs.

    Changing the GAZ Directives requires the consent of all Groundhogs.

    1. Consent here means that no Groundhog objects to the change.
  3. Changes to the GAZ Directives m

Groundhogs maintain tools that enable the fulfillment of the GAZ Directives. (“GAZ Tools”)

Groundhogs divide the decisions and acts of the GAZ into different GAZ Workgroups (GAZWGs).

GAZ Workgroups may request access to certain GAZ assets by default:

  1. GAZ Workgroups may request a Team in the GAZ Colony.

  2. GAZ Workgroups may request channels and channel categories in the GAZ Discord.

GAZ Workgroups may propose a transition to alternative terms, language, decision-making, etc.

  1. GAZ Workgroups operations must continue to produce compatible records.

  2. GAZ Workgroups must continue to follow the GAZ Directives.

  3. GAZ Workgroups can decide to separate from the GAZ, but will lose access to GAZ Tools.

GAZ Workgroups are organized through Directives

  1. Each GAZ Workgroup must have Directives specifying the following:

    1. Decision-making model

    2. Membership

    3. Purpose

    4. Assets

    5. Obligations?

  2. GAZ Workgroups can organize as multiple Workgroups.

Groundhogs maintain the following Workgroups

Groundhogs organize a Bookkeeping Workgroup

  1. The Bookkeeping Workgroup handles the contemporary record-keeping of the GAZ.

    1. The Bookkeeping Workgroup keeps records that recognize the GAZ Values.

      1. The Bookkeeping Workgroup organizes the Groundhog Emacs Workgroup.

        1. The Groundhog Emacs workgroup is responsible for creating and maintianing an Emacs configuration which is capable of creating, modifying, and processing the records required by the Bookkeeping Workgroup. (“Groundhog Emacs”)

        2. The Warp Department maintains a #gemacs{.verbatim} channel in the Prairie category of the GAZ Discord.

          1. emsenn moderates the #gemacs{.verbatim} channel.
        3. The following people are members of the Groundhog Emacs Workgroup:

          1. emsenn

          2. KemoNine

        4. Decisions in the Groundhog Emacs Workgroup are made by emsenn.

  2. The Bookkeeping Workgroup organizes the Accounting Department

    1. The Accounting Department maintains a record of the transactions that affect the GAZ’s value (“GAZ Ledger”).

      1. The GAZ ledger is maintained as an Org-mode/Beancount file (“GAZ Ledger file”, gaz-ledger.org{.verbatim}) controlled by a Git repository (“GAZ Ledger repository”, members.git{.verbatim}), and hosted on a Git forge (“GAZ Ledger forge”, https://source.gaz.community/gaz/ledger)

      2. The Accounting Department uses Beancount and Fava for recording the GAZ ledger.

    2. The GAZ Ledger is divided into five basic accounts:

      1. Assets{.verbatim}

      2. Expenses{.verbatim}

      3. Equity{.verbatim}

      4. Liabilities{.verbatim}

      5. Revenue{.verbatim}

    3. The following people coordinate the Accounting Department

      1. emsenn
  3. The Bookkeeping Workgroup organizes the Documentation Department

Groundhogs organize a Web Workgroup

  1. The Web Workgroup organizes a Warp Department

    1. The Warp Department maintains the computer services which allow for non-local communication, decision-making, and action.

      1. The Warp Department maintains a Discord server (“GAZ Discord”).

      2. The Warp Department maintains a Wiki (“GAZ Wiki”).

      3. The Warp Department maintains a credentials management service (“GAZ Bitwarden”).

  2. The Web Workgroup organizes a Weft Department

    1. The Weft Department stewards the GAZ Wiki.

      1. The GAZ Wiki is an encyclopedia of information about colonialism.

      2. The GAZ Wiki is publicly accessible.

Groundhogs organize teaching people living inside colonialism about it and how they can act against it (“Duckpond”).

  1. The Duckpond teaches people living inside colonialism about colonialism and how they can act against it.

  2. The Warp Department maintains the Duckpond{.verbatim} channel category on the GAZ Discord=

    1. Any person may join the Duckpond{.verbatim}.

    2. Any person who joins the Duckpond{.verbatim} may ask a Groundhog to become a Duckling.

      1. A Duckling is a person who has chosen to learn about colonialism from the Duckpond.

      2. The Documentation Department maintains a list of Ducklings (“Duckling List”)

        1. The Duckling list is maintained as an Org-mode file (“Duckling List file”, ducklings.org{.verbatim}), controlled by a Git repository (“Duckling List repository”, ducklings.git{.verbatim}), and hosted on a Git forge (“Duckling list forge”, https://source.gaz.community/duckpond/ducklings).

        2. The Duckling List contains each ducklings:

          1. Discord name

          2. Email

          3. xDai address

    3. The Warp Department maintains the #wading-pool{.verbatim} channel in the Duckpond{.verbatim}.

      1. The #wading-pool{.verbatim} is the general purpose chat channel for Ducklings.
    4. The Warp Department maintains the #learn{.verbatim} channel in the Duckpond{.verbatim}.

    5. The Warp Department maintains the #act{.verbatim} channel in the Duckpond{.verbatim}.

    6. The Warp Department maintains the #question{.verbatim} channel in the Duckpond{.verbatim}.

  3. The Warp department maintains the Fens{.verbatim} channel category on the GAZ Discord

    1. The Fens{.verbatim} channels are for any Duckling who holds more than 100 GAZ Tokens.
  4. The following people coordinate the Duckpond

    1. emsenn

Groundhogs organize a blockchain-based fund & governance protocol (“GAZ Colony”).

  1. The GAZ Colony is on the Web at https://xdai.colony.io/colony/gaz

  2. The GAZ Colony is managed by emsenn

  3. The GAZ Colony is at 0xA235373212d843A98B05e883C4ce43504692A0C1{.verbatim} on the xDai mainnet (“GAZ Colony Wallet”).

    1. The GAZ Colony Wallet is tracked by account Assets:Colony:Root{.verbatim}.
  4. The Accounting Department tracks the GAZ Colony in the GAZ Ledger.

Groundhogs organize a blockchain currency (“GAZ token”)

  1. The GAZ token is at 0x0B9F6889B01BC8Ea674E6f9a0a53b07Cd0EE4867{.verbatim} on the xDai mainnet.

  2. The Accounting Department maintains the GAZ Token Mint through the GAZ Colony.

  3. The GAZ token was created on March 24th, 2021

    2021-03-24 commodity GAZ
       name: "Groundhog Autonomous Zone Token"
       asset-class: "xDai token"
  4. The Accounting Department tracks the GAZ Token Mint in the GAZ Ledger.

    1. Minting GAZ Tokens is balanced against Equity:Mint:GAZ{.verbatim}.

    2. Minted GAZ Tokens go into the GAZ Colony Wallet.

      This is automatically determined by how Colony works.

  5. GAZ Tokens may only be minted with affirmative consent from all Groundhogs.

Groundhogs organize a Bootstrapping Workgroup for creating the GAZ

  1. The Bootstrapping Workgroup may make decisions for the GAZ until it is closed.

    1. This overrides all other decision-making processes specified in the GAZ Directives.

    2. Only emsenn may make decisions.

  2. The Bootstrapping Workgroup is operated by emsenn

  3. The Bootstrapping Workgroup maintains relationships with Gophers:

    1. KemoNine is helping draft the directives, and is also operating much of the Warp Department so has a hand in lots of things through this Bootstrapping period.

Groundhogs organize Makha Sa Garden.

  1. Makha Sa Garden is located at the corner of N. Merritt Mill Rd. and Rosemary St., in the colonial settlement of Chapel Hill in state of North Carolina.

  2. Makha Sa Garden exists on the unceded traditional territory of the Shakori-Eno peoples, and in relationship to the Indigenous people who live here today, as well as people brought to this place through diaspora, displacement, and settler-colonization.

  3. Any Duckling, Gopher, or Groundhog may work with Makha Sa Garden (“Stewards of Makha Sa Garden”).

  4. Stewards of Makha Sa Garden center [de|anti]colonial land stewardshp.

    1. Stewards of Makha Sa Garden work to improve the local soil.

    2. Stewards of Makha Sa Garden cultivate native plants.

    3. Stewards of Makha Sa Garden cultivate xeric plants.

    4. Stewards of Makha Sa Garden cultivate medicine plants.

    5. Stewards of Makha Sa Garden propagate plants.

    6. Stewards of Makha Sa Garden save seed.

    7. Stewards of Makha Sa Garden give away propagated plants to BIPOC.

  5. Stewards of Makha Sa Garden steward plants and animals at Makha Sa Garden

    1. Stewards of Makha Sa Garden steward the rosemary bush under the lamppost by the western stairs of Brick Box Apartments (“Hoey’s Rosemary”).

      1. Stewards of Makha Sa Garden will prune Hoey’s Rosemary after it blooms, every spring.

        1. Stewards of Makha Sa Garden will attempt to propagate cuttings from pruning Hoey’s Rosemary.
    2. Stewards of Makha Sa Garden steward the red sorrel by the rock dam behind Meineke (“Makha Sa Sorrel”).

      1. Stewards of Makha Sa Garden will prune the Makha Sa Catchment Trees to let the Makha Sa Sorrel get sunlight.

      2. Stewards of Makha Sa Garden will try and save the seed from the Makha Sa Sorrel after it blooms.

        Late May?

    3. Stewards of Makha Sa Garden steward the decorative trees in the water catchment (“Makha Sa Catchment Trees”).

Groundhogs organize the Ferguson garden.

The GAZ operates the Beadworking Group (GAZ-BED)

GAZ-BED produces beadwork for GAZ members.

Musings?

On Roles

A person’s role is determined by the involved Workgroups and people, not an abstract label within the GAZ. For example, that someone is an officer in the Records workgroup does not matter should they show up to crew a Fibercraft operation, but whether or not they are a Groundhog or a Gopher might matter.

On Workgroups

Each workgroup is meant to be really automonous, to the point where if they say no one affiliated with a specific other workgroup is allowed to crew any of their operations. That sort of autonomy is seen by emsenn as a mechanism against bureaucratic power accruing in the GAZ itself, which should only exist enough to allow “TELNET-style negotiations” between Workgroups.

”…[I]ts not explicit anywhere but workgroups can create sub-workgroups as many layers deep as wanted.) I guess that idea is important: its like russian nesting dolls, where the main group can create a smaller group that is, at start, indistinguishable from the big group except that it has no purpose and no members, but then through having a purpose and members, and acting out over time, it distinguishes itself.” - emsenn

On TCUTT

When discussing how to do something, it’s easy to get bogged down in theory. Therefore, it’s encouraged to, in response to a question, ask back: “TCUTT?”

The Colonial Urge To Theorize

“Is this quesiton related to making us capable of taking the action-at-hand, or is it just asking questions out of colonial habit?”

For example, if the action-at-hand is “write up some documentation about workgroups,” asking a question about workgroup theory is good. But if the action is “copy notes from the #praxis{.verbatim} chat channel into the records, and asking about workgroup theory is just to imagine some possible innovation that makes the work more efficient, well, that’s not the action-at-hand. (But, it might be good to make a note to explore that as an action to take, at another time!)

Responses to “TCUTT?” might be:

  • You’re right; let’s ignore the question and move on.
  • I think the question relates to the action-at-hand [because …]. (You don’t have to express your reasoning for beleiving there’s a relationship, but it might help folk answer the question.)
  • The question is related to <another action>, but I see that action as related to this one [because…].
  • I think knowing the answer will help motivate me to do the action-at-hand [because…].
  • I think knowing the answer will help orient me properly around the action-at-hand [because…].

Workgroups

[Domestic]{.spurious-link target=“dom.org”} [DOM] : Handles keeping the Burrow nice.

[Sourcing]{.spurious-link target=“sor.org”} [SOR] : Handles bringing materials into the GAZ.

[Diplomacy]{.spurious-link target=“dip.org”} [DIP] : Forms relationships with other communities and societies.

[Records]{.spurious-link target=“rec.org”} [REC] : Makes records (ledgers, documents, etc.) as needed, for other Workgroups.

[Library]{.spurious-link target=“lib.org”} [LIB] : Handles the material cultural artifacts the GAZ holds.

[Landwork]{.spurious-link target=“lan.org”} [LAN] : Forms relationships with Land near the Burrow.

[Medicine]{.spurious-link target=“med.org”} [MED] : Makes medicine (including food).

[Fibercrafts]{.spurious-link target=“fib.org”} [FIB] : Makes fabric, textiles, blankets, clothing, etc.

Proposals

Soon

Solar water-heater.

What’s the best - in terms of energy - way to heat up some water for washing dishes, laundry, our selves?

Later

Someday

Tree-weight batteries?

Soil-batteries