Concepts

Metryon uses a few small building blocks. Their boundaries are deliberate, but they are meant to feel natural in daily use.

Inbox

The Inbox is where unplanned work arrives. An item may come from GitHub, Jira, another integration, or a quick note you add yourself.

Nothing in the Inbox is a commitment yet. It is a place to read, decide, and move on. You can turn an item into a task, connect it to existing work, or leave it out of your plan.

Goals

A goal describes an outcome worth reaching. It holds the reason behind a group of tasks and makes “done” easier to recognize.

Goals are useful for work that spans several steps. They are optional for small fixes, maintenance, and other work where an extra layer would add little value.

Tasks

A task is a piece of work you can act on. Tasks move through Todo, In progress, and Done.

State and priority answer different questions. State says where the work stands; priority says what needs attention first. Keeping them separate means urgent work can be seen clearly without distorting its progress.

Notes

Notes hold information that matters but does not need to become work. They can keep research, decisions, references, or loose thoughts close to the goals and tasks they support.

Integrations

Integrations bring outside work into Metryon and keep a link to its source. GitHub pull requests and Jira issues, for example, can appear in the Inbox without losing their identity or history.

Metryon remains the place where you organise the work. The connected service remains the home of the external record.

Ways of working

Execution can be manual, AI-assisted, or handled by an agent. These are choices for doing the work, not different kinds of task.

Manual work stays first-class. Adding an agent does not move ownership away from you; it gives a task another way to proceed.

Templates and workflows

A template gives recurring work a useful starting shape: its defaults, expected context, and available actions.

A workflow describes what happens after an action begins. It can move a task, call an integration, involve an agent, or pause for approval. Templates choose workflows; they do not hide copies of the same process inside every item.

Agents and their runtime

An agent definition describes a role: how it should work, which tools it may use, and where its limits are. The model and the program that runs it are separate choices.

This separation lets the same kind of agent work through different providers or harnesses without changing the task itself. Metryon tracks the run; the runtime owns the underlying process and terminal session.

Permissions

Actions that affect external systems pass through explicit permission and approval rules. An approval allows an action to be attempted; it is not treated as proof that the action succeeded.

This distinction matters when a network request is interrupted or its result is unclear. Metryon keeps that uncertainty visible instead of silently trying again.

How the pieces fit

An Inbox item can become a task. A task may contribute to a goal and may use a template. An action from that template can start a workflow, which may remain manual or involve integrations and agents. Permissions stay between the workflow and any external change.

The structure is there to preserve context and control. In ordinary use, the path should still feel short.