There are two main functions of this repo,
- Implement all github specific goodness
- Org README
- Issue Templates
- PR Templates
- Other special files
- Utilize the discussions tab effectively (see categories)
The goal here is to manage khaaliDimaag using github discussions (and github in general) while also having enabling public transparency and input. As such, the discussion categories are designed to help move a thought-bubble, all the way to a release-announcement, going through all manner of discussions from implementation details to ethical concerns to business impact.
Every new feature or product passes through a set of discussion categories and as the discourse
progresses through the categories, the roadmap of that feature or product is informed. The
discussion categories are mapped to 4 bits, where each bit place value holds a special meaning,
informed by whether it is a
-
$0$ broadly represents the heart or the feel or the abstract; simultaneously being nothing and everything. -
$1$ broadly represents the brain or the facts or the reality; ie, it is well defined and a "grounded" unit.
| Mapping | Category Name | Description | When to use? |
|---|---|---|---|
| thought-bubble | an idea; the concepts of a plan | half baked features begin here | |
| napkin-math | a more structured and reasoned out idea | feature ideas may also begin here but have a higher bar of acceptance | |
| onboarding | strategies to reduce friction for users to leverage kdio | when discussing how new users discover, access, and start using a feature | |
| context-switch | how kdio fits inside a different domain | does the new feature enable kdio to operate in a different domain? | |
| its-ethical-ethical | with great power, comes great responsibility | to consider the ethical implications of this new idea | |
| outsiders-forum | speak less, read more! | could be used as a customer support channel | |
| marketing-stunts | how we occupy mindshare | when discussing positioning, narrative, and public-facing communication strategies | |
| thanks-obama | all democratic polls conducted here | when the discussion reaches a stage requiring some form of voting, either internally, or publically | |
| incentive-design | all things regarding mechanism design, tokenomics, and game theory | to discuss what this new idea will enable / disable | |
| validation-framework | validating the idea and assumptions | use this to talk about how we validate our assumptions and track success | |
| user-experience | mapping user flows and journeys | to talk about e2e user experiences | |
| interface-design | all things related to the clients interacting with the protocol | how do we make sure that anyone may build a client? | |
| protocol-infra | any updates to the core protocol needed | to talk about how or if this idea adds any value to core infra or protocol | |
| protocol-security | consideration of all things security, including user error! | when evaluating attack vectors, failure modes, edge cases, and defensive measures | |
| doing-business | how do we ensure the protocol makes money, or is anti-fragile? | to discuss revenue streams from this idea | |
| release-announcement | fuck it, ship it! | the last step of discussions, talking about how we announce this new feature post implementation |
Important
Note that implementation of the idea/feature may happen while the discussions are taking place as it moves through the different discussion categories
| Place Value | track | vibe | ||
|---|---|---|---|---|
| exploration | execution | phase | what phase is the discussion in? | |
| self | world | tether | where is this discussion tethered? | |
| foundational | manifestation | layer | which layer is this discussion on? | |
| intrinsic | extrinsic | orientation | how is this discussion oriented? |
One thing to note here is that the discussion category with
Also the bit-flipping mechanism coupled with the place-value semantic naming also enables us to jump around these discussion categories by choosing a track. The 4 place values give us 4 tracks to choose from:
the-phaseInterleaves thinking and doing (Good for features where you want to validate ideas incrementally rather than planning everything upfront)the-tetherAlternates between self-focused and world-focused concerns (Good for features that need strong internal conviction before external engagement)the-layerGoes from foundational to manifestation at each level (Good for features where you want to build up from first principles before making anything visible)the-orientationThe natural counting order — intrinsic first, then extrinsic (Good as a general-purpose default because it ensures you fully understand the thing itself before considering it in relation to others)
| Mapping | Theme | ||
|---|---|---|---|
| thought-bubble | incentive-design | from "what if?" to "why would anyone?" | |
| napkin-math | validation-framework | from structured thought to structured testing | |
| onboarding | user-experience | from entry point to entire path | |
| context-switch | interface-design | from domain fit to system boundary | |
| its-ethical-ethical | protocol-infra | from "should we?" to "how do we build it right?" | |
| outsiders-forum | protocol-security | from listening to defending | |
| marketing-stunts | doing-business | from capturing attention to capturing value | |
| thanks-obama | release-announcement | from consensus to launch |
| Mapping | Theme | ||
|---|---|---|---|
| thought-bubble | its-ethical-ethical | the idea meets its moral weight | |
| napkin-math | outsiders-forum | what we think vs what they think | |
| onboarding | marketing-stunts | pulling users in vs reaching out | |
| context-switch | thanks-obama | domain mapping vs reality check | |
| incentive-design | protocol-infra | rules of the game vs the field it's played on | |
| validation-framework | protocol-security | probing our assumptions vs defending against others' probes | |
| user-experience | doing-business | value delivered and value captured | |
| interface-design | release-announcement | designing the touchpoint vs announcing the arrival |
| Mapping | Theme | ||
|---|---|---|---|
| thought-bubble | onboarding | what it is vs how they find it | |
| napkin-math | context-switch | what we reason and where it fits | |
| its-ethical-ethical | marketing-stunts | what we stand for vs how we say it | |
| outsiders-forum | thanks-obama | hearing voices and counting votes | |
| incentive-design | user-experience | the rules underneath vs the experience on top | |
| validation-framework | interface-design | hypothesis and implementation | |
| protocol-infra | doing-business | what holds it up vs what keeps it alive | |
| protocol-security | release-announcement | securing the system and spotlighting it |
| Mapping | Theme | ||
|---|---|---|---|
| thought-bubble | napkin-math | raw intuition meets structured reasoning | |
| onboarding | context-switch | native context vs foreign context | |
| its-ethical-ethical | outsiders-forum | our ethics vs their feedback | |
| marketing-stunts | thanks-obama | we speak, they vote | |
| incentive-design | validation-framework | build the model vs validate the model | |
| user-experience | interface-design | what we want them to feel and how we make them feel that | |
| protocol-infra | protocol-security | the core vs defending the core | |
| doing-business | release-announcement | making it work vs making it known |