Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,11 @@ The backend (`fastapi_backend`) and the frontend (`nextjs-frontend`) are version
one stops the old address at once, and the feed asks directories and search engines not to list it. Editors make and
fill feeds with `POST /api/v1/feeds` and `POST /api/v1/feeds/{id}/items`; agents use the MCP tools `list_feeds`,
`create_feed` and `publish_to_feed` ([Published feeds](docs/feeds.md)).
- Routines fill them: the graph workflow nodes Select assets and Select activities pick what came in since the
routine last ran, Publish to feed adds it to a feed, and Podcast episode makes an episode about it (added to a
feed, listed once it's made). Try on the canvas says what they would do
([Publishing from the graph](docs/processing.md#publishing-from-the-graph)).

## 0.14.0 <small>October 17, 2026</small> {id="0.14.0"}

- **Dates read as days, for agents.** With Settings → Analysis → Read dates on (off by default), analysis reads the
Expand Down
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -141,7 +141,8 @@ listed under [In progress](#in-progress), and what comes next under [Planned](#p
templates to start from, a search by their words, a download as Markdown, and Undo and Recently deleted instead of a
confirm. Export an asset or a collection as an evidence PDF with everything Lens found about it, or the parts you
pick. Publish a namespace's resources, episodes, timeline activities or text as a private RSS feed or a podcast
feed that any feed reader or podcast app follows. ([Podcasts](docs/podcasts.md),
feed that any feed reader or podcast app follows, and let a routine fill it on a schedule with what's new, or make
an episode about the week's new resources. ([Podcasts](docs/podcasts.md),
[specs from transcripts](docs/notes.md#specs-from-transcripts), [notes](docs/notes.md),
[evidence PDFs](docs/api.md#evidence-pdfs), [published feeds](docs/feeds.md);
[checks](docs/requirements.md#learn-from-it))
Expand Down
11 changes: 9 additions & 2 deletions docs/feeds.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Published feeds (RSS and podcasts)

**Status: in progress.** Feeds, their private addresses, the API and the MCP tools are built. Routine workflow nodes
that pick part of the graph or the timeline and publish it, and the Feeds page in the web app, come next.
**Status: in progress.** Feeds, their private addresses, the API, the MCP tools and the workflow nodes that let a
routine fill a feed or make an episode on a schedule are built. The Feeds page in the web app comes next.

A namespace can publish what's in it as a feed that any feed reader or podcast app follows: new resources, podcast
episodes, things on the timeline, or text a person or an agent wrote. Each feed has a private address; add it to the
Expand Down Expand Up @@ -48,6 +48,13 @@ again adds only what's new. A feed lists its newest items (50 by default, up to
Feed readers poll; the feed answers `304 Not Modified` when nothing changed (its `ETag`), and notes when a reader
last read it (`fetched_at`, at most once a minute), so the web app can show that a podcast app is subscribed.

## From a routine

A routine fills a feed on a schedule with a graph workflow ([Publishing from the graph](processing.md#publishing-from-the-graph)):
**Select assets** or **Select activities** picks what's new since the routine last ran, in the namespaces it covers,
and **Publish to feed** adds it, or **Podcast episode** makes an episode about it and adds that. Each run adds only
what's new, and what the feed's readers couldn't read is refused.

## API and MCP

| | |
Expand Down
4 changes: 4 additions & 0 deletions docs/podcasts.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,10 @@ The audio is the asset's (`GET /api/v1/recordings/{id}/audio`), and so are shari
use the MCP tools `create_podcast` (resources as `recording_ids`, lines as `"<recording_id>:<line>"`) and
`get_podcast` ([MCP](mcp.md)).

A routine makes episodes on a schedule with the **Podcast episode** workflow node
([Publishing from the graph](processing.md#publishing-from-the-graph)): an episode about the week's new resources,
added to a [feed](feeds.md) your podcast app follows.

## The prompts are templates

The plan, write and fact-check prompts are prompt templates (Templates in the web app) called **Podcast: plan**,
Expand Down
28 changes: 28 additions & 0 deletions docs/processing.md
Original file line number Diff line number Diff line change
Expand Up @@ -756,3 +756,31 @@ Every change is recorded (`GET /api/v1/graph-changes`): editors of the namespace
proposals (dismissing says the two are different, so the pair isn't suggested again) and undo applied changes; an
admin can undo everything a run applied at once (`POST /api/v1/routine-runs/{id}/undo`). Merges are undone exactly as
from an entity's page.

### Publishing from the graph

Graph workflows also publish, so a routine fills a [feed](feeds.md) or makes a [podcast episode](podcasts.md) on a
schedule. Their nodes:

- **Select assets** passes on the resources in the routine's namespaces (or the *namespaces* named), newest first,
*limit* at most (50, up to 500): those that came in *since* the routine's last run (the default; on its first run,
the past week), or in the past *day*, *week* or *month*, or *all* of them; matching *q* (words in the title),
*topics*, *entities* and *status*. Podcast episodes are left out unless *include episodes* is on, so an episode about
the week's resources isn't a source for the next one.
- **Select activities** passes on the [timeline](timeline.md)'s activities in those namespaces, of the *kinds* named
(with their descendants), *since* the same choices, matching *q* and a *where* match tree, newest first, *limit* at
most (50, up to 200). Only what everyone who reads the namespace sees, never someone's own.
- **Publish to feed** adds what comes in to the *feed*: resources and episodes, activities, or text (a template
node's output becomes a text item, with the node's *title*). What's in the feed already isn't added again, so a
routine that runs again adds only what's new; what the feed's readers couldn't read is refused and said in the run's
log. The feed's namespace is one the routine covers.
- **Podcast episode** makes an episode about the resources that come in (*max sources*, 10, of those with text; none
under *min sources*), with the *title*, *prompt*, *length* and *style* of [Podcasts](podcasts.md), placed in the
*namespace* named, else the *feed*'s, else where an admin's episode goes; a source its readers couldn't read is left
out. With a *feed*, the episode is added to it and listed once it's made.

A run's result counts what was `published` and the `episodes` made, and its log says what each node did. Try on the
canvas runs a graph workflow over the namespaces you pick and says what each node would do, without publishing. So
Select assets → Podcast episode (feed *Weekly*, length 10) on a routine that runs every Monday makes an episode about
the week's new resources and puts it in your podcast app; Select activities (kinds `asset.added`) → Publish to feed
puts the timeline in your feed reader.
1 change: 1 addition & 0 deletions docs/requirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -169,6 +169,7 @@ request, to another check that proves the same thing; loosening a requirement or
| A note shows the notes it's inside and the notes inside it, to people and agents | [test_notebook.py](https://github.com/adeelahmad/lense/blob/main/fastapi_backend/tests/api/test_notebook.py) `test_path_and_children`, `test_assistant_keeps_notes`; [test_mcp.py](https://github.com/adeelahmad/lense/blob/main/fastapi_backend/tests/api/test_mcp.py) `test_note_tools`; [note-page.test.tsx](https://github.com/adeelahmad/lense/blob/main/nextjs-frontend/__tests__/note-page.test.tsx) |
| Undo and Recently deleted instead of a confirm | [test_notebook.py](https://github.com/adeelahmad/lense/blob/main/fastapi_backend/tests/api/test_notebook.py) `test_recently_deleted`; [notes-delete.test.tsx](https://github.com/adeelahmad/lense/blob/main/nextjs-frontend/__tests__/notes-delete.test.tsx) |
| A namespace publishes a private RSS feed or a podcast feed (Apple Podcasts' tags, audio with byte ranges) of resources, episodes, timeline activities and text, holding only what its readers can already read; through the API and MCP | [test_feeds.py](https://github.com/adeelahmad/lense/blob/main/fastapi_backend/tests/api/test_feeds.py) `test_making_filling_and_reading_a_feed`, `test_a_podcast_feed_lists_what_has_audio`, `test_timeline_activities_in_a_feed`, `test_vaults_and_settings`, `test_agents_use_feeds` |
| A routine fills a feed on a schedule, or makes a podcast episode about what's new: graph workflow nodes pick the resources or timeline activities since the last run, add them to a feed, or make an episode about them; Try says what they would do | [test_feed_nodes.py](https://github.com/adeelahmad/lense/blob/main/fastapi_backend/tests/api/test_feed_nodes.py) `test_a_routine_publishes_new_resources_to_a_feed`, `test_a_routine_publishes_the_timeline_and_text`, `test_a_routine_makes_an_episode_and_the_feed_lists_it_once_made`, `test_try_says_what_it_would_do_and_bad_settings_are_refused` |
| An asset or a collection exported as an evidence PDF, whole or the parts you pick | [test_evidence.py](https://github.com/adeelahmad/lense/blob/main/fastapi_backend/tests/api/test_evidence.py) `test_a_collection_as_one_evidence_pdf`, `test_everything_lens_found_goes_in`, `test_picking_the_parts`; [evidence-parts.test.tsx](https://github.com/adeelahmad/lense/blob/main/nextjs-frontend/__tests__/evidence-parts.test.tsx) |

## Automate it
Expand Down
Loading
Loading