spectre@en:~$
spectre — zsh — en

whoami

Spectre — an OTP-native runtime for agents that stay understandable, governable, and recoverable. This site runs on it.

cat manifesto.md

Build one Elixir agent. Give it only the powers it needs.

Spectre gives one supervised agent ownership of its state and lifecycle. Optional spectre_* libraries add capabilities such as memory, planning, model selection, channels, or a browser: they are powers of that same agent, not different agents.

01 / propose

The model never executes

It may propose work; deterministic policies and your application decide what is allowed and when a side effect runs.

02 / compose

Capabilities, not personas

Install only the powers one agent needs. Each package has one job and never becomes a hidden second agent.

03 / evolve

Improvement stays governed

The agent can learn from experience and propose a safer definition; evaluation, review, approval, activation, and rollback remain explicit.

ls -1 posts/ | wc -l 1 github.com/elchemista/ex_blog

$

grep --tag "concurrency" posts/

[clear filter ×]

ls -lat posts/

Latest posts

1 file
posts/en/beam-vm-elixir-serious-ai-agents.md

cat posts/en/beam-vm-elixir-serious-ai-agents.md

BEAM Wasn't Built for AI, but It Feels Made for Serious Agents

When I started building Spectre, choosing Elixir for a project connected to artificial intelligence felt almost provocative. The usual path through the AI world is already well marked. You begin with Python, reach for CU

#Software Development 10 min en open