whiteport-design-studio 0.1.0

package/src/workflows/1-project-brief/alignment-signoff/contract.template.md

@@ -0,0 +1,297 @@
+# Project Contract
+
+**Project**: {{project_name}}  
+**Date**: {{date}}  
+**Client**: {{client_name}}  
+**Contractor**: {{contractor_name}}  
+**Contract Language**: {{contract_language}}  
+**Governing Law/Jurisdiction**: {{governing_jurisdiction}}
+
+---
+
+> **Contract Philosophy**: This contract is designed to be simple, fair, and clear - providing reliable terms that support a long-lasting working relationship between both parties.
+
+---
+
+## 1. Project Overview
+
+### The Realization
+
+{{realization}}
+
+### Recommended Solution
+
+{{recommended_solution}}
+
+---
+
+## 2. Business Model
+
+**Selected Model**: {{business_model}}
+
+{{business_model_description}}
+
+{{business_model_terms}}
+
+---
+
+## 3. Scope of Work
+
+### The Path Forward
+
+{{path_forward}}
+
+### Deliverables
+
+Based on the path forward, the following deliverables will be provided:
+
+{{deliverables_list}}
+
+### In Scope
+
+The following work is explicitly included in this contract:
+
+{{in_scope}}
+
+### Out of Scope
+
+The following work is explicitly NOT included in this contract:
+
+{{out_of_scope}}
+
+**Note**: Any work outside the scope defined above requires a written Change Order (see Section 10: Not to Exceed Clause).
+
+---
+
+## 4. Our Commitment
+
+{{our_commitment}}
+
+---
+
+### Payment Terms
+
+**Total Contract Amount**: {{total_amount}}
+
+**Payment Structure**: {{payment_structure}}
+
+**Payment Schedule**:
+{{payment_schedule}}
+
+**Background**: Clear payment terms protect both parties and ensure fair compensation.
+
+**What it does**: Defines when and how payments will be made.
+
+**Purpose**: 
+- Ensures supplier receives fair compensation for work
+- Provides client with clear payment expectations
+- Protects both parties from payment disputes
+- For fixed-price contracts, upfront payment is fair since supplier assumes cost overrun risk
+
+**Payment Terms Details**:
+- **Payment Method**: {{payment_method}} (check, wire transfer, credit card, etc.)
+- **Payment Due Dates**: {{payment_due_dates}}
+- **Late Payment**: {{late_payment_terms}} (e.g., interest charges, work suspension)
+- **Payment Conditions**: {{payment_conditions}} (e.g., payment required before work begins, payment tied to deliverables)
+
+**For Fixed-Price Contracts**: 
+This is a fixed-price contract, meaning the contractor commits to deliver specified work for the agreed price, regardless of actual costs. Since the contractor assumes the risk of cost overruns, upfront payment (50-100%) is standard and fair. This demonstrates client commitment and enables the contractor to deliver quality work without cash flow concerns.
+
+---
+
+## 5. Timeline
+
+{{timeline}}
+
+*Note: Timeline is based on the work plan outlined above and may be adjusted based on project requirements.*
+
+---
+
+## 6. Why It Matters
+
+{{why_it_matters}}
+
+---
+
+## 7. Expected Outcomes
+
+### The Value We'll Create
+
+{{value_we_create}}
+
+---
+
+## 8. Risks and Considerations
+
+### Cost of Inaction
+
+{{cost_of_inaction}}
+
+---
+
+## 9. Confidentiality
+
+### Confidentiality Clause
+
+**Background**: This clause protects sensitive information shared during the project.
+
+**What it does**: Both parties agree to keep project information confidential.
+
+**Purpose**: Protects proprietary information, business strategies, trade secrets, and sensitive data.
+
+**Terms**:
+
+Both parties agree to:
+
+- Keep all project-related information confidential
+- Not disclose project details to third parties without written consent
+- Use confidential information solely for project purposes
+- Return or destroy confidential materials upon project completion or termination
+- Maintain confidentiality obligations even after project completion
+
+**Exceptions**:
+- Information already publicly known
+- Information independently developed
+- Information required by law to be disclosed
+
+**Duration**: Confidentiality obligations shall remain in effect for [X] years after project completion.
+
+---
+
+## 10. Not to Exceed Clause
+
+### Budget Cap
+
+**Background**: This clause sets a maximum budget limit.
+
+**What it does**: States that total costs will not exceed a specified amount without prior written approval.
+
+**Purpose**: 
+- Protects both parties from unexpected cost overruns
+- Ensures budget control
+- **Prevents scope creep** - Any work beyond the original scope requires approval and may affect the budget cap
+
+**Terms**:
+
+- Total project costs shall not exceed **{{not_to_exceed_amount}}** without prior written approval from {{client_name}}
+- Any work that would exceed this amount must be approved in advance
+- If additional work is needed, a change order must be signed before proceeding
+- This cap includes all fees, expenses, and costs related to the project
+
+**Change Orders and Scope Control**:
+- Any changes to scope that affect cost must be documented in a written change order
+- Change orders must be signed by both parties before work begins
+- Change orders may adjust the not-to-exceed amount if agreed upon
+- **Scope creep prevention**: Work outside the original scope (as defined in Section 2) requires a change order and approval before proceeding
+- This clause helps prevent gradual expansion of project scope without proper authorization
+
+---
+
+## 11. Terms and Conditions
+
+### Work Initiation
+
+**When work begins**: {{work_initiation_date_or_condition}}
+
+**Background**: This clause specifies exactly when the contractor is authorized to begin work.
+
+**What it does**: Defines the start date or conditions that must be met before work begins.
+
+**Purpose**: 
+- Prevents unauthorized work before contract is fully executed
+- Establishes clear timeline expectations
+- Protects both parties by ensuring work only begins after proper authorization
+
+**Initiation conditions** (select applicable):
+- Upon full execution of this contract (signatures from both parties)
+- On a specific date: {{specific_start_date}}
+- Upon receipt of initial payment/deposit
+- Upon written notice from {{client_name}}
+- Other: {{custom_initiation_condition}}
+
+### Project Initiation
+
+This project is initiated upon approval of the project pitch. Project initiation is considered complete upon stakeholder approval.
+
+### Next Steps
+
+After contract approval:
+1. Proceed to full Project Brief development
+2. Execute work plan as outlined above
+3. Deliverables will be provided according to the agreed timeline
+
+### Changes and Modifications
+
+Any changes to scope, timeline, or investment must be agreed upon in writing by all parties.
+
+### Intellectual Property
+
+**Philosophy**: Clear IP ownership prevents future disputes and protects both parties' interests.
+
+All deliverables and work products created under this contract will be owned by {{client_name}} upon full payment, unless otherwise specified in writing. This ensures clarity and prevents misunderstandings about ownership rights.
+
+### Termination
+
+**Philosophy**: Fair termination terms protect both parties while allowing for reasonable exit if needed.
+
+Either party may terminate this agreement with [X] days written notice. Upon termination, payment is due for work completed to date. This ensures fair compensation for work done and reasonable notice for both parties to plan accordingly.
+
+### Dispute Resolution
+
+**Background**: Defines how conflicts will be resolved if they arise.
+
+**What it does**: Establishes the process for handling disagreements.
+
+**Purpose**: Provides a clear path for resolving disputes without costly litigation when possible.
+
+**Method**: {{dispute_resolution_method}} (mediation/arbitration/litigation)
+
+**Location**: {{dispute_resolution_location}}
+
+Any disputes arising from this contract shall be resolved through {{dispute_resolution_method}} in {{dispute_resolution_location}}.
+
+---
+
+### Governing Law and Jurisdiction
+
+**Background**: Determines which laws apply and where legal proceedings would take place.
+
+**What it does**: Specifies the legal framework and court system that governs the contract.
+
+**Purpose**: Provides legal clarity and predictability for both parties.
+
+**Governing Law**: This contract shall be governed by and construed in accordance with the laws of {{governing_jurisdiction}}.
+
+**Jurisdiction**: Any legal proceedings arising from this contract shall be subject to the exclusive jurisdiction of the courts of {{governing_jurisdiction}}.
+
+**Contract Language**: This contract is executed in {{contract_language}}. In case of translation, the {{contract_language}} version shall prevail.
+
+---
+
+## 12. Approval
+
+**Client Approval**:
+
+Signature: _________________  
+Name: {{client_name}}  
+Date: _______________
+
+**Contractor Approval**:
+
+Signature: _________________  
+Name: {{contractor_name}}  
+Date: _______________
+
+---
+
+## Appendix
+
+### Reference Documents
+
+- Project Pitch: `docs/1-project-brief/pitch.md`
+- Project Brief: (To be created after contract approval)
+
+---
+
+*This contract is based on the project pitch dated {{date}}.*
+

package/src/workflows/1-project-brief/alignment-signoff/pitch.template.md

@@ -0,0 +1,101 @@
+# Project Pitch: {{project_name}}
+
+> Compelling case for why this project matters and should be built
+
+**Created:** {{date}}
+**Author:** {{user_name}}
+**Status:** Ready for stakeholder approval
+
+---
+
+## 1. The Realization
+
+{{realization}}
+
+---
+
+## 2. Why It Matters
+
+{{why_it_matters}}
+
+---
+
+## 3. How We See It Working
+
+{{how_we_see_it_working}}
+
+---
+
+## 4. Paths We Explored
+
+{{paths_we_explored}}
+
+---
+
+## 5. Recommended Solution
+
+{{recommended_solution}}
+
+---
+
+## 6. The Path Forward
+
+{{path_forward}}
+
+---
+
+## 7. The Value We'll Create
+
+{{value_we_create}}
+
+---
+
+## 8. Cost of Inaction
+
+{{cost_of_inaction}}
+
+---
+
+## 9. Our Commitment
+
+{{our_commitment}}
+
+---
+
+## 10. Summary
+
+{{summary}}
+
+---
+
+## Value Trigger Chain
+
+**Strategic Summary** - [View full VTC](./vtc-primary.yaml)
+
+This project serves:
+- **Business Goal:** {{vtc_business_goal}}
+- **Solution:** {{vtc_solution}}
+- **Primary User:** {{vtc_user}}
+
+**What drives them:**
+- *Wants to:* {{vtc_positive_forces}}
+- *Wants to avoid:* {{vtc_negative_forces}}
+
+**Awareness Journey:** {{vtc_awareness_start}} → {{vtc_awareness_end}}
+
+This strategic chain ensures every design decision serves the user's psychology while achieving business goals.
+
+---
+
+## Next Steps
+
+**After approval**, proceed to:
+- **Full Project Brief** - Detailed strategic foundation
+- **Trigger Mapping** - User research and personas
+- **Platform Requirements** - Technical foundation
+- **UX Design** - Scenarios and prototypes
+
+---
+
+_Generated by Whiteport Design Studio_
+

package/src/workflows/1-project-brief/alignment-signoff/section-guide.md

@@ -0,0 +1,212 @@
+# Pitch Section Exploration Guide
+
+**Framework Inspiration**: This guide draws from proven frameworks:
+- **Customer-Problem-Solution (CPS)** - Clear structure
+- **Value Proposition Canvas** - Understanding customer needs
+- **Problem-Agitate-Solve (PAS)** - Natural flow
+- **Business Case Framework** - Investment and consequences
+
+---
+
+## 1. The Realization
+
+**Framework**: Problem-Agitate-Solve (PAS) - Start here
+
+**Questions to explore**:
+- "What have you realized needs attention?"
+- "What observation have you made?"
+- "What challenge are you seeing?"
+- "What evidence do you have that this is real?"
+
+**Best Practice: Confirm the Realization with Evidence**
+
+**Help them identify evidence:**
+
+**Soft Evidence** (qualitative indicators):
+- "Do you have testimonials or complaints about this?"
+- "What have stakeholders told you?"
+- "What patterns have you observed?"
+- "What do user interviews reveal?"
+
+**Hard Evidence** (quantitative data):
+- "Do you have statistics or metrics?"
+- "What do analytics show?"
+- "Have you run surveys or tests?"
+- "What do server logs or error reports indicate?"
+
+**Help them combine both types** for maximum credibility:
+- Start with soft evidence (testimonials, complaints, observations)
+- Support with hard evidence (statistics, analytics, survey results)
+- Show the realization is grounded in reality
+
+**Keep it brief** - 2-3 sentences for the realization, plus 1-2 sentences of evidence
+
+**Help them articulate**: Clear realization backed by evidence that frames a reality worth addressing
+
+---
+
+## 2. Why It Matters
+
+**Framework**: Value Proposition Canvas + Impact - Understanding why this matters and who we help
+
+**Questions to explore**:
+- "Why does this matter?"
+- "Who are we helping?"
+- "What are they trying to accomplish?" (Jobs)
+- "What are their pain points?" (Pains)
+- "What would make their life better?" (Gains)
+- "How does this affect them?"
+- "What impact will this have?"
+- "Are there different groups we're helping?"
+
+**Keep it brief** - Why it matters and who we help
+
+**Help them think**: Focus on the value we're adding to specific people and why that matters
+
+---
+
+## 3. How We See It Working
+
+**Questions to explore**:
+- "How do you envision this working?"
+- "What's the general approach?"
+- "Walk me through how you see it addressing the realization"
+
+**Keep it brief** - High-level overview, not detailed specifications
+
+**Flexible language** - Works for software, processes, services, products, strategies
+
+---
+
+## 4. Paths We Explored
+
+**Questions to explore**:
+- "What other ways could we approach this?"
+- "Are there alternative paths?"
+- "What options have you considered?"
+
+**Keep it brief** - 2-3 paths explored briefly
+
+**If user only has one path**: That's fine - acknowledge it and move on
+
+---
+
+## 5. Recommended Solution
+
+**Questions to explore**:
+- "Which approach do you prefer?"
+- "Why this one over the others?"
+- "What makes this the right solution?"
+
+**Keep it brief** - Preferred approach and key reasons
+
+---
+
+## 6. The Path Forward
+
+**Purpose**: Explain how the work will be done practically - which WDS phases will be used and the workflow approach.
+
+**Questions to explore**:
+- "How do you envision the work being done?"
+- "Which WDS phases do you think we'll need?"
+- "What's the practical workflow you're thinking?"
+- "Will we need user research, or do you already know your users?"
+- "Do you need technical architecture planning, or is that already defined?"
+- "What level of design detail do you need?"
+- "How will this be handed off for implementation?"
+
+**Keep it brief** - High-level plan of the work approach
+
+**Help them think**: 
+- Which WDS phases apply (Trigger Mapping, Platform Requirements, UX Design, Design System, etc.)
+- Practical workflow (research → design → handoff, or skip research, etc.)
+- Level of detail needed
+- Handoff approach
+
+**Example responses**:
+- "We'll start with Product Brief, then do UX Design for 3 scenarios, skip Trigger Mapping since we know our users, and create a handoff package for developers"
+- "Need full WDS workflow: Brief → User Research → Architecture → Design → Handoff"
+- "Just need design specs - skip research and architecture, go straight to UX Design"
+
+---
+
+## 7. The Value We'll Create
+
+**Framework**: Business Case Framework - What's the return?
+
+**Questions to explore**:
+- "What's our ambition? What are we striving to accomplish?"
+- "What happens if we DO build this?"
+- "What benefits would we see?"
+- "What outcomes are we expecting?"
+- "How will we measure success?"
+- "What metrics will tell us we're succeeding?"
+- "What's the value we'd create?"
+
+**Best Practice: Frame as Positive Assumption with Success Metrics**
+
+**Help them articulate**:
+- **Our Ambition**: What we're confidently striving to accomplish (enthusiastic, positive)
+- **Success Metrics**: How we'll measure success (specific, measurable)
+- **What Success Looks Like**: Clear outcomes (tangible results)
+- **Monitoring Approach**: How we'll track these metrics (brief)
+
+**Keep it brief** - Key benefits, outcomes, and success metrics
+
+**Help them think**: Positive assumption ("We're confident this will work") + clear success metrics ("Here's how we'll measure it") = enthusiastic and scientific
+
+---
+
+## 8. Cost of Inaction
+
+**Framework**: Problem-Agitate-Solve (PAS) - Agitate the problem / Business Case Framework
+
+**Questions to explore**:
+- "What happens if we DON'T build this?"
+- "What are the risks of not acting?"
+- "What opportunities would we miss?"
+- "What's the cost of doing nothing?"
+- "What gets worse if we don't act?"
+- "What do we lose by waiting?"
+
+**Keep it brief** - Key consequences of not building
+
+**Can include**: 
+- Financial cost (lost revenue, increased costs)
+- Opportunity cost (missed opportunities)
+- Competitive risk (competitors gaining advantage)
+- Operational impact (inefficiency, problems getting worse)
+
+**Help them think**: Make the case for why we can't afford NOT to do this
+
+---
+
+## 9. Our Commitment
+
+**Framework**: Business Case Framework - What are we committing to?
+
+**Questions to explore**:
+- "What resources are we committing?"
+- "What's the time commitment?"
+- "What budget or team are we committing?"
+- "What dependencies exist?"
+- "What potential risks or drawbacks should we consider?"
+- "What challenges might we face?"
+
+**Keep it brief** - High-level commitment and potential risks
+
+**Don't force precision** - Rough estimates are fine at this stage
+
+**Help them think**: Time, money, people, technology - what are we committing to make this happen? What risks or challenges should we acknowledge?
+
+---
+
+## 10. Summary
+
+**Questions to explore**:
+- "What are the key points?"
+- "What should stakeholders remember?"
+- "What's the main takeaway?"
+
+**Keep it brief** - Summary of key points (let readers draw their own conclusion)
+