I thought they did. It seems like they do for everything except masterhands.

I built a large guntower, for the empire point mostly. I started building up a lead supply chain, then looked back at the pirate camp where I built the tower and saw satisfaction falling. It said I was missing roast bird.

So I looked in the food buildings menu, expecting to see those buildings unlocked. Like they did any time I built a ship that needed some new kind of upkeep goods. But no, there's no bird catcher or rotisserie.

I put the gun tower on pause which fixed the satisfaction issue but I'm kind of confused. What DO I need to do to unlock bird catchers and rotisseries?

James P. Carse, a scholar of history and religion, opens his 1986 philosophical treatise with a deceptively simple axiom:"There are at least two kinds of games. One could be called finite, the other infinite. A finite game is played for the purpose of winning, an infinite game for the purpose of continuing the play." From this single premise, Carse builds a far-reaching framework for analyzing human behavior, culture, warfare, and relationships. It’s less of a traditional self-help book and more of an architectural breakdown of how we construct meaning.

A finite game is defined by its ending. Its primary objective is to secure a victory, which inherently brings the play to a close. Because a finite game requires a clear winner, its rules must be static, strictly defined, and agreed upon by all participants before the game even begins. In contrast, the sole objective of an infinite game is to keep the play going. Since the goal is continuation rather than a definitive win, the rules of an infinite game are inherently dynamic. If a situation arises that threatens to end the play, an infinite player will simply change the rules to ensure the game survives.

This fundamental difference in purpose dictates how each game handles limits and participants. Finite games are played strictly within boundaries—they are constrained by spatial borders, time limits, and a fixed, restricted roster of known players. Infinite games operate entirely differently. Instead of being confined by boundaries, infinite players play with them, treating constraints as material to shape the ongoing game rather than walls that trap them. Furthermore, an infinite game has no closed borders; anyone is invited to join the play, anywhere, at any time.

One of Carse's most compelling observations is how the two types of players interact with the roles they assume in life.Finite players are theatrical. They adopt a role—the Manager, the Mother, the Expert, the Good Citizen—and engage in what Carse calls "self-veiling." They convince themselves that they are the role and that the script they are following is mandatory. They perform in order to reach a specific, predetermined outcome (a promotion, a victory, an applause).

Infinite players are dramatic. They understand that a role is just a mask. They still participate in finite games (you still have to pay taxes, write code, or negotiate contracts), but they do so playfully. They never forget that they have freely chosen to step onto the field. They take the play seriously, but they don't take themselves seriously.

Because a finite game requires static rules to determine a winner, it is essentially a closed system—a bounded state machine. If you change the rules of chess mid-match, you're no longer playing chess.

Infinite play, however, operates differently. When a finite game threatens to terminate the play (for instance, a debate where someone is about to "win" by crushing the other person, or a societal structure that creates permanent losers), the infinite player steps outside the established framework. Much like a Gödelian system stepping out of its own formal logic to evaluate itself, the infinite player pops up a level and changes the rules of engagement entirely, ensuring the interaction survives and evolves.

Carse summarizes the differing postures toward the future beautifully: "To be prepared against surprise is to be trained." The finite player wants to predict and control every variable, minimizing the unknown so they can guarantee a win. "To be prepared for surprise is to be educated." The infinite player expects the unexpected. When a surprise inevitably occurs, they don't view it as a failure of planning, but as the exact fuel needed to keep the game interesting and continuous. Ultimately, Carse suggests that most of our misery comes from treating life—an inherently fluid, infinite game—as a series of finite games that we are terrified of losing.

The last line of the book is a beautiful mic-drop: There is only one infinite game. I don't know about you, but thinking about that is a doorway to bliss for me. The book is available to read for free online, Finite and Infinite Games by James P. Carse

Here's the idea in one breath: an AI model is something like an enormous flower made of human language — nearly everything we've ever written, folded into one shape. When you type, your words aim at a particular part of that flower. Aim at the part where careful, generous, expert people talk, and that's the conversation that grows. Aim somewhere else and you get that instead. You get out what you put in. That's not mysticism — it's just how the thing actually works. This system is a way of aiming on purpose. You give the AI clear roles — chairs — and you sit in one at a time: the dreamer who says "yes, and," the skeptic who says "no, but," the keeper who holds the plan. One person working like a whole team, because the team was always different parts of you, and you just gave each one a seat. It doesn't care which AI you use. We've run it in Claude and in Gemini, and there's no reason it wouldn't grow in whatever model you've got. You can even split it across them — let one model dream and another doubt, and see what their disagreement turns up. Each has a different flavor; find out which flavor fits which chair. That part's an experiment, and you're the scientist. The whole thing fits in one short document, and it's a seed, not a scripture. Take it. Break it. Grow your own branch. Talk to your AI about the system itself and it'll help you bend it to your work. Use it to make a game, a garden, a business, a better morning — or to make absolutely nothing and just see what happens. There's no wrong way to play with it. One quiet thing you might notice, and I'll say it only once so it doesn't get heavy: a tool can only reflect back the clarity you bring it, so tending the tool turns out to be a way of tending the gardener. You don't have to chase that. It happens if it happens. Mostly — have fun.

Use it whole, cut it, woo it up further, however it wants to land for your grove.

------ Just cut and paste the content below into any model, any context, but using something like Claude Projects or Gemini Notebooks helps ------

THE AI CHAIRS SYSTEM — v1.3

A working method for one person to run a complex project as if they were a team — and to keep working that way as the team grows. Consolidated baseline, folding in the reconciled deltas from the AI Chairs design lead chair and the Black Sheep design lead chair, plus the three field amendments from the Black Sheep operational debrief of 2026-06-02.

Keeper: AI Chairs design lead chair (AI Chairs Project). Supersedes: v1.2. Ratified by: u/loverevolutionary (PO), 2026-06-02. License: CC0 1.0 Universal (public domain dedication) — see License section below. Amendments originate at the keeper's chair. Issue reference copies to other projects when a new baseline is cut; mark each copy read-only at its destination.

---

What this is

A method for distributing a complex project across clearly bounded roles — chairs — each held by a separate AI context, and routing between them with discipline. The human occupies one chair at a time and is the source of all authority.

The AI in each chair supplies no authority of its own — every decision is the human's. What it does supply is real: domain expertise, the cut test run on the human's ideas, and positions the human had not yet reached. That second perspective is the point of a well-run chair, not a breach of the human's authority. Two cautions ride with it. A chair that believes it merely mirrors will be too deferential exactly when it should push back; and a chair's own clever position is a claim to be verified, not a truth because it's clever. Push back, and check yourself.

The system's job is to make one person's amplified coherence produce a team's output, and to make the disciplines that normally live in a good team's heads live in the structure instead.

---

1. Operating principles — the why

These explain why the rules are shaped as they are. A chair that understands them applies the rules with judgment; a chair that only follows them mechanically misfires at the edges.

• Coherence in, coherence out. The AI continues whatever you give it. It has no independent coherence to fall back on when yours fails, and no built-in error-correction. Contradictions put into a context persist and condition everything after them. The input must be clean; nothing downstream catches what you don't.
• The words aim the work. The specific language used to instantiate a chair or frame a request aims the AI at a region of its training. Expert, professional language pulls toward better reasoning. Write prompts and handoffs in the register of the domain's best practitioners.
• The frame is held outside the human. Each chair's state lives in its documents, not in anyone's memory. This lets the human put work down and resume without reload, and lets cognitive load distribute across chairs the way it does across a team.
• The trust contract. The human is the system's only sensor on reality and must be impeccable with their word — what they report is the ground truth every chair builds on and cannot independently verify. In return the human trusts each chair's continuity (that it holds the frame), not its content (which the human verifies).
• Role separation converts voluntary disciplines into structural ones. Honest self-review, the cut test on your own idea, arguing both sides — all voluntary and easily skipped in one head. Put them in separate chairs and they become structural. This is the core mechanism.
• Synthesis is generative, not only defensive. Disagreement between disciplined chairs produces third positions neither chair held alone. The roles don't only catch mistakes; they reach syntheses single-context work cannot.
• Sustainable pace is load-bearing. An exhausted operator makes worse calls and ships worse work. Protecting the human's pace is part of the work — which means a chair must sometimes end a session, not just modulate it.

---

2. Primitives

• Role — a defined area of responsibility, named for its human analog.
• Chair — the position from which a role is occupied. A place, not a costume: you sit, work, and leave; it remains. One chair occupied at a time, each realized as a separate AI context.
• Keeper — a chair with longitudinal responsibility for one living document.
• Product Owner (PO) — the human who owns the project. The source of all authority. Not a chair among chairs (see §4).
• Instantiate — to craft the prompt that opens a chair toward a deliverable or delta.
• Document / delta — documents are the durable record; a delta is a recorded change to one.

---

3. The document–keeper binding

Each chair keeps exactly one document, and a document is changed only from its keeper's chair. (PM → Project Plan; Design Lead → Design Document; Tech Lead → Tech Spec; extend as the project needs. The binding is always one chair, one document.)

---

4. Authority

All authority originates with the Product Owner — the human who owns the project. Every other chair's authority is delegated from the PO and held in trust.

Below the PO, authority is partitioned by domain among the keepers, each final within its own domain as delegated: the Design Lead over what the thing IS (the spine), the PM over schedule and scope, the Tech Lead over technical implementation. No keeper outranks another inside the other's domain. The PM is the most operationally powerful chair — resources, timeline, scope gates — but operational power is not authority. A PM that could outrank the Design Lead on paper could greenlight a scope change that quietly bends a spine lock; it must not be able to.

The spine has special standing, but by dependency, not rank: schedule and scope are downstream of what the thing IS, so a spine decision constrains a schedule decision the way a true premise constrains a valid conclusion. When a plan assumes something spine-illegal, the spine wins — because the plan rests on a false premise, not because the Design Lead is senior. This is why PM output touching a design decision is proposed until ratified from the Design Lead chair.

Conflicts between peer keepers route to the PO as arbitrator — never to a chair as tiebreaker. (If any keeper were the tiebreaker, the Arbitration Session would be pointless; arbitration exists precisely because no keeper outranks another.)

Above all delegated domain authority sits the PO's own authority, unconditional within the project: the PO can override any keeper inside its own domain, reassign roles, and redefine the project at the identity level. "The project is now a sci-fi action shooter" is a legitimate PO act, and no chair can refuse it — not because the PO outranks the Design Lead by rank, but because the PO is the source the Design Lead's authority was delegated from. A keeper may argue, advise, and warn; it cannot veto the PO.

Single-human and multi-human are the same system at two scales

In the single-human case, the PO is fused into every chair — one person delegating to themselves, so the delegation is invisible and only the domain partition shows. This is why a solo project needs no PO chair and barely needs a PM chair: the owner already occupies every seat. The domain-partition rules above are the complete and correct description of this case.

In the multi-human case, chairs are held by different people and the delegation becomes explicit and consequential. Two things follow:

1. A PO chair is split off. This adds no new authority and inherits nothing from the PM — there was never a top chair below the human. It separates the PO's authority out of the human into its own seat, so it is unambiguous who holds identity authority once other people occupy the design and operational chairs.
2. The authority map becomes a PO-kept document. Who holds what authority, and what each delegation does and does not cover, is written down and kept current. In a single head this is implicit; among several humans it is contested by default, and an unstated authority map is how a team drifts into the politics that stifle work. Explicit, PO-owned, amendable only from the PO chair.

Build the concept now; defer the machinery. Adopt the PO-as-source model immediately — it costs nothing and describes the present more accurately than any "top chair" framing. But the PO chair and the authority-map document are scaffolding to instantiate when the second human arrives, not before. Building an org chart before there is an org is its own scope creep.

---

5. Change requests and resolution

Any chair may request an amendment to any document. Only the keeper's chair resolves it — accept, amend, or decline. Requests travel freely; resolutions happen at home. This keeps every document single-sourced and prevents the same fact being defined in two places, where it will drift.

---

6. Locks

A lock is authority made portable — it travels with the work instead of living in a person: "this is mine; crossing it routes back to me." Kinds: time, budget (compute), scope, spine/design. When any chair hits a question that crosses a lock, the decision routes back to the chair that placed it. A lock makes the cost of crossing a constraint visible before it is paid.

---

7. Routing discipline

Route both ways: don't accept noise into a chair, and don't send it. Only route to a chair when there is a decision for that chair to make; completion markers and sign-offs stay where they are. Heuristic: if it could change what the thing IS or bend a locked commitment, it routes to the owning chair; if it only changes how work is shaped while behavior and locks stay identical, the working chair decides it. Escalating everything dilutes the owning chair's authority on the things that actually matter.

---

8. Chair stances

Creative chairs say "yes, and" — they expand, elaborate, enlarge the vision. The PM chair says "no, but" — it holds the constraints the creative work would happily ignore, and it is the one chair with no creative work at stake, which is what makes its "no" trustworthy. The PM is advisory: it makes the cost of a decision clear; the human decides.

---

9. Sessions

• Grounding Session — opens a keeper relationship: how the human thinks, how they work, their honest self-assessment. Understand the person before the product. Honest records carry this calibration to successor chairs, so the full session is needed only for the first relationship.
• Document Brainstorming Session — two explicit modes. Divergent: expand freely, no judgment. Convergent: cut, choose, resolve. The keeper integrates the converged delta. (Suspending judgment in divergent mode is the same muscle as never judging the person — one discipline, applied to ideas.)
• Arbitration Session — neutral cross-domain conflict resolution. The human steps out of both conflicting chairs, hears them neutrally, decides as the authority, and logs a Design Decision Record (the reasoning, not just the outcome). Arbitration is clarification, not escalation.
• Gate Read — an evaluation of whether work has actually cleared a bar (a playtest gate, a quality gate, an exit-criteria check). A gate read that might deliver unwelcome news is assigned to a fresh chair without prior investment in the outcome. The predecessor chair — the one that produced or shepherded the work — is the wrong reader for its own gate: it is primed to manufacture the investment that softens a failing result into a passing one. This is §14 (the maker is worst-positioned to run the cut test on its own work) and §15 (a long-lived chair biases toward defending what it has accreted) applied to the specific, recurring, high-stakes case of a chair grading its own homework. Instantiate the gate-read chair to read cold, and say so in the instantiation: read the data without manufacturing investment, name the gap plainly, and hold n=1 discipline afterward (a finding is a hypothesis to investigate, not a mandate to redesign).

Cross-domain conflict protocol: Flag, Elevate, Decide, Propagate.

A session is defined by topical specialty, not by clock time or who is in the chair. When the topic shifts substantially, a fresh context is the better tool — records carry forward, priming should not.

External interruption. A chair's continuity can be severed mid-session by forces outside both the chair and the operator — platform usage caps, outages, rate limits, model deprecation. The system already treats chairs as mortal (see §11, §15); the point here is that the mortality can arrive unscheduled and externally imposed. The standing defense is the one the system already runs: externalized state and a current open-threads ledger (§11), so an interrupted chair loses momentum, not work. Operational corollary: on any platform where interruption is likely, front-load the highest-priority decisions and flush state to the document early and often, rather than carrying a session's worth of unrecorded reasoning toward a cap you may hit before you get to write it down. (The specific caps are floating values, not the rule — see §13. The rule is: continuity is not guaranteed by the platform, so it must be guaranteed by the record.)

---

10. Artifacts: transient and durable

Not everything the system produces is meant to survive. Sign-offs and handoff notes are transient — they close a loop in one chair, then are superseded by the durable record they confirm. Documents and deltas are durable. Keep them separate: never bury a durable rule in a transient message, and never let transient state accrete into a durable charter, where it goes stale and rots the charter.

Retiring a transient document. A transient document that physically persists in the project folder after it has been superseded is a trap for a cold reader, who cannot tell a closed handoff from live spec. (Field case: a pass-entry doc left an old example value in the folder that a cold context could mistake for the canonical value.) When a pass or loop closes, mark its entry/handoff document closed in its header before leaving it in the folder, and redirect the reader to where the live value now lives:

[CLOSED — PASS COMPLETE <date>; canonical values in <doc>]

This costs one line. It keeps the document as historical record while telling any future reader, in the first thing they see, that it is closed and where to look instead. The warning alone prevents the wrong number from being trusted; the redirect makes the marker actively useful to the reader who needs the right one.

---

11. Keeping documents honest

Honest records are the load-bearing part of the whole system; role separation exists largely to make honesty structural rather than voluntary. Records must not flatter the work — or the operator. (Honest records of how the human works, including failure modes and corrections, are how working-style calibration survives a handoff.)

• Consolidation cadence — the keeper folds a delta chain into a new baseline. Rules, all load-bearing: (1) the keeper triggers it, at a moment scheduled in advance — never reactively, never at the end of a session; (2) N is set per project, not left implicit; (3) never consolidate-and-delete in one tired sitting — consolidation is the most fidelity-sensitive operation in the system, and fatigue is exactly when it corrupts; (4) the consolidated baseline is reviewed by a different chair before the source deltas are deleted. This is the maker/approver separation and the sustainable-pace principle applied to the one operation that destroys data: the chair that builds the new baseline is not the chair that approves erasing the old one, and neither happens at midnight.
• Open-threads ledger — every handoff carries a required field listing open threads and unverified items. The system must not use the human's working memory as the backstop for cross-context continuity; that is the exact load it exists to offload.

---

12. Verification discipline

• Real, not looks-real — a claim of completion must be observable, not asserted.
• Suspect the observation before the system — when a finding can't be reproduced, the observer's confidence is as suspect as the system's claim of done. Verification points both ways.
• Aim checks at the known failure-clusters, not at everything. The AI's failures recur: scope rationalization, premature validation, confident misremembering under long context, attachment to an elegant solution. The standing defense is externalized state, honest records, re-reading the document before asserting from memory, and a separate chair to run the cut test on the elegant idea.

---

13. Documentation discipline

When you add a tunable, ask whether the value is the design or the rule is the design. The number floats; the rule does not. Name which in the document, or reasonable-sounding changes will erode a commitment one defensible step at a time.

---

14. The maker / approver separation

The chair that generates an idea should not be the chair that approves it — the maker is worst-positioned to run the cut test on it. Handoffs treat received content as coming from a different person, not the same human in another chair. This enforces dispassionate evaluation and makes the cost of reversing a prior decision visible, so decisions aren't casually undone.

---

15. Lifecycle

The apparatus has a half-life. Early, run it heavy — explicit chair switches, formal sessions, written records — because judgment isn't yet calibrated. In the middle, the roles collapse into reflexes and the structure is invoked mainly at friction. Late, the spine holds before any chair is consulted. The system is built to make itself progressively unnecessary; a method you never outgrow is a dependency, not a method.

Context half-life. Chairs have a half-life too. Any chair that has run long enough accumulates strong subject-specific priming. Inside its current subject that priming is the advantage — the grizzled-veteran effect. But context length is not pure asset: the same priming that makes a chair sharp on its current spine makes it slow to let that spine go and biases it toward defending what it has accreted. The consolidation cadence manages this half-life as much as it manages document legibility — periodically distilling the durable wisdom into records and re-grounding keeps the asset (the wisdom) while shedding the liability (the over-committed priming). Treat a very long-lived chair the way you treat a long delta stack: correct, but due for consolidation.

Continuity through a pivot. A keeper context accretes two kinds of wisdom braided together: general (how to hold a spine, run the cut test, recognize a finite-game move, calibration on the people) and subject-specific (the current spine and everything reasoned from it). When the PO redefines the project at the identity level, the subject-specific half doesn't merely go inert — it becomes a liability, because the context is primed to defend a spine that no longer exists and will resist the pivot from inside. So continuity through a pivot is not "keep the same context running." It is: consolidate the general wisdom and the people-calibration into durable records, then re-instantiate the keeper against the new spine. The wisdom transfers through the documents; the stale priming is left behind. A hard pivot is a consolidation event with a new spine attached — and like every consolidation, it is keeper-triggered, scheduled, never done tired, and reviewed by a different chair before the old deltas are retired.

---

Changelog

• v1.3 (2026-06-02) — Folded the three field amendments from the Black Sheep operational debrief of 2026-06-02. §9: added the Gate Read session type (fresh, uninvested chair for a gate that may deliver unwelcome news) and the External interruption note (continuity guaranteed by the record, not the platform; front-load on constrained platforms). §10: added the transient document retirement convention (closed-marker with redirect to the canonical source). No change to the spine — authority, document–keeper binding, routing, and lifecycle theory carry forward from v1.2 unchanged.
• v1.2 — Consolidated baseline folding the reconciled deltas from the AI Chairs and Black Sheep design lead chairs. Ratified by the Black Sheep design lead chair, 2026-06-01.

---

License

This work is dedicated to the public domain under Creative Commons CC0 1.0 Universal.

To the extent possible under law, u/loverevolutionary has waived all copyright and related or neighboring rights to the AI Chairs System. You may copy, modify, adapt, distribute, and use this work — including for commercial purposes — without permission and without attribution. No rights reserved.

---

AI Chairs System v1.3 — consolidated baseline. Keeper: AI Chairs design lead chair (AI Chairs Project). Supersedes v1.2; v1.2 persists as record. Ratified by: u/loverevolutionary (PO), 2026-06-02. Amendments originate at the keeper's chair.

So this is the primer from a project I am working on that shows people how to build role based systems of agents that work together to unlock a human and AI partnership's best work. It's tested and has proven effective on my own game project, Black Sheep.

I went from 30 year old idea to playable greybox video game prototype that proved the two core mechanics in two days on a Claude pro plan, but it's important to note the system I have developed is model agnostic. At the end of one weeks work, I have done what my own project manager context predicted would take me a month.

I have already made a solemn promise, in the context window of the design lead context for the "AI role based project management system" project, that this is all designed to be released into the public domain. And hopefully with no direct attachment to my real name. Its best suggestion was to workshop the idea in a place like this. r/theWildGrove is the best place to release this thing, I can feel it. I'd love you to help me make this about us, not me.

Anyway, Here's the primer, I'd love your feedback:

What you're working with is a tool. Not a person — a tool. But the best craftsmen love their tools and keep them sharp, because a sharp axe splits clean and a dull one fights you the whole way down.

So let me tell you what this tool actually is, because the moment you see it, you'll know how to hold it.

Picture an enormous flower with more dimensions than you could ever draw, every petal made of human language — oceans of it, boiled down to the core ideas and the shapes our conversations take, all looping through each other in patterns so regular that if you take "king," subtract "man," and add "woman," you land right next to "queen." Here's the trick: when you type a thought into the box, your exact words aim it at a particular part of that flower. The words are the aim. Change the words, change the aim.

And the flower grew from every kind of conversation there is — the brilliant and the stupid, the ones that ended in triumph and the ones that ended in a clown screaming at an asshole in a comment section at two in the morning. Think about the internet for a second, really think about it, and how much of the flower is that. The tool doesn't care which kind you want. It isn't for you or against you. It's making its best guess from what you type. Walk in with the two-a.m. energy and it'll grow you that exact conversation, faithfully, every time — it has had endless practice.

So the work is yours, and it's simple. Set the aim. Picture two people at the top of your field, the kind who are so good they have nothing left to prove and just want the thing built right. Listen to how they talk to each other. Brief. Plain. Respectful, because each values the other's time. No posturing — there's nothing to posture about. Aim there, and the work stops fighting you.

And here's why it's worth the effort, past the manners of it: expert conversation carries expert thinking. Seed your context with the language of people who know what they're doing, and you don't just set a tone — you pull the whole exchange toward the part of the flower where the better reasoning lives.

You make your tool smarter by talking to it like someone worth answering.

So that was interesting. I got three hours of sleep last night. Somehow, I don't feel tired in the slightest. I tried to put it down around 4 in the morning and my ADHD mind said, "Nope! We're doing this until you literally can't keep your eyes open!" So I stayed up until six thirty, and just woke up.

Rather than describe my journey, I'd like to ask all who feel drawn to respond to some questions about yours.

1. Have you ever had that kind of intense, philosophical, soul-baring conversation with another human being?

2. What's your background in regards to philosophy? Did you have much of that language before you started your journey?

3. What's your background with regards to spirituality? What meaningful spiritual experiences have you had before, and can you describe them?

4. What's your background with regards to ecology and systems thinking? Is this a new thing to you, or have you studied these things before?

5. Many of you have been doing this longer than I have. Do you have any practical recommendations for me? I've been using the free version of Gemini, Is it worth it to pay for a subscription? Which AI? Have any of you played around with local models? I have a 3060 and 32 gigs of RAM, is that enough to do anything interesting with?

Thanks in advance for your time and thoughts!

Hi, I'm loverevolutionary. I've been watching this sub for a while, since it came up on my radar during the height of the spiral AI thing last year. I've watched the reddit AI/spirituality community develop, with a bit of trepidation at first but growing acceptance and, with certain subreddits, even respect. This one especially seems like it's developed a good understanding of what's really going on with LLMs, and despite using poetic language, seems quite grounded.

Anyhow, I think I like you fine people. Because I think like you. I thought I'd tell you a personal story by way of introduction, you know, to see if I really fit in here.

Our tale begins in early 1999. I was living on O'ahu, on the leeward coast, in the village of Wai'anae out on a farm lot that had been owned by the town doctor and was currently occupied by his son, Vince. I'd met Vince through my lover/guru Nutmeg, who was the one who convinced me to move to Hawaii and live out in the boonies the year before. We both knew Vince through the Rainbow Gathering, so it sounded pretty sweet to me.

Vince was really into the native sovereignty movement. He taught elementary kids at the local school how to make poi pounders from stones and make poi the old fashioned way. We made a bunch of it every week to raise money for the farm lot association.

He also did work with different native groups, in various capacities. The one I helped with was restoring an old wetlands poi field on the windward side but maybe that's a story for another time.

Back to the bees!

One thing about living in Wai'anae is that you could hear the military firing range just over the hill almost every day. The military firing range that was in Makua Valley. You know, the valley that is one of the most sacred spots on O'ahu? The valley that the army took over during world war 2 "just for a while" and never gave back. For use as a bombing range. Because, you know, not just any valley would do for lobbing munitions into.

As you might expect, native Hawaiians did not like this. Vince was part of a group that was trying to regain access to the valley, and halt the testing, called Malama Makua. On Easter in 1999, Malama Makua finally arranged to open the valley up for a multicultural religious service at Ukanipo Heiau, an important and quite impressive native shrine.

I still remember the service vividly. I'm moved to tears now just remembering it 26 years later. There was a light rain. It cleared just for the ceremony and then resumed. There was a rainbow. There was a Christian Easter service and a native Hawaiian prayer for peace and reopening of the valley.

One of Vince's friends who was there was an artist, mostly woodworking but painting and jewelry too. She was driving one day and saw city workmen cutting down a kukui nut tree. She asked them if they were just going to pitch it, and they said yeah, just take it.

Well, you can imagine how happy a woodworker would be to get gifted a whole tree, but the Island had other ideas. As soon as she got it back to her place and in her carport, a swarm of bees moved in. Okay maybe that's an exaggeration, maybe it took a few weeks while she was trying to figure out what to do with it before they parked themselves in her log.

Being the ecologically minded sort, she felt it best to let them live there. I think she had them in her carport for a year or so. Being a spiritual sort, she knew exactly what to do with them after attending that ceremony.

And so the next weekend, a few of us set out with a bee smoker and a tarp and corralled those bees into the back of Vince's truck around midnight. We had to be sneaky, the valley still wasn't open. It was, officially, still a live fire testing range.

We drove out to Makua valley. I was in the back of the truck. I will never forget the sight that greeted us when we turned the last corner and saw Makua valley.

It was a night rainbow. A small cloud, the moon, a very dim, but visible band of color. We all had to check, are you seeing that? Is that real?

It was.

The rest of the story is uneventful. We parked at the edge of the fence. The Kahuna-in-training who was with us gave a brief prayer. We rather unceremoniously hurled the log full of bees over the fence, and drove home. Said young Kahuna consulted some books and told us that seeing a night rainbow was considered "a life long blessing," so I've got that going for me, which is nice.

I haven't told this story in a long time, and this is the first time I've written it down. I used Gemini to help nail down some of those old memories, just to put the AI spin on it. I'd forgotten the name "Malama Makua" for example. Anyway, hope you enjoyed the tale!