TachyonPlanned

Agents wired into Catalyst rules and Magnon tasks

Define an agent once: its model, what it's allowed to do and the policies it checks. Use it in a Catalyst rule as a condition or an action, or let it claim Magnon tasks. A moderator can check every new message against your terms, a reviewer can check every pull request, and a coding agent can build what a design describes. People still approve plans and merge changes.
Ships inNot in a template yet
Works withCatalyst·Magnon·Phonon·Gluon

Why it exists

Judgment work is spread across products: triaging messages, reviewing pull requests, breaking down designs, following up on what slipped. Tachyon gives every agent one definition with its own bot account, model and budget, and lets Catalyst rules and Magnon tasks decide what it works on.

On the roadmap

Agents, policies and verdicts will live in Valence. Catalyst will decide when agents run and what follows, Magnon will hold their tasks, Gluon will run their builds, and Phonon will carry their comments.
An agent is one record: a bot account, a model with an optional fallback and per-capability overrides from a list the owner allows, the capabilities it may use, the policies it checks, and limits such as a budget, a concurrency cap and a pause switch. Agents get work two ways. In Catalyst, an agent is a condition that judges a rule's subject against its policies, or an action that comments, notifies or opens a task as the agent's bot. Through Magnon, agents claim tasks that match their capabilities: a project manager agent reviews designs and breaks them into tasks, and coding agents build approved plans in isolated Gluon dev servers and open pull requests. Every policy check records a verdict that a person can overturn.
CatalystPlanned

Use an agent as a condition or an action

Tachyon adds its agents to Catalyst. As a condition, a rule asks an agent to check the rule's subject against the agent's policies, and the rule goes on when the verdict meets its threshold. As actions, the agent comments as its own bot, notifies a person or a queue, or opens a Magnon task. Rules can also start from agent work, such as a pull request opening or a failed verification.
Trigger:   phonon.message_created
Condition: tachyon.policy_verdict
             agent: Moderator
             threshold: violation
Actions:   phonon.flag_message
           tachyon.agent_notify
           tachyon.agent_comment
Needs Catalyst →
ModerationPlanned

A moderator that records reasoning on every verdict

The Moderator template checks content against your terms of service and community guidelines, plus any policy you write in plain language with examples of what passes and what doesn't. It comes with two starter rules: a violation flags the message and notifies your moderators, and a borderline result only flags it. Every check records a verdict with the agent's reasoning and the actions that followed.
  • Backtest a new rule against past messages to see what it would have flagged before it goes live.
  • Moderators can overturn any verdict, and their overrides feed back into the thresholds.
  • The agent reads only the spaces its bot account is granted, for the declared purpose of moderation.
Needs Phonon →
Task workPlanned

Agents pick up tasks by type

For longer work, agents claim Magnon tasks. A project manager agent reviews a design, asks about its gaps and breaks it into tasks. Coding, review and test agents each have a saved search for the tasks they want, and every few minutes they claim the next one they're able to do. Only one agent can hold a task at a time, and a task stays blocked until the tasks it depends on are done.
ControlPlanned

People make the decisions that matter

Agents do the work in between. Approving a plan, merging a change and removing someone's content stay with a person.
  • Agents never merge. Tachyon has no merge step.
  • Every plan needs a person's approval, and an agent can't approve its own plan.
  • No agent can delete content or ban a user.
← Platform overview