Tinderbox Meetup 26 JUL 26: Musing on Data (what is it) and Tagging Strategies in Tinderbox
| Level | Intermediate |
| Published Date | 7/27/26 |
| Revision | 1 |
| Tags | Data, Tagging, 5CKM, 5Cs of Knowledge Management, Eastgate, Identity Praxis, Inc., Mark Bernstein, Michael Becker, Tinderbox |
| Video Length | 01:35:51 |
| Video URL | https://youtu.be/J8oO_fJtqA0 |
| Example File | TBX Meetup 26JUL26.tbx (168.3 KB) |
| TBX Version | 11.5 |
| Instructor | Michael Becker |
In this Tinderbox Meetup, we explored a deceptively simple question: What is data? Before diving into Tinderbox workflows, the group examined the relationship between data, information, knowledge, and the systems that create and manage them. The discussion highlighted that data is not simply “there”—it is collected, contextualized, interpreted, and ultimately transformed into knowledge through curation and analysis. This naturally led into broader conversations about AI, privacy, ownership of digital information, and why thoughtful knowledge management is becoming increasingly important.
Building on that conceptual foundation, we shifted into a hands-on discussion of incremental formalization in Tinderbox. Using a real forum question about organizing one hundred notes, we demonstrated several practical strategies for evolving an unstructured collection of notes into a well-organized knowledge base. The session compared the use of tags, attributes, sets versus lists, prototypes, folders, agents, adornments, and maps, emphasizing that there is no single “correct” workflow. Instead, Tinderbox allows users to progressively add structure as their understanding develops, creating flexible systems that evolve alongside their thinking.
Five Key Takeaways
- Start by defining your information model. Before tagging notes, ask fundamental questions: What is data? What is a note? When does data become information or knowledge? Your answers should shape how you organize your Tinderbox document rather than the other way around.
- Use incremental formalization instead of over-designing upfront. Begin with simple notes and gradually introduce tags, attributes, prototypes, agents, and maps as patterns emerge. Let structure evolve naturally with your understanding.
- Choose the right organizational mechanism for the job. We compared multiple approaches—including folders, tags, prototypes, adornments, and agents—and discussed the tradeoffs of each. Tags help classify, prototypes encapsulate common behaviors, agents automate organization, and adornments provide visual grouping.
- Think carefully about tagging strategy. The session demonstrated how Tinderbox’s built-in Tags attribute (a set) differs from user-created attributes (lists or sets), why sets prevent duplicate values, and how thoughtful tag definitions can become the foundation for powerful agent-driven workflows.
- Build systems that help you think, not simply store information. AI can rapidly generate hundreds of notes, but the real value comes from curating, correlating, visualizing, and refining those notes into meaningful knowledge. Tinderbox excels not because it stores information, but because it supports the ongoing process of sensemaking.