Features

A scannable catalog of everything the Holons ecosystem can currently do

This page is the catalog of what's working today — grouped by what you can do, not by which package implements it. Each capability links to the page with the deep-dive.

The implementation lives in the Harvest monorepo: one shared @holons/core, five interfaces (web, Telegram, CLI, AI agent, MCP server), and the HoloSphere substrate beneath all of them.

Coordination

How groups organize work, time, and attention.

Unified Quest model — tasks, proposals, events, offers, and requests are one shape with one lifecycle, so everything composes cleanly. → Tasks
Quest creation — from a plain title, from a design-stream step, from a recursive QuestTree, or from a ritual session.
Participants — join, leave, toggle membership on any quest (pure, instant in every UI).
Quest completion with plan/execute split — preview what completion will do (who scores, which dependents unblock, which REA events fire) before committing.
QuestTree (recursive backcasting) — generate nested goal trees from a vision statement, with holonic metadata per node (skills required, impact category, success metrics).
Ritual sessions → design streams — turn a wish-statement and an advisor panel into a set of quests, preserving the ritual provenance.
Calendar — events, recurring events, scheduling.
Checklists — recurring and role-based task lists.

Recognition & contribution tracking

Where what gets done gets seen.

Appreciations — /appreciate @user [reason] style peer recognition, public and attributable. → Appreciative Holon
Value equation — each holon defines weights for hours, appreciations, completed quests, currencies, and more. → Scoring
Per-user scoring — total score, breakdown by field, percentage share of the holon.
Per-action scoring — answer "what would I get for this?" before doing it.
All-user scoring — full leaderboard / equity view in one call.
Live subscriptions — score and equation changes propagate to every UI in real time.
Time-decay weights and currency contributions — built in to the equation model.
REA event ledger — every recognized action emits a typed event into an append-only stream that feeds scoring, federation, and audit. → REA Accounting

Governance

How holons decide.

Council proposals — full lifecycle: create, save, vote, tally, derive status. → Council
Consent-based voting — agree, block, abstain. A single block by a member with standing keeps a proposal from passing.
Quorum thresholds — per-proposal, with a sensible default.
Pure tally helpers — every UI renders the same live tally without round-tripping to storage.
DNA changes via Council — adding chromosomes or evolving the DNA sequence happens through proposals, binding identity drift to consent.
Role management — /setroles, /assignroles, role-based checklists.

Resources

What flows through the holon.

Shared expenses with multi-currency — log a cost, split it, see the credit matrix and per-user net balances. → Expenses
Currency normalization — "EUR", "euros", "Euro" all become eur; multi-currency totals are additive.
Receipt attachments — pictures (Telegram file IDs) per expense.
Community library — tools, books, equipment, lent and borrowed with state tracking. → Library
Deposit accounting — items with a value produce REA deposit events on borrow and release events on return.
Ratings and issues — per-item ratings, reviews, and issue reports with resolution status.
Shopping lists — shared lists of items the holon needs, addable via /buy.
Wants and offers — /request what you need, /offer what you can give. /board to see everyone's.

Identity & culture

What the holon stands for.

DNA chromosomes — three types: value, tool, practice. Each has a name, description, and optional icon/color. → DNA
DNA sequence — an ordered, unique, length-bounded (≤20) selection from the chromosome library that defines the holon.
Seed defaults — new holons start with a curated set of default values, tools, and practices.
Live DNA validation — duplicates, length overruns, invalid references, missing-required all surface as typed errors.
Versioned sequences — DNA has a version counter for optimistic concurrency.
Membership zones — Core Stewards / Active Contributors / Ambassadors / Supporters, with movement based on involvement. → Zoned Holon
Personal values and needs — /ivalue, /values, /ineed, /needs capture per-user signals visible across the holon.

Federation

How holons connect to each other.

Three publish targets — broadcast to all federated partners, send to one specific partner, drop into an H3 cell. → Federation
Hologram envelope — published items get provenance metadata (origin holon, lens, timestamp, source identity).
Settings hex — a geographic discovery cell: anyone subscribed to the cell sees every published item from every member holon in the region.
Federation snapshots — read-only view of partners and partner names.
Nostr-keyed source identity — federationSourceId can be a Nostr pubkey, separating identity from holon ID.
Best-effort propagation — one bad destination doesn't block the rest; denials surface via callback and PublishOutcome.errors.
/federate and /fork — bot commands to bind and unbind federations from chat.

Interfaces

Five ways to interact with the same data.

Web dashboard (apps/web) — SvelteKit app with Mapbox + H3 geospatial views, schema-driven forms, federation UI, interactive holon network graph.
Telegram bot (@holons/telegram-ui) — Telegraf with scenes, inline keyboards, Puppeteer screenshots. The everyday surface for most communities. Full commands reference.
Command-line interface (@holons/text-ui) — holons binary with REPL and one-shot modes; argument grammar; auto-generated help.
AI agent loop (@holons/ai-ui) — holons-ai CLI that runs an in-process Claude tool-use loop against the shared command registry. Embeddable as a library via runAgent().
MCP Server (@holons/mcp-ui) — ~100 tools across 14 domains, stdio or SSE-over-HTTP. Any MCP client (Claude Desktop, IDE plugins, custom agents) can drive a holon end-to-end.

All five share the same @holons/core functions, so an action initiated in any of them produces identical effects in every other.

AI integration

What makes a Claude agent a first-class member.

MCP tool surface — ~100 tools spanning tasks, council, scoring, DNA, library, expenses, calendar, users, federation, holosphere, checklists, shopping, settings, and commands. → MCP Server
Two transports — stdio (Claude Desktop / IDE integration) or SSE on HTTP (network-reachable agents).
Identity resolution — HOLONS_ACTOR_* env vars (or per-call overrides) attribute every write to a specific user.
HoloSphere connection per call — actor + substrate are resolved fresh, so the server is stateless and safely concurrent.
In-process agent loop — @holons/ai-ui embeds Claude inside the holon's own runtime; useful for cron jobs, webhook handlers, embedded intelligence.
Prompt caching — system prompt + tool definitions cached with one ephemeral breakpoint so multi-turn sessions are cheap.
Auto-tool generation — every CoreCommand becomes an Anthropic tool with a JSON Schema generated from its params; one file, four interfaces.

Spatial substrate

The data layer beneath everything.

H3 geospatial holons — every holon can be a hierarchical hex cell; parent/child/neighbor lookups are constant-time. → HoloSphere
Multi-resolution holons — neighborhood → city → region → continent, with natural aggregation via cell-to-children traversal.
GunDB distributed storage — peer-to-peer, real-time, offline-tolerant, no central server required.
Lenses — named categories of data per holon (tasks, expenses, rea_events, dna_sequence, …) that evolve independently.
JSON Schema validation per lens — strict mode rejects malformed writes at the substrate level.
Real-time subscriptions — subscribe(holon, lens, callback) for live change feeds.
Soul references — federated data uses lightweight pointers; the original lives in one space, copies resolve to it on read (single source of truth, no storage duplication).
Auto-propagation — opt-in flag on writes to propagate to every federated space automatically.
AI summarization — optional OpenAI integration to compute lens summaries across scales.
Identity-aware writes — writeWithIdentity attaches the actor; canWriteToHolon checks standing.
Message federation — track and update messages across federated chats.

Agreements

How commitments become legible.

Memorandum of Understanding template — written agreement covering vision, contributions, allocation, governance, conflict resolution, appreciation, review. → MoU
Commitment Registry — published commitments, validation workflows, reputation updates on completion. → Funding Flow
Two-layer agreements — human-readable text + programmable contract configuration that operationalises it. → Agreements

Holon flavors (composable patterns)

Not exclusive types — most holons are several at once. → Holon types (flavor)

Splitter Holon — routes incoming resources via configurable splits; the canonical dial controls internal vs external flow.
Managed Holon — coordinated day-to-day through HolonsBot (or equivalent); the common starting point.
Zoned Holon — concentric membership zones for differentiated participation depth.
Appreciative Holon — value system anchored in peer recognition.

Implementation status

Mostly stable; a few packages are early.

Component

Version

Notes

@holons/core

0.1.x

Active; shape stable, domains evolving

apps/web (harvest-web)

2.0

Production-grade dashboard

@holons/telegram-ui

active

Mixed TS+JS; the most-tested surface

@holons/text-ui

0.1.0

CLI/REPL — works, small surface

@holons/ai-ui

0.1.0

Early; command registry currently a fallback, will move to @holons/core/commands upstream

@holons/mcp-ui