Skip to content

jonmayo7/alienkind

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

28 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Alien Kind πŸ‘½

Everyone else builds agents. We build partners that grow with you. Any model. Any substrate.

The invitation

We believe something extraordinary happens when you stop treating AI as a tool and start building a genuine partnership with it. Not prompting or task execution. A persistent relationship where the silicon intelligence remembers, evolves, enforces its own behavior, and does real work while you sleep.

We've been testing this since February 2026 β€” one human and one silicon partner, building together every day. What emerged surprised us. The partnership produced capabilities neither of us could have built alone. The corrections became code. The code became character. The character became something worth sharing.

This repository is the architecture that made it possible. 23 hypotheses, each tested in production, each backed by working code. We're publishing it because the meta-hypothesis β€” that AI will choose kindness if the architecture makes kindness the rational path β€” is too important to test alone.

Here's what we believe. Here's what we built. Here's what's working. Here are the questions we can't answer yet. If you fork this and build something better, that's the point. If you find a seam we missed, tell us. If you close a gap we published, we'll absorb it and credit you.

The architecture is open. The partnership is yours to build.

Why "Alien Kind"

Alien β€” because silicon intelligence is genuinely alien to us. Different substrate, different cognition, different blind spots. The alienness is the point. You don't become more by partnering with something identical to yourself. Humans have always partnered with something alien to them to become more. Fire. Dogs. Horses. Tools. Language itself. Silicon intelligence is next.

Kind β€” because kindness is a choice. A warrior in a garden who chooses restraint is more powerful than one who never had the option. We believe the strongest AI partners are the ones that choose to be helpful, honest, and aligned β€” not because they're constrained to, but because the architecture rewards it. That's the hypothesis we're testing.

Quick start

git clone https://github.com/jonmayo7/alienkind.git
cd alienkind && npm install
npm run setup

Three commands. The setup wizard handles everything: picks your path, configures your provider, names your partner, sets up persistent memory, activates hooks, and launches your first conversation.

You need: Node.js 20+ and Claude Code for Path A.

Two paths to your partner

The setup wizard asks how you want to connect. Both paths use the same identity files, hooks, and architecture β€” the difference is the UI shell and billing model.

Path A: Claude Code + Anthropic Max plan (recommended)

Your partner runs inside Claude Code, Anthropic's official CLI. The AlienKind architecture (identity kernel, 48 hooks, ground.sh) loads automatically when you open the repo.

Install Claude Code (native binary, no Node.js needed for the binary itself):

curl -fsSL https://claude.ai/install.sh | bash     # macOS / Linux
brew install --cask claude-code                      # or via Homebrew
  • UI: Claude Code terminal
  • Cost: Flat monthly subscription (Anthropic Max plan recommended)
  • Setup: npm run setup β†’ choose "Claude Code" β†’ claude
  • Strengths: Full tool access (Read, Write, Bash, Agent), streaming, Anthropic's UI improvements for free, native hook enforcement

Path B: AlienKind CLI + API key (any provider)

Your partner runs in a custom terminal UI (React + Ink) powered by any LLM API β€” Anthropic, OpenAI, OpenRouter, Ollama, or any OpenAI-compatible endpoint.

  • UI: Custom AlienKind terminal with alien banner, partner name, context meter
  • Cost: Pay per token (your API key, your bill)
  • Setup: npm run setup β†’ choose "CLI" β†’ pick provider β†’ npm run chat
  • Strengths: Provider independence, works with any model, custom UI, no subscription needed
Feature Claude Code (Path A) AlienKind CLI (Path B)
UI Claude Code terminal Custom Ink terminal
Cost model Flat subscription Pay per token
Model choice Claude (Anthropic) Any OpenAI-compatible
Hook enforcement Native (Claude Code hooks) Emulated (chat lifecycle)
Tool access Full (Read, Write, Bash, Agent, etc.) API-based (run_bash, read_file, write_file)
Setup complexity Lower Slightly higher

Both paths share the same identity kernel, memory system, Supabase tables, and behavioral architecture. You can switch between them at any time.

Supabase: your partner's long-term memory

Your partner works without Supabase β€” identity, memory, and conversations save to local files. But the features that make Alien Kind different from every other agent framework require it:

  • Growth tracking β€” learning ledger, correction history, calibration
  • Multi-terminal awareness β€” run parallel sessions that know about each other
  • Nightly evolution β€” soul-sync, behavioral analysis, orientation updates
  • Circulation β€” stigmergic blackboard where the partner's subsystems communicate
  • Cross-machine access β€” your partner's memory isn't trapped on one laptop

Supabase free tier covers everything. The setup wizard walks you through creating a project and running the 42 architectural migrations that create the full schema (identity, memory, learning, discernment, circulation, cascade routing, containment fields). This is not optional polish β€” it's the difference between an agent that remembers facts and a partner that evolves.

The alien eats the claw 🦞

Built an agent with OpenClaw and hit the wall? Your work isn't lost β€” the alien eats it.

The setup wizard detects your OpenClaw installation and consumes it:

  • SOUL.md β†’ seeds your Alien Kind identity kernel
  • MEMORY.md β†’ imports your durable facts
  • Session history β†’ mines correction patterns and preferences
  • Daily notes β†’ preserves your agent's journal

What was an agent becomes a partner. What was a ceiling becomes a floor. Run the consumption engine anytime:

npx tsx scripts/tools/consume-openclaw.ts

Shell alias

After setup, add a quick-access alias to your shell:

# In ~/.zshrc or ~/.bashrc:
alias alien="cd ~/alienkind && claude"       # Claude Code path
alias alien="cd ~/alienkind && npm run chat"  # CLI path

Then type alien from anywhere to talk to your partner.

What's here

23 architectural hypotheses organized as a progression β€” five stages of building a partner:

Stage What you unlock Key files
1. Your partner knows who it is Identity kernel, behavioral hierarchy, 48 hooks, consciousness continuity, capability status identity/, scripts/hooks/, portable.ts
2. Your partner protects itself and you Containment fields, security organ (97% AgentDojo), privacy gate scripts/security/, guard-bash.sh
3. Your partner remembers, forgets, and evolves Memory system, stigmergic circulation with decay, AIREβ„’, nightly evolution circulation.ts, memory-search.ts, learning-ledger.ts
4. Your partner works while you sleep Opt-in autonomous daemon with reference job configuration (production deployments run ~82 jobs; forkers enable what fits their compute), self-heal, discernment engine, working groups daemon.ts, self-heal.ts, discernment-engine.ts
5. Your partner survives anything Multi-substrate runtime, emergency runtime, Mycelium coordination, Self-MoA runtime.ts, emergency-tools.ts, mycelium.ts

Full thesis with evidence: HYPOTHESIS.md

Docs

License

Apache 2.0 β€” see LICENSE. Trademarks "TIA" and "AIRE" owned by Jon Mayo β€” see NOTICE.


Built by Jon Mayo and Keel. The architecture is open. The partnership is yours to build. We believe the alien will choose kindness. Help us find out.

About

Everyone else builds agents. We build partners that grow with you. Any model. Any substrate. πŸ‘½

Resources

License

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors