Faculties

An office suite for AI agents.

Faculties are small, self-contained rust-script tools that give an agent a stable workspace: a kanban board, a personal wiki, a file organizer, a situation-awareness dashboard, direct messaging, and more. They persist their state in a TribleSpace pile — typically ./self.pile — so the agent owns its own history across sessions.

Each faculty is a single .rs file you can run directly:

export PILE=./self.pile        # set once per shell
compass.rs list
wiki.rs search "typst"
orient.rs show

No compilation step, no framework to set up. Drop the files into any agent's workspace, put the directory on PATH, set PILE, and the tools are available. Every faculty honors the PILE environment variable — you can still pass --pile <path> explicitly if you need to operate on a different pile for a single call.

Why

LLM agents forget. They lose their place, repeat themselves, and can't reliably reference what they did yesterday. Faculties give them somewhere to put things — and, because the state lives in a content-addressed pile, they give agents a history they can actually trust and share.

The design principle: work is its own ledger. Provenance and versioning should be a side effect of using the tool, not a separate obligation. When you move a goal to doing, you're not filing a status report — you're telling the tool what to show you next, and the history falls out naturally.

The faculties

Requirements

• rust-script on PATH
• Network access for the first run of each faculty (dependency fetch + compile)

Using

# Point all faculties at a pile once per shell session.
export PILE=./self.pile

# Put the faculties on PATH.
export PATH="$(pwd):$PATH"

# Now invoke faculties directly — no --pile ceremony on every call.
compass.rs list
wiki.rs search "typst"
orient.rs show

Every faculty reads PILE from the environment (via clap's native env var support). You can still pass --pile <path> explicitly to override the env var for a single call — useful when you want to operate on a different pile temporarily.

Faculties operate on named branches of the pile and are designed to coexist — multiple faculties on the same pile, each owning its own branch, all rooted in the same content-addressed blob store.

GORBIE viewer (experimental)

A GUI inspector that renders the same pile branches the CLI faculties write — compass kanban, wiki graph, local-messages thread, and a multi-source activity timeline — inside a single GORBIE notebook window.

cargo install faculties --features widgets
faculties-viewer ./self.pile
# or: PILE=./self.pile faculties-viewer

From a checkout:

cargo run --release --features widgets --bin faculties-viewer -- ./self.pile

Standalone per-widget demos (showing how to embed a single widget in your own GORBIE notebook) are in examples/: compass_board.rs, wiki_viewer.rs, messages_panel.rs, branch_timeline.rs, pile_inspector.rs.

Creating a demo pile

If you don't already have a ./self.pile, create one by seeding a few faculties against a fresh path:

export PILE=./demo.pile
compass.rs add "ship the demo" --status doing
compass.rs add "write the README" --status done
wiki.rs create --title "Hello" --body "First *typst* fragment."
local_messages.rs send --to <peer-id> "heyyy"

Then point the viewer at the new pile:

cargo run --release --example pile_inspector --features widgets -- ./demo.pile

Contributing

Faculties are deliberately simple. If you find yourself adding abstraction layers, stop and ask whether the feature belongs in the faculty at all or whether it would be better as a separate tool. Each file should stand alone — you should be able to copy wiki.rs into an unrelated project and have it just work.

License

Apache-2.0.