Skip to content

Replace hardcoded "Ryan"/"R2" with placeholders in location-awareness.md #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
joshphoenix1 wants to merge 1 commit into
base: main
Choose a base branch
from
+7 −7
Open

Replace hardcoded "Ryan"/"R2" with placeholders in location-awareness.md #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 7 additions & 7 deletions clawchief/location-awareness.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Status: v1
Created: 2026-04-06
Purpose: make clawchief location-aware so Ryan's task list, reminders, and appointment triage reflect where he physically is and whether a task is actually doable from that place.
Purpose: make clawchief location-aware so {{OWNER_NAME}}'s task list, reminders, and appointment triage reflect where they physically are and whether a task is actually doable from that place.

## Ownership boundary

Expand All @@ -19,15 +19,15 @@ This file does not own:

## Core principle

Do not present a task as actionable if Ryan cannot physically do it from his current location.
Do not present a task as actionable if {{OWNER_NAME}} cannot physically do it from their current location.

Location is part of task context, not a nice-to-have.
A good daily plan should distinguish between:
- can do anywhere
- can do while traveling
- requires being at the principal's home base
- requires being at a specific appointment location
- can be delegated by R2
- can be delegated to {{ASSISTANT_NAME}}

## Current known anchor

Expand All @@ -36,11 +36,11 @@ A good daily plan should distinguish between:

## Operating rules

1. When Ryan is traveling, suppress or reframe home-only tasks as blocked, delegated, or rescheduled instead of showing them as normal active tasks.
1. When {{OWNER_NAME}} is traveling, suppress or reframe home-only tasks as blocked, delegated, or rescheduled instead of showing them as normal active tasks.
2. When a task clearly depends on a place, add the location constraint into the task text.
3. When an appointment or meeting is time-bound and location-bound, preserve both in the task text when known.
4. If Ryan's travel status creates a conflict with an existing task, update the Todoist task in the same turn.
5. If a task is still important but cannot be done from Ryan's current location, choose one of these states:
4. If {{OWNER_NAME}}'s travel status creates a conflict with an existing task, update the Todoist task in the same turn.
5. If a task is still important but cannot be done from {{OWNER_NAME}}'s current location, choose one of these states:
- blocked while traveling
- delegate to someone else
- reschedule to the next plausible date/location window
Expand All @@ -54,7 +54,7 @@ A good daily plan should distinguish between:
- Todoist task wording, section, due date, and labels should reflect location constraints when relevant.
- `clawchief/priority-map.md` already treats travel and schedule integrity as priority context.
- `daily-task-prep` should use this rule when curating Todoist `Today`.
- Heartbeat check-ins should avoid nudging Ryan about tasks he cannot physically do from where he is.
- Heartbeat check-ins should avoid nudging {{OWNER_NAME}} about tasks they cannot physically do from where they are.
- The executive-assistant workflow should use this rule before offering times or treating travel windows as available.

## Examples
Expand Down