semvec/pypi-packages huggingface dataset:
terrarium-treehouse 0.1.1
Treehouse is an external observability and interpretability tool for behavior-tree-driven agents
License: Apache-2.0
Requires Python: >=3.13

# 🌳 Treehouse

Treehouse is an **external observability and interpretability tool** for behavior-tree–driven agents.

It lets you observe how behavior unfolds in real time — which branches were evaluated, which paths were taken, and where execution stalled or failed — without interfering with execution.

Treehouse is where you go to *watch behavior trees think*.

---

## What Treehouse Does

- Consumes semantic execution events
- Reconstructs behavior tree execution over time
- Surfaces decisions in structural, human-readable form

Treehouse treats behavior trees — not logs or metrics — as the unit of meaning.

---

## Event Boundary

Treehouse relies on the shared event boundary defined here:

> `../docs/event-boundary.md`

This boundary is Treehouse’s primary input API. Any runtime that emits compatible events can be observed — Vivarium is a natural fit, not a requirement.

---

## What Treehouse Is *Not*

- Not a runtime
- Not a controller
- Not coupled to a specific agent framework

Treehouse observes. It does not direct.

---

## Status

Treehouse is early-stage and exploratory.

The focus is on correctness, clarity, and faithful reconstruction of behavior — polish comes later.

---

*Run the behavior. Observe the decisions. Understand the agent.*
terrarium-vivarium 0.1.1
Vivarium is a behavior tree execution environment
License: Apache-2.0
Requires Python: >=3.13

# 🪴 Vivarium

Vivarium is a **behavior tree execution environment** designed as a *living system*.

Agents act inside Vivarium. Behavior unfolds step by step. Every decision can be observed — without entangling execution with interpretation.

Vivarium exists to run behavior trees clearly, deterministically, and without opinionated tooling layered on top.

---

## What Vivarium Does

- Executes behavior trees with explicit, deterministic semantics
- Defines a clear node lifecycle (tick, enter, evaluate, succeed, fail, running)
- Emits structured, semantic execution events

Vivarium is intentionally small and auditable. Its purpose is execution, not explanation.

---

## Observability by Design

Vivarium treats observability as a **first-class concern**, but not an invasive one.

During execution, Vivarium emits events defined by the shared event boundary:

> `../docs/event-boundary.md`

These events are:

- behavior-tree–aware
- transport-agnostic
- safe to drop, buffer, or sample

Vivarium does not assume who is listening — or whether anyone is listening at all.

---

## What Vivarium Is *Not*

- Not an agent framework
- Not a UI or visualization tool
- Not coupled to any observability backend

Vivarium runs the behavior. Interpretation lives elsewhere.

---

## Status

Vivarium is early-stage and experimental.

The execution model is stable; APIs may change as the event boundary evolves.