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:

FormatFEAT.
Count25
Examples"FEAT. Add refresh_commits", "FEAT. Improve UX", "FEAT. Generate-unppp-workflows"
FormatSPRINT.
Count23
Examples"SPRINT. Changed Sprint Candidates label", "SPRINT. Resolve 191 unused imports"
FormatUNPARTY.
Count19
Examples"UNPARTY. Connect theunpartybuilder to theunpartyapp", "UNPARTY. Add CORE scaffold"
FormatSTAGE.
Count18
Examples"STAGE. Change after adding routes", "STAGE. Add workflow data per unppp"
FormatLLM.
Count14
Examples"LLM. Fix activity bars", "LLM. Refactor repo metadata report"
FormatWORKFLOW.
Count12
Examples"WORKFLOW. Update", "WORKFLOW. Add refresh-unppp-scores workflow"
FormatTHINK.
Count10
Examples"THINK. Start here", "THINK. How can health be used as composite score"
FormatBRAND.
Count7
Examples"BRAND. Add font-google-sans-code", "BRAND. Update localization strings"
FormatUX.
Count6
Examples"UX. Add signature error message", "UX. Fix uppercase"
FormatDEPEND.
Count7
Examples"DEPEND. Add GitHub org to initial.py", "DEPEND. Rate limit error persists"
FormatFIX.
Count4
Examples"FIX. Load GITHUB_TOKEN fallback", "FIX. Complete CLI metadata fields"
FormatDECK.
Count3
Examples"DECK. Versioning raw-repo-metadata.json", "DECK. RepoMetadata"
FormatDATA.
Count2
Examples"DATA. Add CoreML training script", "DATA. Add training data generator"
FormatML.
Count2
Examples"ML. Add think for ARCH", "ML. Start Label ideation"
FormatMOOD.
Count2
Examples"MOOD. Remove emotion driven label", "MOOD. Start Mood feature proposal"
FormatSTORY.
Count2
Examples"STORY. Million Dollar Bill for theunpartyapp", "STORY. Update copy to remove DTLA"
FormatUI.
Count2
Examples"UI. Start UI ideation for styling"
FormatUSER.
Count2
Examples"USER. Define your CORE Stack", "USER. Create NextJs app for build-001"
FormatDEBT.
Count2
Examples"DEBT. Claude Code fix add @babel/plugin", "DEBT. Repository metrics spotted similarities"
FormatSYNC.
Count1
Examples"SYNC. package.json"
FormatSUNSET.
Count1
Examples"SUNSET. Remove CloudKit Entitlements"
FormatTRAIN.
Count1
Examples"TRAIN. CoreML classifier: 8-type RandomForest"
FormatSTART.
Count1
Examples"START. Add Dash view for global views"
FormatFOUNDER.
Count1
Examples"FOUNDER. Implement ERP schema and integrate background color picker"
FormatCONNECT.
Count1
Examples"CONNECT. theunpartyunppp to theunpartylanding"
FormatASK.
Count1
Examples"ASK. How to navigate to user defaults from UserDefaultsViewer"
FormatUNPPP.
Count1
Examples"UNPPP. Replace font-mono"
FormatMood.
Count1
Examples"Mood. Remove emotion driven label" (one instance with capital M)

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

Formatfix:
Count18
Examples"fix: fetch all commit IDs before sorting", "fix: move Python app/ modules"
Formatfeat:
Count16
Examples"feat: wire unppp leaderboard into dashboard", "feat: add full calendar/seasonality view"
Formatrefactor:
Count8
Examples"refactor: remove hardcoded Pinecone defaults", "refactor: Home component to remove unused"
Formatchore:
Count3
Examples"chore(deps): bump next from...", "chore: finalize Pinecone debug automation"
Formatdocs:
Count2
Examples"docs: weekly summary March 7-13", "docs: Create comprehensive README"
Formatdoc:
Count2
Examples"doc: add assistant keyword audit", "doc: add APP-IS-FULL-OF-SH.MD"
Formatstyle:
Count2
Examples"style: align AIWrappedVisualization Canvas", "style: align AIWrappedVisualization shell UI"
Formatstory:
Count3
Examples"story: update story-049 via unseen"
Formatux:
Count1
Examples"ux: improve conversation data timeline"
Formatdebug:
Count1
Examples"debug: surface /api/logs errors in dashboard"
Formatinvestigate:
Count1
Examples"investigate: add correlation timeline + query tool"
Formatpackage:
Count2
Examples"package:add-clerk-success", "package:add-clerk"
Formatstatus:
Count1
Examples"status:update:online"
Formatbug:
Count1
Examples"bug:api-theunpartybuilder"
Formatabout:
Count1
Examples"about: generated by theunpartybuilder"
Formatmerge:
Count1
Examples"merge: resolve conflicts with main"

SPECIAL PATTERNS & OUTLIERS (not fitting either format):

PatternMerge commits
CountMultiple
Examples"Merge pull request #18...", "Merge branch 'main'", "Merge remote-tracking branch..."
PatternEmoji-prefixed
CountMultiple
Examples"🤖 Update README cache" (from theunpartydocs)
PatternNo clear prefix
CountVarious
Examples"moving repo outside parent directory", "Add color constants", "Initial commit", "Initial Commit"

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)

#stories

🧗🏾‍♂️ in progress