system-prompts-and-models-o.../salesflow-saas/docs/customer_learnings/friction_log.md
Claude 3ef62652aa
Phase 2 Execution Waves: 90-day plan + Verification Protocol scaffolding
Saves the DEALIX_PHASE2_EXECUTION_WAVES.md 90-day plan and scaffolds every
artifact the coding agent can produce. Wave A-E execution is explicitly
blocked until the Week-12 Phase Gate (§3) returns Green.

Added:
  §1 Verification Protocol (V001-V007)
    - scripts/v001_secret_scan.sh — trufflehog + gitleaks full-history scan
    - backend/tests/security/test_rls_fuzz.py — 10K cross-tenant fuzz
    - docs/verification/V003_pentest_engagement.md — vendor RFP + scope
    - docs/verification/V004_no_founder_demo_test.md — 3-tester protocol
    - scripts/v005_truth_registry_audit.py — independent audit tool
    - infra/load-tests/baseline.js — k6 perf baseline
    - frontend/tests/a11y/baseline.spec.ts — Playwright+axe baseline
    - docs/baselines/README.md + docs/verification/README.md

  §2 Founder Decision Sprint (FD001-FD005)
    - docs/internal/legal_entity_decision.md — MISA/DIFC/Delaware brief
    - docs/internal/trademark_status.md — SAIP filing kit tracker
    - docs/hiring/{design_engineer, backend_engineer, head_of_cs}.md

  §3 Customer Validation (CV001-CV004)
    - docs/customer_learnings/pilot_agreement_template.md
    - docs/customer_learnings/pilot_template/success_criteria.md
    - docs/customer_learnings/pilot_template/kickoff_checklist.md
    - docs/customer_learnings/friction_log.md + feature_requests.yaml
    - docs/customer_learnings/weekly_review_template.md

  Truth registry updates
    - docs/registry/TRUTH.yaml — new verification_protocol,
      founder_decision_sprint, customer_validation sections

Gates (post-change):
  architecture_brief.py     40/40
  release_readiness_matrix  94/94 (added 30 new scaffold checks)
  v005_truth_registry_audit 19/19 SUPPORTED
2026-04-17 11:13:27 +00:00

1.7 KiB
Raw Blame History

Customer Friction Log

One entry per friction. No aggregation, no editorializing. Raw source of truth. Head of CS owns; Founder reads weekly on Wednesday. Rule: entry written within 24h of the conversation. No exceptions.


Entry Template (copy for each new entry)

### YYYY-MM-DD — [customer_short_name] — [short_title]

- **Reporter**: [dealix_team_member]
- **Customer role**: [CFO / COO / Sales Ops / Admin / End user]
- **Severity**: [P0 show-stopper | P1 major | P2 annoyance | P3 nice-to-have]
- **Theme tag**: [auth | arabic | approval | evidence | reporting | integration | perf | a11y | other]
- **Context** (12 sentences describing what customer was trying to do):

- **What they said** (direct quote when possible, Arabic OK):
  >

- **What actually happened** (observed behavior, steps to reproduce):

- **Workaround used (if any)**:

- **Linked GitHub issue / ticket**: #____

- **Status**: [open | in-progress | resolved | won't-fix-with-rationale]

Entries

[Seed — example of the format; delete on first real entry]

2026-04-17 — Example Retail Group — Approval Card Arabic RTL label truncation

  • Reporter: Head of CS
  • Customer role: CFO
  • Severity: P2 annoyance
  • Theme tag: arabic, a11y
  • Context: CFO trying to approve a deal from mobile Safari in Arabic locale.
  • What they said:

    "الزر الأخضر يخفي نصف السطر العلوي. ما أقدر أقرأ اسم الصفقة."

  • What actually happened: Approve button overlaps deal title in RTL at viewport <375px.
  • Workaround used: Customer approved from desktop instead.
  • Linked GitHub issue / ticket: #TBD
  • Status: open (queued for Wave A)