Use the Feluda Journal

Use the Feluda Journal

The Feluda Journal is where you keep notes, reports, findings, and workflow results that should remain available after a conversation or run ends.

You can use it to:

• write your own notes;
• review entries created by AI tools;
• keep workflow results;
• organise recurring reports;
• sort entries by date;
• compare information over time; and
• watch for new entries with Journal Monitor.

This guide explains how to use the Journal clearly and safely.

Open the Journal

Select Journal from the Feluda sidebar.

The Journal page shows your available entries and the area used to read or write content.

A new Feluda setup may have few or no entries.

The list grows as you:

• create notes manually;
• ask an AI model to write an entry;
• run workflows that use the Journal tool; or
• schedule workflows that save recurring results.

Understand the Journal layout

The Journal workspace is designed around two main activities:

• finding an entry; and
• reading or editing its content.

Depending on your current version and selection, you may see:

• the entry list;
• entry titles;
• dates or timestamps;
• sorting controls;
• the Markdown editor;
• rendered entry content; and
• Journal Monitor.

Select an entry to open it.

Create a manual entry

Use the option for creating a new Journal entry.

Give the entry a clear title.

Then write the content in the Markdown editor.

A useful manual note might include:

# Project Decision

## Decision

The team approved the revised homepage structure.

## Reason

The new structure makes the main product areas easier to find.

## Next Actions

* Sam prepares the final design.
* Mia reviews the page copy.
* The launch date remains open.

Save the entry after reviewing it.

Choose a clear title

The title should explain what the entry contains.

Good examples include:

• Project Atlas — Decision Log;
• Customer Interview Notes — North Region;
• Weekly Support Review — 2026-W23;
• Research Findings — Local AI Models; or
• Daily Operations Briefing — 2026-06-08.

Avoid titles such as:

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

Clear titles make browsing and sorting more useful.

Add dates to recurring entries

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

For example:

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

Dated titles help you:

• distinguish one run from another;
• identify missing periods;
• compare changes;
• avoid duplicates; and
• find the correct result later.

Write with Markdown

Journal entries support Markdown.

You can use:

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

Use formatting to make the information easier to scan.

Do not add formatting that does not help the reader.

Use headings

Headings create a clear structure.

For example:

# Weekly Project Review

## Summary

## Completed Work

## Current Blockers

## Upcoming Deadlines

## Decisions Needed

Use one main heading for the entry and smaller headings for its sections.

Use bullet lists

Bullet lists work well for:

• findings;
• action items;
• risks;
• ideas;
• open questions; and
• short status updates.

For example:

## Action Items

* Sam prepares the final design files.
* Mia confirms the interview dates.
* Reza reviews the publication checklist.

Keep each bullet focused on one item.

Use numbered lists

Use numbered lists when order matters.

For example:

## Next Steps

1. Review the source material.
2. Confirm missing dates.
3. Prepare the final report.
4. Ask for approval.

Do not use numbers when the items can happen in any order.

Use tables

Tables are useful for structured details.

For example:

| Owner | Action | Deadline |
|---|---|---|
| Sam | Prepare design files | Friday |
| Mia | Confirm interviews | Not provided |

Keep tables small enough to read comfortably.

Use headings or lists when the content contains long explanations.

Use links carefully

Add a link when it helps the reader return to a source or related page.

Use descriptive link text.

Prefer:

[Feluda documentation](https://feluda.ai)

Instead of:

Click here

Review external links before saving an important entry.

Use code blocks

Code blocks can preserve commands, structured output, or examples.

For example:

```text
Input → LLM → Output
```

Use a language label when it improves readability.

Do not place private API keys, passwords, or access tokens in a Journal entry.

Save the entry

Save after writing or editing.

Before saving, check:

• the title;
• the date or reporting period;
• the heading structure;
• important names and numbers;
• links;
• action items;
• missing information; and
• whether sensitive details are necessary.

Reopen the entry after saving when the information is important.

Browse entries

Use the entry list to move between saved notes and results.

When browsing, look at:

• the title;
• the date;
• the source or project;
• the entry type; and
• whether it was written manually or created by a workflow.

Consistent titles make this process faster.

Sort entries by date

The Journal can sort entries by date.

Use newest first when you want to review recent activity.

Use oldest first when you want to follow a project, investigation, or recurring report from the beginning.

Sorting changes only the display order.

It does not edit the entries.

Review an entry

Open the entry and read the full content.

Check:

• whether the title matches the content;
• whether the date is correct;
• whether the source is clear;
• whether important information is complete;
• whether missing details are visible;
• whether claims are supported;
• whether follow-up actions are clear; and
• whether the information is still current.

AI-written entries should be compared with the original source when accuracy matters.

Edit a manual entry

Open the entry and use the available edit control.

Make the required changes.

Then save the updated version.

Useful edits may include:

• correcting a name or date;
• adding context;
• clarifying a decision;
• updating an action item;
• adding a source link;
• marking an item complete; or
• improving the Markdown structure.

Preserve important original meaning when the entry acts as a historical record.

Add a review note

When an AI-generated entry needs correction, add a visible review section.

For example:

## Human Review

* The deadline in the source is Friday, not Thursday.
* The final customer email still needs approval.
* The budget amount has not been confirmed.

This separates the original result from the later review.

Create a repeatable entry structure

Use the same structure for recurring entries.

For example:

# Weekly Support Review

## Summary

## Common Issues

## Unresolved Cases

## Escalations

## Recommended Actions

## Missing Information

A consistent structure makes reports easier to compare.

It also helps workflows produce predictable output.

Use the Journal with Workbench

Workbench can use a Journal tool when it is available and enabled.

A useful request is:

Use the Journal tool to create an entry titled
"Meeting Summary — 2026-06-08".

Include:
1. a summary;
2. decisions;
3. action items with owners and deadlines; and
4. unanswered questions.

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

Notes:
[Paste the meeting notes here.]

After the model responds:

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

Use the Journal with workflows

A workflow can save its result as a Journal entry.

For example:

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

This is useful when the result should remain available after the workflow run ends.

Test the Journal action manually before relying on it in regular work.

Use the Journal with scheduled workflows

A scheduled workflow can create recurring Journal entries.

For example, a weekly schedule may:

1. collect approved project information;
2. prepare a review;
3. write a dated Journal entry; and
4. return a completion result.

Review every recurring entry.

Automatic writing does not guarantee accurate content.

Confirm AI-written entries

After an AI model or workflow writes to the Journal, check:

• whether the entry exists;
• whether the title is correct;
• whether the date is correct;
• whether the full result was saved;
• whether important facts match the source;
• whether missing information is shown; and
• whether a duplicate was created.

A successful tool action confirms that something was written.

It does not confirm that the content is correct.

Use Journal Monitor

Journal Monitor watches a selected journal for new entries in real time.

Use it when:

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

Open Journal Monitor and select the journal you want to watch.

Keep the monitor open while the process is active.

Review a monitored entry

When a new entry appears:

1. confirm the title;
2. confirm the timestamp;
3. open the full entry;
4. compare it with the expected source;
5. review warnings or missing information;
6. check for duplicates; and
7. decide whether follow-up is needed.

The monitor shows that new content arrived.

It does not approve the content.

Monitor recurring reports

Journal Monitor can be useful for:

• daily briefings;
• weekly project reviews;
• research summaries;
• security monitoring;
• content reports; or
• long-running investigations.

Use clear dated titles so each new entry can be identified immediately.

Find missing entries

When an expected entry does not appear, check:

• whether the Workbench task or workflow ran;
• whether the Journal tool was enabled;
• whether the workflow reached the Journal step;
• whether the correct journal was selected;
• whether an error occurred;
• whether the entry used another title; and
• whether the run stopped earlier.

Review Workbench Activity, RunFlows output, or Schedule Manager history before repeating the action.

Avoid duplicate entries

Duplicate entries may appear when:

• the same workflow runs twice;
• a schedule overlaps;
• a timeout is retried;
• a manual and scheduled run use the same title;
• two workflows write to the same journal; or
• a delayed confirmation causes another attempt.

Before retrying:

• search or browse for the entry;
• compare timestamps;
• review workflow history;
• check active schedules; and
• confirm whether the first action completed.

Use unique titles

A recurring workflow should create distinguishable titles.

Use:

Daily Briefing — 2026-06-08

Rather than:

Daily Briefing

Include the relevant:

• date;
• week;
• month;
• project;
• customer;
• region; or
• reporting period.

Unique titles make duplicate detection easier.

Keep unrelated information separate

Do not place every note and report into one long entry.

Create separate entries when:

• the topic changes;
• the project changes;
• the reporting period changes;
• the source changes;
• a new decision is made; or
• the information needs a different reviewer.

Focused entries are easier to browse and reuse.

Keep one purpose per entry

A good entry should have one main purpose.

For example:

• meeting summary;
• decision log;
• project review;
• research findings;
• customer interview notes; or
• monitoring report.

When an entry becomes too broad, divide it into separate notes.

Record sources

Add source information when it matters.

You may include:

• a link;
• a filename;
• a document title;
• a meeting date;
• a workflow name;
• a report period; or
• another clear reference.

This makes later verification easier.

For example:

## Source

* Workflow: Prepare Weekly Project Review
* Reporting period: 1–7 June 2026
* Source file: project-status.md

Separate facts from suggestions

An AI-written entry may contain both source facts and recommendations.

Keep them separate.

For example:

## Confirmed Findings

[Facts from the source]

## Suggested Next Steps

[AI suggestions for review]

Do not present suggestions as confirmed decisions.

Mark missing information

Use a visible value such as:

Not provided

for missing details.

Avoid leaving an empty field when the reader may not know whether the value was forgotten or unavailable.

For example:

Owner	Action	Deadline
Mia	Confirm interviews	Not provided

Mark review status

When appropriate, add a status such as:

• Draft;
• Needs Review;
• Approved;
• Superseded; or
• Archived.

For example:

**Status:** Needs Review

Use a status only when someone understands what it means and who can change it.

Review old entries

Older Journal content may no longer reflect the current situation.

Review entries when:

• a project changes;
• a decision is replaced;
• a report is corrected;
• a source is updated;
• an action is completed; or
• a newer entry supersedes the old one.

Add a note that points to the newer entry when needed.

Preserve historical meaning

When the Journal acts as a record, avoid rewriting old entries in a way that hides what was originally known.

Instead, add:

## Update — 2026-06-08

The launch date was later confirmed as 20 June 2026.

This keeps the original context and the later correction visible.

Protect sensitive information

Before saving private information, check:

• whether it is necessary;
• whether personal details can be removed;
• which model processed it;
• whether a cloud provider received it;
• which tools were enabled;
• whether the correct Journal destination is selected; and
• who can access the computer and user account.

Do not save:

• API keys;
• passwords;
• access tokens;
• private connection values; or
• other credentials.

Use the intended Secrets or provider settings instead.

Use normal device security

Journal entries are stored with your local Feluda data.

Protect them with normal device practices, including:

• a secure user account;
• screen locking;
• operating-system updates;
• appropriate file access;
• encrypted storage where required; and
• secure backups.

Local storage does not make sensitive information automatically safe.

Back up important entries

Do not rely on one device as the only copy of information that must be kept.

Follow your normal personal or organisational backup process.

Important entries may also need to be copied into an approved long-term record system.

The Journal is a useful working space, but it may not replace formal record storage required by your organisation.

Review the Journal regularly

A regular review helps you:

• identify new workflow results;
• catch missing reports;
• find duplicate entries;
• compare recurring findings;
• close completed actions;
• update outdated notes; and
• decide what needs follow-up.

The value of the Journal comes from using the saved information, not only collecting it.

A practical Journal routine

Use this process:

1. Open Journal.
2. Sort entries for the task you are reviewing.
3. Select the relevant entry.
4. Confirm its title and date.
5. Review its source and content.
6. Correct or annotate important errors.
7. Check action items and missing information.
8. Confirm AI-written entries against the source.
9. Watch Journal Monitor when new entries are expected.
10. Check for missing or duplicate results.
11. Protect sensitive information.
12. Back up records that must be preserved.

The Journal gives you a clear place to keep and review useful Feluda output over time.