Agent workflows

​

Agent contract

Use Locality for this workspace.
Edit the mounted Markdown files directly.
Before pushing, show me `loc diff` for the file you changed.

Update the launch plan at:
~/Library/CloudStorage/Locality/notion-main/go-to-market/launch-plan/page.md

​

What agents should do

• read mounted files with normal file tools;
• edit page.md directly;
• preserve Locality frontmatter and ::loc{...} directives;
• use loc status <path> when they need state;
• use loc diff <path> before remote writes;
• push only when the user asks, or when Live Mode reports a review path;
• if the user asks them to sync back to Notion, update Notion, publish, or apply edits remotely, run loc diff <path> and then loc push <path> -y for safe plans.

​

What agents should avoid

• do not rewrite generated loc: identity frontmatter;
• do not edit _schema.yaml unless the task is explicitly about database schema;
• do not remove ::loc{...} directives unless replacing the underlying unsupported block intentionally;
• do not run broad loc push commands without a scoped path;
• do not delete old-looking folders until loc status confirms they are untracked and safe to remove.

​

Live Mode behavior

• the desktop app reports attention needed;
• the file is conflicted;
• the user asks for a push;
• the agent needs to explain what is pending.

​

Good agent prompt

Use Locality to edit my Notion workspace.

Target file:
~/Library/CloudStorage/Locality/notion-main/engineering-wiki/launch-checklist/page.md

Make the requested Markdown edits directly in that file. Preserve existing
frontmatter, block identity directives, and database schema files. When done,
run `loc diff` for the target file and summarize the planned remote changes.
Do not push unless I explicitly approve it.

​

MCP fallback

{"argv":["status","~/Library/CloudStorage/Locality/notion-main","--json"]}

​

Installed guidance