Scratching off the B.S. working on Helix Project
I'm going to switch up my life strategy pretty soon. I've been doing a lot of unnecessary stressing and working.
So next move. Working on some Helix thing. That's what matters now. I really may not keep this account for long.
Helices. God there's so much time to be saved. I'm always in a rush. Always pressed for time. I can't even be productive at my job anymore and still get ahead.
Helices... That's all I need to focus on for the rest of the day. I gotta be smart about it though. Jesus.
So what ideas have I not tried? A rule node, alright. and using its own typing as a program. I would likely need some "random" somewhere as well.
Or I was thinking of having a main net & then passed around token connections. I want there to be programs sort've cruising the network of connections. And signals need to degrade over distance but at the same time be capable of handling complex stuff. So tokens seem good. They are like fuel. Or can be used like it a currency?
Idk. this whole thing needs to be thoroughly scrambled too. what can I really test? really?
what even makes sense? I don't know. All we need to do is naturally generate structured associations, right? and what else? well that first one is pretty hard. how can you send something out into the world of this hyper dimensional board game, that's going to guarantee that you fall in place with your related parts. There is the gene pair, the created and then also everything within the body (other gene pairs).
You know what's funny? I hardly recognize the people in my meetings. They are just faces over a TV screen. Its taken me 6 months to actually anchor in some names. I mean, yeah, I know who Sarah is... but... Everyone else... fuck 'em. My brain has been in such a shit storm for the entirety of this contract thanks to that damn chaos theory.
Can't wait to work more on it.
So . Back to it. Where are we at. Gene pairs. What about 'em? Yeah. Hyper dimensional board thing. So we gotta figure out what an actual edit is going to look like. What gets switched? Or dropped?
I don't know. And what about... 3pm... should I leave? or should I stay?
Definitely need to lay low & stay calm.
Ok ok ok ok ok ok...
Helices.
Back to that. What gets switched? traded? dropped? connected?
What are all the things that can happen?
-Drop Connection
-Add Connection
-Trade Flavor Connection (Red for Red? or Red for Blue? Both?)
-Change rule node. Copy from a deck of connections... I mean, a deck is the only way to not have a singularity.
-Shuffle Deck. i guess... since we're using decks now. reversed, pull forward
I mean, really, there are so many effects I can apply.
There are also rainbow states that I can flip Booleans between each pair of helices.
We may not have to trade entire flavor'd connections. Just a series of adds and drops. when changing the rule node, we can apply a flip to the new rule node, or the old one, before it's traded. how do we pick a new rule node? idk.
ok. so just flipping and switching... up. dropping? are there limits to drops? maybe a negative state for a connection? that would be interesting. I'm thinking tokens as well. for systems. and if I can get them to fall in classes some how. I can get boolean classes, but not the classes I really need. How can those naturally emerge? spreading classes? infection? So if I can spread classes by infection, what can we do with those classes? They'd be ruled by the one... okay. and it would have to have its own internal system of logic. like a brain or something. maybe. each one that is a class. ok. that's a tangible thing to the master. it's spot or it's use of the master class program. Alright... Alright...
So a node right now has:
-Class & Class State
-PortalDeck. Link to self is code
-Rule
So I'm looking at
h.classing = H;//
h.portalDeck[H] = [ H, H, H ]
h.state = H;
State is complicated. What does it actually represent? What value can it hold?
What if we go just with the portal deck and use a more "conway" like approach with the rules.
h.portalDeck[H]=[H,H,H];
everything comes in 1 by 1. that's good. I will use size compares
I may have a boolean thing per node as well.
h.state[H] = BOOL;
Dead or alive. so I'll just go with that. I will have to draw some things out. I'll see where it goes