What is the Feluda Journal?

What is the Feluda Journal?

The Feluda Journal is a built-in workspace for saving and reviewing useful information over time.

It can contain:

• entries written by AI during a Workbench conversation;
• results created by a workflow;
• recurring output from scheduled workflows; and
• notes that you write yourself.

Journal entries are stored with your local Feluda data.

This makes the Journal useful for reports, research notes, summaries, decisions, monitoring results, and other information you want to return to later.

What you can do in the Journal

The Journal lets you:

• browse saved entries;
• open and read earlier results;
• add your own notes;
• write entries in Markdown;
• sort entries by date;
• monitor a selected journal for new entries; and
• review information created by workflows and AI tools.

You do not need to use the Journal for every task.

Use it when the result should remain available after the conversation or workflow run ends.

Why the Journal is useful

Workbench and RunFlows are designed around active tasks.

The Journal is designed around information you want to keep.

For example, you may use it to store:

• a daily briefing;
• a weekly project review;
• meeting summaries;
• research findings;
• security observations;
• content ideas;
• investigation notes;
• workflow reports; or
• personal working notes.

Instead of searching through several old conversations or completed runs, you can return to the Journal and review the saved entry.

Journal entries

A Journal entry is one saved piece of content.

An entry may include:

• a title;
• a date and time;
• headings;
• paragraphs;
• bullet points;
• numbered steps;
• tables;
• links;
• code blocks; or
• other Markdown formatting.

A clear title makes the entry easier to find and understand later.

For recurring content, include the date or reporting period in the title.

For example:

Weekly Project Review — 2026-06-08

is clearer than:

Weekly Project Review

Manual notes

You can write your own Journal entries.

Manual notes are useful when you want to:

• record a decision;
• save a useful idea;
• add context to an AI-generated result;
• keep a project log;
• document a review;
• record a follow-up action; or
• preserve information that does not belong in a workflow.

The built-in editor supports Markdown, so you can organise a note with headings, lists, links, and other readable formatting.

AI-written entries

Feluda can make a Journal tool available to an AI model.

When that tool is enabled, the model may be able to create a Journal entry during:

• a Workbench conversation;
• a Studio workflow;
• a RunFlows execution; or
• a scheduled workflow run.

The tool must be available and enabled where the action is requested.

The model should also receive a clear instruction explaining:

• what to save;
• the entry title;
• the required sections;
• the source information;
• what not to add; and
• how missing information should be handled.

A simple AI Journal example

In Workbench, you could enable the Journal tool and write:

Use the Journal tool to create an entry titled
"Customer Interview Notes — 2026-06-08".

Include:
1. a short summary;
2. the main customer needs;
3. repeated concerns;
4. action items; and
5. unanswered questions.

Use only the interview notes below.
If information is missing, write "Not provided."
Do not guess.

Interview notes:
[Paste the notes here.]

After the model responds:

1. review the Workbench Activity log;
2. confirm that the Journal tool was called;
3. open the Journal; and
4. review the saved entry.

Do not rely only on the model saying that the entry was created.

Workflow entries

A workflow can write its result to the Journal.

For example:

Input
→ Summarise
→ Extract Actions
→ Write Journal Entry
→ Output

This is useful when the workflow produces information that should remain available after the run finishes.

Common workflow uses include:

• meeting summaries;
• research findings;
• recurring reports;
• monitoring results;
• review notes; and
• project updates.

Test the Journal action manually before using it in a recurring or scheduled workflow.

Scheduled Journal entries

A scheduled workflow can create Journal entries automatically.

For example, a daily workflow may:

1. retrieve approved information;
2. summarise it;
3. write a dated Journal entry; and
4. finish with a reviewable output.

This can be useful for:

• daily briefings;
• weekly reports;
• recurring research;
• monitoring logs;
• regular project updates; or
• periodic review notes.

Every scheduled Journal workflow should have a reviewer.

Automatic entry creation does not remove the need to check the content.

Use clear entry titles

A good title explains what the entry contains.

Useful titles include:

• Daily Operations Briefing — 2026-06-08;
• Weekly Project Review — Week 23;
• Customer Interview Findings — North Region;
• Research Notes — Local AI Providers; or
• Security Review — June 2026.

Avoid titles such as:

• Note;
• Report;
• Entry 1;
• Test; or
• Final.

Clear titles reduce confusion when the Journal contains many entries.

Use dates for recurring entries

Add a date, week, month, or reporting period when similar entries are created repeatedly.

For example:

• Daily Briefing — 2026-06-08;
• Weekly Support Review — 2026-W23;
• Monthly Research Summary — June 2026.

This helps you:

• distinguish repeated entries;
• sort and compare results;
• identify missing periods;
• avoid accidental duplicates; and
• review changes over time.

Markdown formatting

Journal entries support Markdown.

This lets you use:

• headings;
• bold and italic text;
• bullet lists;
• numbered lists;
• links;
• tables;
• quotations; and
• code blocks.

Use formatting to improve readability.

Avoid adding so much formatting that the actual information becomes harder to find.

A practical entry structure

For a recurring report, use a consistent structure.

For example:

# Weekly Project Review

## Summary

[Short overview]

## Completed Work

* [Item]

## Blockers

* [Item]

## Upcoming Deadlines

| Owner | Task | Deadline |
|---|---|---|

## Decisions Needed

* [Decision]

## Unanswered Questions

* [Question]

A consistent structure makes entries easier to compare.

Sort entries by date

The Journal can sort entries by date.

You can view:

• newest entries first; or
• oldest entries first.

Use newest-first sorting for daily review.

Use oldest-first sorting when you want to follow a project or investigation from the beginning.

Sorting changes the display order.

It does not change the entry content.

Browse and review entries

Open an entry to read its full content.

Review:

• the title;
• the date;
• the source;
• the main findings;
• missing information;
• unsupported claims;
• follow-up actions; and
• whether the entry is still current.

AI-written entries should be checked against the original source when accuracy matters.

Journal Monitor

Journal Monitor lets you watch a selected journal for new entries in real time.

It can be useful when:

• a workflow is still running;
• several AI agents write entries;
• scheduled workflows produce recurring results;
• you are monitoring a long process; or
• you want to see new findings as they are saved.

The monitor helps you notice new activity.

It does not replace reviewing the entry itself.

A Journal Monitor example

Imagine that a scheduled research workflow writes a new summary each morning.

You can monitor the related journal to see when the new entry appears.

Then:

1. open the entry;
2. review the title and date;
3. compare the findings with the returned sources;
4. check warnings or missing details; and
5. decide whether follow-up work is needed.

The monitor shows that something was added.

Human review confirms whether the result is useful.

The Journal and RunFlows are different

RunFlows shows the execution of a workflow.

The Journal stores entries that should remain available later.

Area	Main purpose
RunFlows	Start workflows and review live or completed execution output
Journal	Keep and browse saved notes, reports, and workflow entries

A workflow can return a result in RunFlows and also save an entry to the Journal.

Check both when the workflow is designed to do both.

The Journal and Workbench are different

Workbench is designed for interactive AI conversations.

The Journal is designed for saved information.

Use Workbench when you want to:

• ask questions;
• test instructions;
• compare models;
• use tools interactively; or
• improve a result through follow-up messages.

Use the Journal when you want to:

• preserve a result;
• add a permanent note;
• review recurring entries;
• compare reports over time; or
• keep a structured record.

Journal tools and permissions

A Journal tool can create or update saved information.

Treat it as a write action.

Before enabling it, confirm:

• what the tool can do;
• which journal or destination it uses;
• what content will be written;
• whether the title is correct;
• whether duplicate entries may be created; and
• whether the result can be reviewed.

Test the action with non-sensitive information first.

Confirm every important write

After an AI model or workflow writes to the Journal:

• check the Activity log or workflow output;
• open the Journal;
• find the expected entry;
• review the title;
• review the content;
• confirm the correct date or reporting period; and
• check whether a duplicate was created.

A successful tool call does not guarantee that the saved content is correct.

Avoid duplicate entries

Duplicate entries can appear when:

• the same workflow runs twice;
• a schedule overlaps;
• a timed-out write is retried;
• two schedules use the same destination;
• a title never changes; or
• a manual run and scheduled run create the same report.

Reduce duplicates by:

• using dated titles;
• checking the Journal before retrying;
• reviewing active schedules;
• preventing overlapping runs; and
• removing duplicate schedule configurations.

Review missing entries

When an expected entry does not appear, check:

• whether the workflow ran;
• whether it reached the Journal step;
• whether the Journal tool was available;
• whether the correct destination was selected;
• whether an error occurred;
• whether the entry used another title; and
• whether the workflow stopped earlier.

Review RunFlows or Schedule Manager history before repeating the action.

Protect sensitive information

Journal entries are stored with your Feluda user data, but normal privacy checks still apply.

Before saving sensitive information:

• confirm that it is necessary;
• remove details that are not needed;
• review which model processed it;
• check whether any cloud provider received it;
• review enabled tools;
• confirm the Journal destination; and
• protect access to the computer and user account.

Local storage does not replace normal device security.

Journal data and updates

Journal entries are stored separately from the Feluda application files.

Normal application updates do not replace your personal Journal data.

Keep normal backups of important information according to your own device and organisation practices.

Do not treat the Journal as the only copy of information that must be preserved permanently.

Use the Journal for review, not only storage

A useful Journal is reviewed regularly.

Use it to:

• compare recurring reports;
• identify repeated problems;
• follow project changes;
• track decisions;
• notice missing periods;
• review trends; and
• prepare follow-up work.

Saving an entry is only the first step.

The value comes from using the information later.

Keep journals understandable

Use consistent titles and entry structures.

For example:

• Research — Daily Findings — 2026-06-08;
• Support — Weekly Review — 2026-W23;
• Project Atlas — Decision Log — 2026-06-08.

Consistency makes browsing and sorting more useful.

Avoid mixing unrelated content under unclear titles.

Keep human review where needed

Human review is especially important when Journal content affects:

• customers;
• employees;
• money;
• contracts;
• legal rights;
• health;
• safety;
• security; or
• access to important services.

The Journal can preserve an AI-generated summary, report, or recommendation.

It should not turn an unreviewed result into an approved decision.

A practical Journal routine

Use this process:

1. Decide what information should be kept.
2. Choose a clear entry title.
3. Use a consistent Markdown structure.
4. Create the note manually or through an approved tool.
5. Confirm the entry in the Journal.
6. Review important details against the source.
7. Use dates for recurring entries.
8. Check for duplicates.
9. Monitor new entries when a long or scheduled process is active.
10. Review and use the saved information later.

The Journal gives Feluda a place to keep useful results beyond one conversation or workflow run.