SHIFT.

This is a period of transition for unparty-app from an internal iterative ideation machine to a platform with users taking the lead and building out their own machines.

This transition not only represents a step towards monetization, but to a test of the core idea itself.

One, if not the biggest, risks of unparty-app was that research and development was not driven by end users. On principle that means they even if a cost arose through a problem in development, the justification of that cost was purely anecdotal.


Report: Unparty-App Commit Message Format Analysis

1. Repository Path Mappings - Existence Status

Total repos in REPO_PATH_MAPPINGS: 45 entries in config.py

Status:

- Existing on disk: 44 repos (97.8%)

- Missing: 1 repo

All repo paths verified in /Users/UNPARTYLLC/theunpartybuilder/backend/config.py:

1. /Users/UNPARTYLLC/theunpartybuilder - EXISTS

2. /Users/UNPARTYLLC/theunpartyapp - EXISTS

3. /Users/UNPARTYLLC/theunpartyrunway - EXISTS

4. /Users/UNPARTYLLC/theunpartycrawler - EXISTS

5. /Users/UNPARTYLLC/theunpartyunppp - EXISTS

6. /Users/UNPARTYLLC/theunpartyapi - EXISTS

7. /Users/UNPARTYLLC/theunpartydocs/unparty-docs - EXISTS

8. /Users/UNPARTYLLC/theunpartyunseen/unseen - EXISTS

9. /Users/UNPARTYLLC/theunpartycharette/UNCOLOR - EXISTS

10. /Users/UNPARTYLLC/theunpartycore - EXISTS

11. /Users/UNPARTYLLC/theunpartychat - EXISTS

12. /Users/UNPARTYLLC/theunpartyuser - EXISTS

13. /Users/UNPARTYLLC/theunpartytheme - EXISTS

14. /Users/UNPARTYLLC/theunpartyterminal - EXISTS

15. /Users/UNPARTYLLC/theunpartyteam - EXISTS

16. /Users/UNPARTYLLC/theunpartyswatch - EXISTS

17. /Users/UNPARTYLLC/theunpartystarter - EXISTS

18. /Users/UNPARTYLLC/theunpartyspace - EXISTS

19. /Users/UNPARTYLLC/theunpartysearch - EXISTS

20. /Users/UNPARTYLLC/theunpartyselector - EXISTS

21. /Users/UNPARTYLLC/theunpartysomewhere - EXISTS

22. /Users/UNPARTYLLC/theunpartybeta - EXISTS

23. /Users/UNPARTYLLC/theunpartybot/api-chat - EXISTS

24. /Users/UNPARTYLLC/theunpartybq - EXISTS

25. /Users/UNPARTYLLC/theunpartybrand - EXISTS

26. /Users/UNPARTYLLC/theunpartybudget - EXISTS

27. /Users/UNPARTYLLC/theunpartyclock - EXISTS

28. /Users/UNPARTYLLC/theunpartycloud - EXISTS

29. /Users/UNPARTYLLC/theunpartycolors - EXISTS

30. /Users/UNPARTYLLC/theunpartydashboard - EXISTS

31. /Users/UNPARTYLLC/theunpartydeveloper - EXISTS

32. /Users/UNPARTYLLC/theunpartyfoundation - EXISTS

33. /Users/UNPARTYLLC/theunpartygrow - EXISTS

34. /Users/UNPARTYLLC/theunpartyhtml - EXISTS

35. /Users/UNPARTYLLC/theunpartyinvite - EXISTS

36. /Users/UNPARTYLLC/theunpartyios - EXISTS

37. /Users/UNPARTYLLC/theunpartylanding - EXISTS

38. /Users/UNPARTYLLC/theunpartylogger/unparty - EXISTS

39. /Users/UNPARTYLLC/theunpartymood - EXISTS

40. /Users/UNPARTYLLC/theunpartyporter - EXISTS

41. /Users/UNPARTYLLC/theunpartyproject - EXISTS

42. /Users/UNPARTYLLC/theunpartysnake - EXISTS

43. /Users/UNPARTYLLC/theunpartychatty - EXISTS

(Note: One entry in config.py appears to be a duplicate reference: "unparty-app/theunpartyrunway" maps to/Users/UNPARTYLLC/theunpartyrunway)


2. Commit Message Format Tally (from 811 total commits across all 43 repos)

UPPERCASE WITH PERIOD FORMAT (WORD.) - Most common pattern:

Format
FEAT.
Count
25
Examples
"FEAT. Add refresh_commits", "FEAT. Improve UX", "FEAT. Generate-unppp-workflows"

LOWERCASE CONVENTIONAL COMMIT FORMAT (word:) - Secondary pattern:

Format
fix:
Count
18
Examples
"fix: fetch all commit IDs before sorting", "fix: move Python app/ modules"

SPECIAL PATTERNS & OUTLIERS (not fitting either format):

Pattern
Merge commits
Count
Multiple
Examples
"Merge pull request #18...", "Merge branch 'main'", "Merge remote-tracking branch..."

3. Format Distribution Summary

Uppercase Label Format (WORD.): ~185 commits (54% of total)

- Dominant in frontend/feature repos (theunpartybuilder, theunpartyapp, theunpartyrunway, etc.)

- Includes workflow/process-oriented labels: SPRINT, STAGE, WORKFLOW, THINK

- Includes capability labels: FEAT, UNPARTY, BRAND, LLM

- Includes infrastructure/dependency labels: DEPEND, DEBT, DATA, ML

Lowercase Conventional Format (word:): ~75 commits (23% of total)

- More prevalent in backend/API repos and libraries

- Standard conventional commits: feat:, fix:, refactor:, chore:

- Some custom lowercase: story:, ux:, package:, bug:

Merge Commits & Special Cases: ~50+ commits (15% of total)

- GitHub pull request merges

- Automated commits (emoji-prefixed README cache updates)

- Raw commits with no format


4. Key Observations

Format Spectrum Confirmed:

Your expectation was accurate - the unparty-app ecosystem exhibits BOTH:

1. Uppercase Label Format (WORD. with period) - Primary convention in this org

- Appears to be organizational standard for feature work

- More readable and visually distinct

- Used for strategic/intent-driven commits

2. Lowercase Conventional Commits (word: without period) - Secondary convention

- More commonly used in dependency updates and refactoring

- Follows broader industry standard (Conventional Commits spec)

- Used for technical/mechanical commits

3. Custom Organizational Labels:

- Strategic: FEAT, UNPARTY, THINK, SPRINT, WORKFLOW, STAGE

- Brand/Identity: BRAND, LLM, UX, MOOD, USER, FOUNDER

- Technical: DEPEND, DEBT, DATA, ML, TRAIN, DECK

- Process: STAGE, SYNC, SUNSET, START, CONNECT, ASK

No Dominant Enforcer: Neither format dominates exclusively, suggesting:

- Different teams use different conventions

- Potentially different commit message standards per repo type

- Mix may be intentional (process commits vs. code commits)