diff options
author | user <user@localhost.localdomain> | 2020-01-02 09:44:44 -0800 |
---|---|---|
committer | user <user@localhost.localdomain> | 2020-01-02 09:44:44 -0800 |
commit | e1ce3cbafd2cf3a9d22320c6a56f372b94492f0f (patch) | |
tree | 42778113e575b2c01c38cc8b66d6affb0b380ea9 | |
parent | c78c16870ec27b9129bfa9efbe21333ba662598c (diff) | |
download | standingwithresilience-e1ce3cbafd2cf3a9d22320c6a56f372b94492f0f.tar.gz standingwithresilience-e1ce3cbafd2cf3a9d22320c6a56f372b94492f0f.zip |
corework
-rw-r--r-- | starts/meaning-vm/core.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/starts/meaning-vm/core.txt b/starts/meaning-vm/core.txt index 4121a57..209d454 100644 --- a/starts/meaning-vm/core.txt +++ b/starts/meaning-vm/core.txt @@ -2,3 +2,7 @@ - the problem-parts used by solutions show the problem-similarities needed in trying to apply the solution-parts elsewhere. this starts with a metric of when the approach can work. THAT IS: once you find and simplify a solution, the problem structure the solution uses shows at least one way to generalize the problem. + +- when i applied this transformation to this set of patterns, the results all had these parts the same. Is this similaritu helpful/meaningful/might it have a reason? + if so i guess I'd better relate around it more, maybe apply + it to more things, or use it as something to explore. |