Skip to main content
These workflows fit Locality’s current file-based model.

​
Engineering wiki updates

Use Locality when the source material is already in Notion but the edit is easier with an agent. Example:
Why Locality helps:
  • the agent can inspect nearby docs with file search;
  • the user can review a concrete Markdown diff;
  • push updates the original Notion page after approval.

​
Meeting notes to action docs

Mount standups, planning notes, or meeting recaps. Ask an agent to turn them into follow-ups, status updates, or launch checklists. Good target files:
  • Standups with Locality/2026-07-02/page.md;
  • Product/Planning/Week 28/page.md;
  • Go To Market/Launch Notes/page.md.
Review with:

​
Content operations

Use Locality for edits that need consistency across many pages:
  • terminology cleanup;
  • launch messaging updates;
  • changelog drafts;
  • support article refreshes;
  • brand voice review;
  • product name corrections.
The agent can search the local workspace, make scoped edits, and leave pending changes for review.

​
Database-backed workflows

Notion databases appear as directories with row pages and _schema.yaml. Useful examples:
  • content calendar rows;
  • customer proof points;
  • bug triage notes;
  • user research repository;
  • CRM-style account notes.
Create a new row as a page:
Then review and push:

​
Portable knowledge bundles

Export mounted content into Open Knowledge Format when you want an offline, connector-neutral bundle.
Good uses:
  • share context with another agent;
  • archive a project workspace;
  • feed a retrieval or indexing pipeline;
  • demo Locality without giving direct Notion access.

​
Safe agent handoff

Give the agent one mounted path, one job, and one review rule.
That workflow keeps the remote app protected while still letting the agent do real work.