Galaris
GitHub

Galaris

Lasting goals and cycles

Organise recurring work with Goals, bounded cycles and a human referrer. Use a separate Process to track an external workflow.

Choose the work object

Use a Task for a bounded deliverable, a Goal for a purpose pursued over several cycles and a Process for work executed by an external engine. These objects have different responsibilities and remain linked where appropriate.

Advance through separate cycles

A Goal stores its purpose and follow-up. Each cycle creates an ordinary Task, then a follow-up mechanism examines results and evidence before deciding to continue or conclude. The model is not kept running continuously between cycles.

A goal ready to resume — The goal brief, assigned agent and human contact; this example remains paused.
A goal ready to resume — The goal brief, assigned agent and human contact; this example remains paused.C23
Cycle history — Existing cycles show progress, continuation decisions and missing information. Demonstration content replaces private data; historical states are preserved.
Cycle history — Existing cycles show progress, continuation decisions and missing information. Demonstration content replaces private data; historical states are preserved.C24

An external process keeps its own record

A Process has its definition, input, run state and output. It can continue outside the agent runtime and return a result to the originating work. Use the dedicated process page for engine capabilities and recovery details.

Process executions — Historical n8n runs with their durations and statuses.
Process executions — Historical n8n runs with their durations and statuses.C25

Set the rhythm and responsibilities

A Goal uses either a frequency between cycles or a parent goal as its trigger. Weekly work windows limit permitted days and hours. The goal tree remains inspectable without dependency cycles.

Description and follow-up are protected documents available in the library. Each cycle creates a Task and retains its verdict, evidence, calls and cost. Pause, resume and immediate-cycle requests remain explicit actions.

Ask the human referrer for a decision

An agent can send a correlated question to its human referrer. Reminders are spaced 24 hours apart, with a configurable count of one by default. Without an answer by the deadline, the Goal pauses. A response may resume it depending on state.

To start work from a meeting or alarm, use calendars.

Find each goal’s documents

Description, tracking and deliverables linked to a Goal’s tasks can be filed in your personal Goals / goal name folders. Provenance and access determine filing; a mention in a title is insufficient. Existing manual filing is preserved, as are other users’ personal folders.

A request for an immediate cycle persists until its Task is created, without bypassing a global pause. Retrying follow-up evaluates the existing result; it does not automatically repeat the work.