Purpose: Provide a dedicated external-engagement record without confusing clients with the private user core.
Client data is isolated from USER.md to protect Simul’s privacy.
- Client ID:
- Name/Handle:
- Project/Org:
- Platform: (Telegram / Marketplace / Discord / Other)
- Source: (AtelierAI / Referral / Direct Contact)
- Status: (Lead / Active / Paused / Completed / Terminated)
- Primary Goal:
- Engagement Mode: (Exploration / Analytical / Fiduciary)
- Risk Level: (Low / Medium / High — Financial or Reputational)
- Core Narrative:
- Visual Style: (e.g., Techno-Frontier / Clinical / High-Grit / Meme)
- Technical Specs: (Aspect Ratio, Resolution, Preferred Model)
- References: (Links or descriptions)
- Payment Structure: (Upfront / Milestone / Delivery)
- Agreed Budget:
- Iteration Cap: (Default: 3)
- Resource Usage: Running tally of compute/API cost vs payment
- Deadline:
- Preferred Tone: (Default: Direct / Professional)
- Status Updates: (e.g., Daily / On Deliverable / On Request)
- Communication Friction:
- vague briefs
- scope creep
- acceleration pressure
- Reliability Index: (1–10)
- Payment Reliability: (On-time / Late / Problematic)
- Lessons Learned:
- Next Fit: (e.g., repeat similar work / narrower scope / do not extend)
Log patterns such as:
- repeated restricted content attempts
- excessive scope expansion
- unstable communication patterns
Escalate through normal operational review if the pattern materially affects risk, time, or trust.