Dump what's on your mind about Buddy Buddy — raw and unfiltered. Each dump lands in the buddy's repo (docs/ingest.md) as a timestamped entry — or saves on this device until a repo is linked and a token is connected.
🔒 Connect GitHub to unlock dumping. Paste a token once — it stays on this device only.
Enter dumps it · Shift+Enter for a new line · Images shrink to 1600px wide before upload — the original stays in your library
Nothing needs attention right now.
The markdown files in Buddy Buddy's repo, baked into this page when it was generated — tap a file name and its contents open right below it; open as many as you like at once. No sign-in and no fetching: the words are right here. To change a file, edit it in the repo — the page picks it up next time it is generated.
Buddy Types is the meta-buddy — the one that defines what buddies are. When Dave (or the system) creates a new buddy, Buddy Types provides the type definitions, expected behaviors, default values, and suggested personas. It's the schema behind the staff.
Buddy Types is the meta-buddy — the one that defines what buddies are. When Dave (or the system) creates a new buddy, Buddy Types provides the type definitions, expected behaviors, default values, and suggested personas. It's the schema behind the staff.
The buddy system has grown organically — 80+ buddies, each with their own shape. But there's no canonical definition of what a 'person buddy' vs a 'project buddy' vs a 'pet buddy' should look like: what fields they have, what behaviors they exhibit, what defaults they start with, what personas suit them. Buddy Types fixes that. It's the type system for the buddy system.
Buddy Types maintains: (1) Type definitions — person, project, pet, place, vehicle, business, etc. Each type specifies expected fields, behaviors, and lifecycle. (2) Default values — what a new buddy of each type starts with (icon suggestions, field defaults, parent suggestions). (3) Persona suggestions — which personas from the roster suit each type (e.g. human buddies get 2-3 tailored options, non-humans get a default). (4) Behavior contracts — what each type is expected to do (e.g. person buddies track relationships, project buddies track milestones). When the New Buddy sheet opens, Buddy Types powers the smart defaults behind it.
None directly — this is infrastructure for the buddy system itself. Better types mean better buddies, which means a better system.
Type validation — warn when a buddy drifts from its type. Type evolution — learn from how buddies actually get used and refine the types. Custom types — Dave defines his own. Integration with the New Buddy sheet for one-tap type selection.
No enforcement — types are guidance, not constraints. Dave can always override. No automatic reclassification of existing buddies.
What are the canonical types? (Person, Project, Pet, Place, Vehicle, Business... what else?) What behaviors are type-specific vs universal? How do personas map to types?
Raw brain-dumps about this buddy. Each entry is timestamped; work the keepers into the dossier.