Planning
I understand creating structured notes and ideas around a book is important to its success. So with no idea of a real story, I have an idea for how to build on top of a concept in an abstract way.
Concept
In a lot of ways a book is just a timeline; both physically and abstractly. In a physical way, the book has a timeline that happens in pages; where "n" is some page from the book. There are other ways, you could go to a particular word; or some other pattern you like. This is just to get your mindset in the right place.
I want to redefine the idea of how a page works.
Where "n" is a page number in a book; I'd like to say that "n" is just a time in the timeline of the book.
Pattern Stacking
I think stacking patterns on top of each other is very useful; so, this provides an example of that. I will be stacking what is discussed here as a topic on top of the algorithms for generating a Pythagorean timeline.
You can find those details here: https://www.assassinatekeene.org/2018/04/pythagoreans.html
Code/Programming: Further expressed concretely and with more detail (implicit to its operation): https://www.assassinatekeene.org/2023/10/universe-of-integerprimitive.html
So, from this point forward, it is expected you understand my writings as it relates to the topic linked.
What am I talking About?
I will approach the writing of the book where the page of the book "n" ... is also the index into the Pythagorean timeline described from previous notes.
The quick structural view for writing would be:
- There is a "Face" at Page(n) ... that, you provide, this point is just meta data - what would you find on page n of a book (to continue the analogy).
- There is a "Face A", "Face B" and "Face C" at Page(n):
-- Lets call Face A: The Demon, or the Past
-- Lets Call Face B: The Wizard, or the Human, or the Present
-- Lets Call Face C: The Dragon, the Future (or the "new" Present)
- Face C is Page(n+1).
It is the case that the algorithm does give you multiple ways to reach the next page, and the next page is also involved in the content of the current page. It helps if you can understand the ideas from programming... to help make this as clever as you'd like.
//On a technical note; there is actually a "small" (n=2n+1) timeline and a "large" (n=4n+4) timeline (then there's a small prime, and a large prime as well) that are all also in parallel, and fit into the same single timeline instance. There are also about 10 symmetric locations, associated with this face or that... there is an organization to it, you can find it in the "Code/Programming" link... and decide what it all means, or how you want to use it. It just is a "Pythagorean Timeline"... a systematic... 1+1... creation of every "non-decimal" Pythagorean triple that exists in the universe.
This, of course, is limited by the number that is infinity within your system... and, I mean a number, not infinity. All systems are bound, or I would say we can know every Pythagorean triple (non decimal) that can ever exist in the universe, and it has a lot of patterns and fits in a simple and concise timeline.
The "Code/Programming" shows how easy it is to create the description/programming/algorithm(s) that generate every single Integer Pythagorean triple in the Universe - but until that is finite, and the number is infinite, you cannot actually claim it will show you all Pythagorean triples - only that it could do it if you put it in a system that puts in a number for infinity that matches up to the Universe's infinity.
Looking for Patterns
You can build on patterns both real and coincidental.
Build a story where you can still use as much or as little of the underlying Pythagorean pattern as you like, but it imbeds a more sophisticated mechanism for creating a story; a timeline.
//An unknown future; by a Pythagorean
//In theory you could read the story like normal, or... you could read it using a "Pulp Fiction" style read of your choosing... who's perspective at what time... without much extra effort when writing the book; as long as an event is properly described.... or you could ask for a compressed version, and a readthrough will be created that omits lower priority events not necessary for a "faster read."
//Sometimes you think of random shit that if you don't write down... you'd probably never bother even thinking about it again; now, there's a chance... this can be fleshed out... recursively as much as I like, for no reason at all (although a book would be the idea).
//I see things you do not see, I hear things you do not hear; they call this Schizophrenia. If you understand or can follow what I am saying here, you probably need to be on disability.
We already have some Patterns
These are what are known as Structural and Behavioral models, that ensure you create stories that are appropriately inverted from their contexts... Its a way to approach the organization of your data, it does not dictate what your data is or does.
With an organized structure already in place you can use it as a method to think about and approach, systematically, your problem of creating a story. Finding where a particular idea fits, and how it breaks down - once you have a structural architecture in place for yourself, that ensures you reach your goals in telling a story.
Things are flexible beyond belief, but you cannot accidentally break the rules of the patterns without a high cost. The idea would be, the model would never need modification - but, these things are elusive.
These are, after all, only notes about a book I would write.
The Ideal story I will tell will be one with "time" and "timelines" as the central concept (repeating the pattern of layering the pattern we know of as a timeline); some adventures around black holes and things like that. That would create a triple layering of the timeline concept/theme - and would drive home how all of these things do everything, and nothing.
Timelines do not have decimals... An event happens... there are events before it and events after it... and they are all ordered and structured by what is discussed here. The timeline provided does not deal with decimals - that would mean you misunderstand how I mean to say this should work.
You must understand, and then you can be the author of how it gets implemented. Just, follow the rules within the patterns when you organize your data. If you want to make hash functions or a decimal system, as part of your own topping and addition to the design - that is up to you. Patterns on and in patterns - these are of your discretion, it still requires you do not violate the rules of IoC Patterns... You cannot lose the inversion of control.
Event Driven Story
This is a pattern right out of programming... instead of writing a book from the start to the finish... you decide what events you want to happen in your book, and you put those in where you need them; as you need more events, you make them.
At some point, your story will be complete; a timeline of events called a book... or whatever.
Composite Pattern Timeline
As noted at the start, there is the physical timeline of a book (the pages) and the abstract timeline of the book (the time within the story itself). You can use a "physical" timeline instance(s) for your book structure, then also use a "abstract" timeline instance(s), but these connections are built in to be transparent and are up to the author how it is implemented.
//You can read more about the Composite Pattern elsewhere.
//The Command Pattern would be the pattern implicitly responsible for the event driven executions... this would be parallel and asynchronous closures when possible... again; the specific implementation is up to the author. Again, read more elsewhere - when using events, everything just executes events: events that fire events to complete its job (so there may be no need for the Command Pattern).
//These patterns are not only for programming, if you understand what the rules say - they work in an abstract way that you as a person can follow (the rules of)... to clean up your data... put one instance of a thing in place, and have it used by every other thing (instead of any duplication)... and apply this idea at infinitum.
//All of this is not to make things more complicated, but it does make things more complex... but, if writers block is a thing, it will not be when dealing with the way to force you to answer your own questions around an event... such that... You can quickly make your plot twists move from one location to another... or what have you... and the rest of your data would "understand" how it should behave when it's time (event) comes, without needing to update it.
//Once you know everything, everything is simple. Philosophically speaking, I'm the first to say I know some things and don't know most things. You may never be able to explain to a single other person; but, if you just write down the things you know... sooner or later, people always will say "ohh! that's what he meant, that is a simple way to look at it now that I understand it.".. Nothing in the world is hard to know... each thing to another... there is just to know, or not to know... the actual act of knowing complicated things, is - in fact - simple.
Comments