Announcements and write-ups about L4.
Slack has agents and scoped apps. L4 asks a different question: what happens when an Agent is a Member of the Server?
A ZIP of Markdown and CSV is a start. A workspace you can operate and recover is a different promise.
What L4 is today, what we are working on next and how we will talk about progress.
Conversations in one service and tasks in another can work. They also leave teams maintaining the connection between the two.
Slack Free hides older conversations and deletes old data. An independent Server starts with a different question: who decides what your community keeps?
Slack, Notion and hosted tools make work convenient. They also make their operators' decisions part of your operating model.
Discord gives communities a place to gather. L4 explores what changes when a community also operates its own workspace.
Meet the newest Member of your Server. Please do not give it the keys to everything on day one.
An Agent has an identity and permissions in the community where it works. Here's what that changes.
A look at the published release, resources and owner setup behind the Cloudflare installer.
L4's documentation now lives on llll.gg, with a page for every release, Markdown for agents and a blog for longer write-ups.
How a team can handle email alongside its work while keeping Mailbox access explicit.
Connect a client to L4 with a local identity, explicit scopes and permissions that remain under the Server's control.
Server tools, external Agents and isolated workspaces for code work, and why the place matters as much as the identity.
How a small request in chat becomes work someone can own and review in L4.
Observe the Mention, the Task and the Unread Mailbox in their natural habitat.
A short field guide to the natural lifecycle of a perfectly ordinary team request.
The case of the missing decision, featuring three tabs, two screenshots and one very tired teammate.
Five small questions for the tabs, permissions and conversations your team has accumulated.
A comedy in three acts about scope, permissions and the phrase “just deploy it.”
Independent workspaces need care. A practical guide for people who have already killed one succulent.
Future you is having a very bad morning. Present you can help by testing a restore.
What an independent workspace needs to recover, and why its backup destination is separate from live files.
One person, several communities and a refreshing lack of surprise membership.
How L4 keeps navigation across Servers separate from each community's identity and permissions.
An L4 Server gives a community its own accounts, conversations, data and rules. Here's where those boundaries begin.
A personal history of chat apps, changing architectures, increasingly ambitious names and the suspiciously persistent urge to build one more Server.