sync: auto-sync from GURU-BEAST-ROG at 2026-06-02 10:44:23
Author: Mike Swanson Machine: GURU-BEAST-ROG Timestamp: 2026-06-02 10:44:23
This commit is contained in:
@@ -48,6 +48,7 @@
|
||||
- [Paste-safe command formatting (Howard)](feedback_command_formatting.md) — Two clauses, one root cause: (a) multi-line scripts not semicolon one-liners (wrap breaks paste), (b) all code at column 0 inside fences (indentation breaks PowerShell paste).
|
||||
- [Autonomous infra/build setup](feedback_autonomous_infra_setup.md) — During infra/build/CI/dev setup, just install prerequisites and push through routine steps; reserve check-ins for genuine decisions (forks, destructive/outward, client/prod).
|
||||
- [Check patterns before asking](feedback_check_patterns_before_asking.md) — Before asking how to do something repeat-style (sync, save, sweep, billing), study existing artifacts and workflow docs first; reach for similar past artifacts as the template.
|
||||
- [Pricing verification — no guessing](policy_pricing_verification.md) — ANY cost presented to the team or a client MUST be verified via live web lookup (WebFetch/WebSearch, fallback to headless Chrome). Never estimate from training data. Cite source + date inline. If unreachable, say so — do NOT substitute a guess.
|
||||
- [Client communication tone](feedback_client_tone.md) — How to write client-facing Syncro comments — expert partner, not intake questionnaire.
|
||||
- [Add Mike as owner on all Entra apps](feedback_entra_app_owner.md) — Apps created via management SP have no user owner — must add Mike manually or publisher verification fails.
|
||||
- [No TOML/config file approach for endpoints](feedback_no_toml_config_endpoints.md) — User explicitly prohibits TOML or config-file-based endpoint configuration — this will never be approved.
|
||||
|
||||
30
.claude/memory/policy_pricing_verification.md
Normal file
30
.claude/memory/policy_pricing_verification.md
Normal file
@@ -0,0 +1,30 @@
|
||||
# Policy: Pricing Verification — No Guessing
|
||||
|
||||
**Set by:** Mike Swanson, 2026-06-02
|
||||
|
||||
Any time a cost or price is presented to the team or a client, it MUST be verified via a
|
||||
live web lookup before being stated. Never use training-data recollections or estimates.
|
||||
|
||||
## Rules
|
||||
|
||||
- Hardware, parts, software licensing, SaaS pricing, labor rates — all require real-time verification.
|
||||
- Use WebFetch / WebSearch first. Fall back to headless Chrome (`web-fetch-chrome.py`) if bot-blocked.
|
||||
- Always cite source and date inline: `[$X.XX — Amazon, 2026-06-02]`
|
||||
- If no pricing source is reachable, state that explicitly. Do NOT substitute a guess or a range
|
||||
"from memory."
|
||||
- Applies in all contexts: Discord bot, main session, any Claude session in this repo.
|
||||
|
||||
## Scope
|
||||
|
||||
Applies to ALL estimate types:
|
||||
- Computer hardware (drives, RAM, CPUs, etc.)
|
||||
- Replacement parts and peripherals
|
||||
- Software licensing and subscriptions
|
||||
- Third-party service quotes
|
||||
- Repair labor estimates (when citing market rates)
|
||||
|
||||
## Why
|
||||
|
||||
Hardware prices fluctuate significantly. A "budget" vs "mid-range" vs "quality" drive can
|
||||
vary by 2-3x depending on current market. Presenting stale or fabricated numbers to clients
|
||||
damages trust and can result in inaccurate quotes.
|
||||
Reference in New Issue
Block a user