# Appreciative Holon An **Appreciative Holon** is a holon whose value system is anchored in peer recognition. Contributions are surfaced and weighted primarily through **appreciations**—explicit acts of recognition members give each other—rather than through hours logged, tickets closed, or top-down evaluation. Where a Splitter Holon distributes resources and a Managed Holon coordinates work, an Appreciative Holon decides **what counts as valuable in the first place**. The appreciation record is what feeds the holon's [value equation](/getting-started/funding-flow.md), and through that, downstream things like splits, rewards, and reputation. ## The appreciation framework Members express recognition through a simple verb. In the [HolonsBot](/software/holonsbot.md), this is: ``` /appreciate @user [reason] ``` Example: ``` /appreciate @laura for taking care of the garden ``` Each appreciation is a public, attributable signal. Over time, these signals accumulate into a transparent record of participation, visible to the whole holon via `/status`. The record fosters **coopetition**—collaborative competition where members are motivated to contribute toward shared goals in a supportive environment rather than to extract individual reward. This is one of the patterns that operationalises [THEOS](/software/the-holonic-earth-operating-system.md)'s first objective: "facilitate prosocial coordination, favouring co-creation and collaboration over competition." See [HolonsBot commands](/software/holonsbot/holonsbot-commands.md) for the full appreciation, status, and weights interface. ## How appreciations become value Appreciations are one input among several in a holon's value equation. A typical formulation: ``` Points = (Hours × Hour_Weight) + (Appreciations × Appreciation_Weight) + (Outcomes_Delivered × Outcome_Weight) Share = Points_Individual / Points_Total ``` What makes a holon **Appreciative** is the relative weight: appreciations are the dominant or defining signal. The `/weights` command lets the holon collectively decide how much each type of contribution counts. This means two holons can run identical software and produce very different cultures—one rewarding hours, another rewarding peer recognition—simply by tuning the weights. ## Why anchor on appreciation * **Captures invisible work.** Care, facilitation, emotional labor, mentorship, and relationship-building rarely show up in ticket trackers. They show up clearly in appreciations. * **Aligns with the holon's stated values.** Each holon (or membrane) defines what it values; appreciations are how members vote on that, continuously, in everyday language. * **Resists gaming.** Unlike self-reported hours, appreciations require another person to vouch for the contribution. This builds a relational rather than transactional record. * **Composes with federation.** When holons federate, appreciation data can flow across membrane boundaries, letting recognition in one community translate into standing in another. ## When to use an Appreciative Holon Choose this flavor when: * Much of the holon's real value creation is hard to measure with conventional metrics. * The community wants its **culture of recognition** to be the primary engine of reputation and reward, not a secondary nicety. * You plan to compose with a [Splitter Holon](/software/holons-types-flavor/splitter-holon.md), [Zoned Holon](/software/holons-types-flavor/zoned-holon.md), or federation contract that consumes contribution points—appreciations become a high-quality input for all of them. Appreciation is the simplest interface for making relationships economically meaningful, which is the core promise of the Holons protocol. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.holons.io/software/holons-types-flavor/appreciative-holon.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.