Commit pre-revisao de simplificação e elegancia do superpowers

references/initial-context-catalog.md

@@ -22,6 +22,8 @@ Use this file for org and business-context interpretation. Skip it for routine c
 ## Hierarchy Shortcuts
 
 - For SA Attach productivity-style asks, the working source of truth is usually `Knowledge DV - Hours - V2`.
+- For any hours/effort rollup, the default metric is 100% of recorded hours: include customer-related work, non-customer/internal work, and Time Off. Exclude any of those categories only when the user explicitly asks for that exclusion or subset.
+- In `DV - SE Team`, use `"Effort"."# Hours"` for default hour totals. Use `"Effort"."# Hours (Excl. Time Off)"` only for explicit excluding-Time-Off asks or when a fixed built-in view forces that measure, and disclose that limitation.
 - In that dataset, the most useful working assumption is:
   - `SE Team Level 3 Email Address` -> manager scope anchor for many manager-rollup asks.
   - `SE Team Level 4 Email Address` -> direct manager under the level-3 manager.
@@ -63,12 +65,16 @@ Keep this section intentionally small. Only verified hierarchy anchors that mate
 | `Quais clientes compoem o total do arquiteto` | Reuse the same de-duplicated architect or opportunity set and pull `Customer Name`, `Opportunity Value`, and `Workload Amount` from `Knowledge DV - Opportunities - V2`. |
 | `Preciso descobrir qual nível representa o manager` | Probe `SE Team Level 1..8 Email Address` with a `%surname%` or exact-email search in `Knowledge DV - Hours - V2` before building the final query. |
 | `Quero deals WON do time do manager` | Prefer `Knowledge DV - Opportunities - V2` for `Close Date`, `Status`, `Opportunity Value`, `Workload Amount`, territory, and owner context; prefer `Knowledge DV - Hours - V2` for hierarchy ownership and allocated hours. |
+| `Horas/atividades sem cliente`, `não relacionadas a oportunidades`, `atividades internas` | This is an explicit subset request. In `DV - SE Team` effort reads, classify as no-customer only when SR Number, Customer Name, and Opportunity ID are all `Unspecified`; any populated SR/customer/opportunity means customer-related. |
 
 ## Practical Rules
 
 - Prefer `--query` for ad hoc joins, filters, and groupings when it can express the ask cleanly.
 - Prefer `--sql` only when you need a dataset the normal `Security Entry Point` filter cannot express or when you must query XSA hierarchy columns directly.
 - Do not trust `Won Flag` from the hours dataset as the only `WON` filter for business reporting. Use `Knowledge DV - Opportunities - V2` `Opportunity Status = 'Won'` plus the required close-date window.
+- For effort/hour analysis, do not apply customer-linkage filters by default. When the user explicitly requests customer vs. non-customer classification, `Unspecified` is the workbook's absence marker; do not test only for SQL `NULL` when determining whether an effort row lacks customer linkage.
+- Validated FY26 my-team no-customer task types: `Administration`, `Content Creation`, `Partner Activities`, `Sales Planning`, `Training Delivery`, and `Training/Personal Development - Taken`. Treat this as a validated pattern, not the primary rule; the primary rule is the three-field `Unspecified` linkage signal.
+- Customer-related FY26 my-team task types observed: `Config`, `Preparation`, and `Travel`; `Delivery` and `Follow-up` were mostly customer-related and had small cases with SR/customer but no opportunity ID, so keep them customer-related unless all three linkage fields are `Unspecified`.
 - Use `Knowledge DV - Opportunities - V2` and the other Knowledge DV views for org-wide reads whose hierarchy starts at Latin America leadership.
 - Use `DV - SE Team` only for self-scoped questions where "my team" really means the executing user and the people below that user, plus the normal SR and session-context questions.
 - Do not use `DV - SE Team` as generic fallback for manager, territory, owner, or org-wide commercial reads.