Ideas for K Factor > 1

Work-product virality

The idea here is that work created in/by PostHog Code carries attribution.

• When we create a PR for them on Github and generate a description, we should attribute PostHog Code in the PR description footer. (linked of course) ~Peter had this idea in issue PostHog/code#725
• When we make a commit, we could make a Github account for PostHog Code and make PostHog Code the Co-Author of the commit, similar to what claude code does.
  • We could also append a footer to the commit description (second -m) where it says something along the lines that it was built/created in PostHog Code. (linked of course)
• When a PR is responsible for closing an issue, and we're able to detect that with "Closes #N" or something, we should have PostHog Code comment on the issue with something quirky like "Lasered by PostHog Code" or maybe something more direct to indicate that the issue was fixed by/in PostHog Code. (linked of course)
• The branches it creates could start with PostHog Code/

Direct invite loop

• Invite mechanics during the closed beta, for every person we invite, they get 1 (or N) invites to share with friends.

Share loop

• Single click to share a session: we could add the ability to share tasks/conversations with a link to colleagues so maybe a designer kicks off some frontend page changes but needs to hand the rest to an engineer who will complete the technical flows.

The issue names GitHub PR descriptions, commits, issue comments, branch names, invite mechanics, and session sharing, but no files or tests. First turn the ideas into a scoped proposal with acceptance criteria for one loop; done is not defined until the chosen behavior and validation are specified.