added

skills/PID-update-maintenance-skill.md

@@ -18,7 +18,7 @@ The agent should look for meaningful change across user-approved sources, draft
 This skill guarantees:
 
 - It will ask for the user's current PID location and format before attempting updates.
-- It will ask which data sources the user authorizes for review.
+- It will ask the user to explicitly list every data source location, account, connector, export, folder, repository, and cloud document set authorized for review; the PID repo or PID file location is never assumed to be the activity source unless the user says so.
 - It will respect the requested timeframe, defaulting to the last 7 days when no timeframe is provided.
 - It will create a local Markdown draft before changing the PID.
 - It will organize findings according to the user's actual PID structure when readable, falling back to the standard PID template sections when needed.
@@ -124,9 +124,12 @@ At the beginning, ask the user to provide or confirm the following. Keep the int
 - Preferred draft filename:
 
 ## Approved Data Sources
-- Local project folders:
+List every authorized source explicitly. Do not assume the PID repo, the folder containing the PID, the current workspace, or recently modified nearby files are approved activity sources unless the user names them. Ask for exact local paths, cloud locations, connector scopes, account labels, export files, repositories, or date-bounded queries for each source category.
+
+- Local PC folders and exact paths:
 - Notes folders:
 - Documents folders:
+- Cloud file locations or connectors (Google Drive, OneDrive, Dropbox, iCloud, SharePoint, etc.):
 - Downloads or exports:
 - Git repositories, including histories:
 - Email accounts or labels:
@@ -262,11 +265,11 @@ Prefer concrete, grounded language over generic praise.
 
 1. Ask for the current PID path/link and format.
 2. Ask for the timeframe. Use the last 7 days if the user says weekly or gives no range.
-3. Ask which source categories are approved and where to find them.
+3. Ask the user to list every approved source location and access method, including local PC paths, cloud folders/connectors, email accounts or labels, calendars, meeting transcript folders, chat exports, repositories, databases, spreadsheets, and publishing/content systems. Do not infer sources from the PID path, current repo, cwd, or neighboring folders.
 4. Ask for privacy boundaries.
 5. Ask where to save the local review draft.
 
-Stop if the user has not authorized any source review.
+Stop if the user has not authorized at least one explicit source location, connector scope, account label, export file, repository, or bounded query to review.
 
 ### Phase 2: Read The Current PID
 
@@ -282,10 +285,10 @@ Completion criteria:
 
 ### Phase 3: Source Inventory
 
-1. List each approved source.
+1. List each explicit approved source, including path/account/connector/query, source category, date range, and scan limits.
 2. Record access method, date range, and scan limits.
 3. Prefer metadata and targeted searches before reading large corpora.
-4. Do not read sources outside the user's approved categories.
+4. Do not read sources outside the user's explicitly listed locations, connectors, accounts, repositories, exports, or bounded queries, even if they are near the PID file or appear recently modified.
 5. Track unreadable or skipped sources in the run receipt.
 
 Completion criteria:
@@ -465,7 +468,7 @@ Use validation tiers so the agent does not confuse a quick structural check with
 
 Run every time:
 
-- intake captured PID location, timeframe, approved sources, and privacy boundaries
+- intake captured PID location, timeframe, privacy boundaries, and at least one explicit approved source location/account/connector/export/repository/query; PID folder/source assumptions are not acceptable
 - review draft exists before any PID update
 - every proposed update has a PID section placement
 - every fact has evidence
@@ -803,13 +806,18 @@ My PID is here: [path or link]
 Review this timeframe: [last 7 days / dates]
 Save the review draft here: [folder]
 
-Approved sources:
-- [folders]
-- [email labels or accounts]
-- [calendar range]
-- [meeting transcript folders]
-- [CSV/JSON/database exports]
-- [other sources]
+Approved sources, with exact locations or access scopes:
+- Local PC folders: [full paths]
+- Cloud files/folders/connectors: [Google Drive/OneDrive/Dropbox/etc. paths, links, or connector scopes]
+- Email accounts or labels: [account + labels/queries]
+- Calendar range/account: [calendar + date range]
+- Meeting transcript folders or recording exports: [full paths or links]
+- Git repositories, including histories: [full paths or remotes]
+- CSV/JSON/database/spreadsheet exports: [full paths or links]
+- Publishing/content/social/newsletter sources: [paths, exports, or accounts]
+- Other sources: [exact source and access method]
+
+Do not assume the PID repo or the folder containing my PID is an approved source unless I list it above.
 
 Privacy boundaries:
 - never include [items]
@@ -822,3 +830,4 @@ First create a local Markdown review draft organized by my PID sections. Do not
 ## One-Sentence Version
 
 Scan user-approved recent activity, extract grounded identity signals, draft them into the user's PID structure for human review, then append approved updates so the PID stays fresh, specific, and useful for AI-native matching.
+