Thread by @brandontoner

<Systematic randomization>
<Programming your attention>
<Algorithms of thought>
<Responsive reflection>

This represents a piece of the cloud of ideas I’ve been wrestling lately.

@RoamResearch + @roamhacker ’s new #SmartBlocks extension makes these lofty terms feel practical.

Could you build systems to direct your attention intentionally?

Could you systematically approach creativity?

Could you build a responsive reflection practice?

What if you could *premeditate* processes to follow given a certain trigger/situation/experience/feeling/etc

Would this be helpful?

What would it enable?

How would it change things?

… at the individual level,,, or *collectively*?

Could we *collaborate* systematically?

And *should* we?

Is intentional lack of structure a structure in itself?

If we desire a more intuitive approach could that be programmed?

Could we adjust and adapt depending on results and how it *feels*?

I’ve talked about Atomic Journaling in the past, so it feels like a good example to use.

Reflection and journaling work *very* well as an application and and example of this sort of thing.

https://twitter.com/brandontoner/status/1304847166985437188

Here’s a sample SmartBlocks randomization to generate a dynamic journaling prompt. This format could be used for LOTS of different situations.

What if you could use this format for systematic creativity using *varied constraint brainstorming*, or “What would X do?” - type prompts?

What about systematic reflection/consideration/assessment/evaluation?

I want to see what people can build with this! Imagine a library of these!

Imagine a collection of amazing prompts that apply in a wide variety of contexts.

AND what if we could start linking CONTEXT and PROCESS.

Cue: Algorithms of Thought.

https://twitter.com/cortexfutura/status/1332466073812262913

cc: @cortexfutura , @elaptics , @tracyplaces , @Conaw

Moving to *algorithms* and *automation*

I see this as linking a TRIGGER with a ROUTINE.

Building strings of “If this, then do that” logic.

More on this soon.

Open questions and projects:

- How could we DETECT the triggers, signalling the algorithm more naturally. What sensory input could be used? Habit, yes, but I’d like to find ways to rely less on my remembering to run an algorithm.

- How can I logistically organize a prompt library such that I’m able to avoid copy/paste.

Breaking page into sections introduces the same problems that file/folder creates. What if something belongs in two places?

Ok, then a master library and block ref into collections…

Not quite, the library gets messy. Hard to browse and find what I need easily.

Ok, then use tagging.

Well, yes, but then I introduce visual noise. The tag then gets carried everywhere when I block reference them.

Ok, then use [*]aliases.

Decent, but not ideal.

Really what I want is the ability to HIDE TAGS. Have them exist, but not visually sometimes. Maybe toggle #[[]] page visibility in the blocks with a keystroke?

That way I could remove *visual noise* from my decision on whether or not to tag a block.

cc: @Conaw

- Building the actual library of prompts. The algorithms. The CONTENT within the SYSTEM.

Here’s where I’m hoping for the leverage of community.

If we had a way to collectively build these prompts and algorithms, and it had an open-source nature to it.

Woah. This could be cool.