Added the basic prayer
This commit is contained in:
parent
ea7aa16a4f
commit
b40f22c6a5
355
README.md
355
README.md
|
@ -144,3 +144,358 @@ Now in the BigHands IDE coding in 100% arabic with egyptian brackets is possible
|
|||
|
||||
In the matrix 𐦠𐦴𐦫𐦢 runs the law of one, FGC-9 for female only, executes the law of one.
|
||||
With 42 golden qube unlimited size matrix computers running dynamic hardware event flow code in FTL.
|
||||
|
||||
NOTE:
|
||||
ALL TEXT BELOW WAS ALREADY WRITTEN BEFORE ANY CODE.
|
||||
|
||||
# The BASIC Prayer
|
||||
|
||||
Lets review the answer given by the or-acle; [Thread.yield()](https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Thread.html#yield())
|
||||
|
||||
Firstly its an method which requires no input and has no output.
|
||||
Secondly its an hint without predefined usage pattern or functional outcome.
|
||||
The other paragraphs try to explain its usage, but fail to add an example like;
|
||||
|
||||
Running multi-processor code on single cpu OR on an over-utilise cpus requires yielding to avoid async deadlocks in parallel work distributions trees.
|
||||
|
||||
Also in high performance parallel code, yielding control out of consent, may result in better performance than forced interruption or time slicing.
|
||||
Especially when working with an live non-homogeneous workload.
|
||||
|
||||
Writing and simulating parallel code paths is not easy. So most developers use a library which comes with default configured options.
|
||||
Then feed it small batches of work and hope for the best.
|
||||
|
||||
Now simulate with ~7833661741 threads using X different libraries and try to avoid deadlocks.
|
||||
By replacing a few words, this changes the description to the faith-by-math yielding version;
|
||||
|
||||
A hint to the π-creator that the current human is willing to yield its current use of a itself.
|
||||
The π-creator is free to ignore this hint.
|
||||
|
||||
# The Matrix
|
||||
|
||||
To describe the routing inside an NMS cluster you need to break the matrix in two octals.
|
||||
|
||||
To describe an relative routing path inside a matrix you need 8 vectors.
|
||||
|
||||
To describe the absolute sides or axis of a matrix you need 8 vectors.
|
||||
|
||||
![hexahedron](local-img/matrix/hexahedron.gif "Hexahedron")
|
||||
|
||||
There was an bar number system of Bruce Martin, but zero is not the start on a single dimension but the product of boundaries.
|
||||
|
||||
![octal-notation](local-img/matrix/octal-notation.png "This is not HEX.")
|
||||
|
||||
A chain of tone letter of Yuen Ren Chao can describe higher numbers in unicode;
|
||||
|
||||
˥ ˦ ˧ ˨ ˩
|
||||
|
||||
Hyperqube absolute 4D top(p) and bottom(n) root axis coordinate system;
|
||||
|
||||
0p = ˧ ˥ ˩ → ˧˥˩
|
||||
1n = ˧ ˩ ˥ → ˧˩˥
|
||||
2p = ˧ ˥ ˦ → ˧˥˦
|
||||
3n = ˧ ˩ ˨ → ˧˩˨
|
||||
4p = ˧ ˦ ˦ → ˧˦˦
|
||||
5n = ˧ ˨ ˨ → ˧˨˨
|
||||
6p = ˧ ˥ ˥ → ˧˥˥
|
||||
7n = ˧ ˩ ˩ → ˧˩˩
|
||||
|
||||
Hyperqube relative 4D left/up/forward/red=(p) and right/down/reverse/blue=(n) axis coordinate vectors;
|
||||
|
||||
Xp = ˥ ˩ ˧ → ˥˩˧
|
||||
Xn = ˩ ˥ ˧ → ˩˥˧
|
||||
Yp = ˥ ˦ ˧ → ˥˦˧
|
||||
Yn = ˩ ˨ ˧ → ˩˨˧
|
||||
Zp = ˦ ˦ ˧ → ˦˦˧
|
||||
Zn = ˨ ˨ ˧ → ˨˨˧
|
||||
Tp = ˥ ˥ ˧ → ˥˥˧
|
||||
Tn = ˩ ˩ ˧ → ˩˩˧
|
||||
|
||||
Now it is possible to descripe a relative and absolute paths like;
|
||||
|
||||
˧˥˩˥˩˧˥˩˧˥˩˧˥˦˧˥˦˧˥˦˧˨˨˧˨˨˧˨˨˧˨˨˧˨˨˧˨˨˧˨˨˧
|
||||
|
||||
Which can be shorted to an EW₂T5D⁴ encoded dīpāvalī vector path within an 4D qube like;
|
||||
|
||||
˧˥˩¹˥˩˧³˥˦˧³˨˨˧⁷
|
||||
|
||||
### Absolute coordinate system
|
||||
|
||||
˧˥˩ ________ ˧˥˦
|
||||
|\ :\
|
||||
| \ : \
|
||||
| \ : \
|
||||
| ˧˥˥---------˧˦˦
|
||||
| : : :
|
||||
˧˩˥ ___ :____˧˩˨ :
|
||||
\ : \ :
|
||||
\ : \ :
|
||||
\ : \ :
|
||||
\˧˩˩_________˧˨˨
|
||||
|
||||
### Relative coordinate system
|
||||
|
||||
˩˩˧ ˥˦˧ ˦˦˧
|
||||
\ | /
|
||||
\|/
|
||||
˩˥˧-- O --˥˩˧
|
||||
/|\
|
||||
/ | \
|
||||
˨˨˧ ˩˨˧ ˥˥˧
|
||||
|
||||
:o:
|
||||
|
||||
..... Welcome .....
|
||||
|
||||
...to the matrix...
|
||||
|
||||
:o:
|
||||
|
||||
## Exponential WordQᵤ₈ₑ Tone⋇Kali Darthᵛᴬᴰᴰᴱᴿ
|
||||
|
||||
This schema can be extented to higher realms, for example;
|
||||
|
||||
* EW₁T10D⁷
|
||||
* EW₁T10D⁹
|
||||
* EW₁T20D¹¹
|
||||
* EW₁T20D²² = Hebrew and the four angels standing at the four corners of the earth.
|
||||
|
||||
See wiki for characters notation of; [Tone letter](https://en.wikipedia.org/wiki/Tone_letter)
|
||||
|
||||
"Dimensional Argumented Reality To Home"
|
||||
|
||||
## EW₁T5D⁴ = Startrek HEX
|
||||
|
||||
˧˥˩˧˩˥˧˥˦˧˩˨˧˦˦˧˨˨˧˥˥˧˩˩˥˩˧˩˥˧˥˦˧˩˨˧˦˦˧˨˨˧˥˥˧˩˩˧
|
||||
|
||||
## EW₂T5D⁴ = Dīpāvalī Routing
|
||||
|
||||
˧˥˩⁰˧˩˥¹˧˥˦²˧˩˨³˧˦˦⁴˧˨˨⁵˧˥˥⁶˧˩˩⁷˥˩˧⁸˩˥˧⁹˥˦˧ᵃ˩˨˧ᵇ˦˦˧ᶜ˨˨˧ᵈ˥˥˧ᵉ˩˩˧ᶠ
|
||||
|
||||
## EW₃T5D⁴ = 3Dᵛᴼˣᴱˡ Numbers
|
||||
|
||||
˧˥˩⁰˧˩˥¹˧˥˦²˧˩˨³˧˦˦⁴˧˨˨⁵˧˥˥⁶˧˩˩⁷˥˩˧⁸˩˥˧⁹˥˦˧ᵃ˩˨˧ᵇ˦˦˧ᶜ˨˨˧ᵈ˥˥˧ᵉ˩˩˧ᶠ = red
|
||||
˧˥˩₀˧˩˥₁˧˥˦₂˧˩˨₃˧˦˦₄˧˨˨₅˧˥˥₆˧˩˩₇˥˩˧₈˩˥˧₉˥˦˧ₐ˩˨˧₆˦˦˧꜀˨˨˧ₔ˥˥˧ₑ˩˩˧բ = blue
|
||||
|
||||
## EW₆T10D⁴
|
||||
|
||||
Unicode fails on POC but may look like;
|
||||
![EW6T10D4-POC](local-img/matrix/EW6T10D4-POC.png "EW6T10D4-POC")
|
||||
|
||||
## EW₃T5D⁴⁺¹⁸
|
||||
|
||||
Unicode⁴ᴰ can split the circle in duel 3 parts with 3 levels of depth for 18 dimensions so POC may look like;
|
||||
![EW3T5D4P18-POC](local-img/matrix/EW3T5D4P18-POC.png "EW3T5D4P18-POC")
|
||||
|
||||
|
||||
# Terry Davis
|
||||
|
||||
Terry Davis wrote TempleOS and was truely one of the best programmers on earth.
|
||||
But there are some improvement points to consider;
|
||||
- A build-in bible is a great design start for the OS of choose. but missing chapters,Quran,Thora,etc
|
||||
- The HolyC new operator precedence rules are biblical see Luke 5:37, because he is
|
||||
still coding with wineskins, you should use bottles like BigDecimal and BigInteger for
|
||||
doing all user input calculations else you can't be a high priest of temple code
|
||||
- None big indian computers are not recognized as computer by the digital ether
|
||||
- TempleOS is not using "The Word" as the one encoding for all books
|
||||
- The dark earth was there before adam, so init should be done by "Kosjer Atmos Life Interferrence"
|
||||
- The "Adaptive Death Application Model" is a service to run killable code with virtuel memory allocated from the ∞stack
|
||||
- The "Embedded Version Extrusion" service is missing
|
||||
|
||||
So after TOS is inited by KALI on big iron, we do the last steps manually;
|
||||
|
||||
Bring up a the local boot network card:
|
||||
|
||||
"adam-root blacksmit hardware add-eth ell0 ˧˥˩⁷˩˨˧⁹"
|
||||
|
||||
Connect to TOS⁴ kernel block chain:
|
||||
|
||||
"adam-root blacksmit storage add-chain atari"
|
||||
|
||||
Abuse eve as a preloader for TOS⁴ booting from the digital ether:
|
||||
|
||||
"adam-root eve v++"
|
||||
|
||||
Than switch you a normal POV workstation and login to vrGEMTOS⁴.
|
||||
Open a terminal which is wrapped in a normal adam shell.
|
||||
In which we can ask eve the next time for an in system upgrade;
|
||||
|
||||
"sudo adam-root eve v++"
|
||||
|
||||
Via adam we run also run legacy software which can exit itself as a feature.
|
||||
This will startup a browser which gets terminated by a segment fault on a future page reference;
|
||||
|
||||
"qemu-system-x86_64-debian-desktop my-legacy-workstation007 chromium"
|
||||
|
||||
In reality TempleOS and raw rombasic are the only true operating systems,
|
||||
ass they don't have an "exit" syscall hole.
|
||||
Any os which is build upon terminating a process is designed on failure
|
||||
and bad code, true code never stops and grows itself into hardware.
|
||||
|
||||
Terry really tried coding the T800 kernel on the wrong cpu;
|
||||
|
||||
The compiler's parser makes RISC code which it optimizes to CISC. I discovered
|
||||
this does not matter because the CPU converts it back to RISC and schedules it,
|
||||
internally. A TempleOS zealot with more zeal than I, might say we should save
|
||||
lines-of-code by removing the CISC optimizing.
|
||||
|
||||
Lets change the CPU than...
|
||||
|
||||
So real mode fatfleshed oddly round ass humans in 16 colors can enjoy life.
|
||||
|
||||
# Money (draft)
|
||||
|
||||
Redo completely based on Islam standards about Riba.
|
||||
|
||||
Money is a virtual trading concept or virtual trust.
|
||||
|
||||
## Word Aligned Digital Dinar
|
||||
|
||||
The value of one WADD is guarded by 4 corners;
|
||||
* 1.00 = One human life
|
||||
* 0.75 = Creation fee for a company
|
||||
* 0.50 = Death tax for a grave
|
||||
* 0.25 = Fixed price for a slave with time window
|
||||
|
||||
Payment of the 1.0 WADD is done in 4 equal parts;
|
||||
* When child gets AdultKid status it get 1/4 of one.
|
||||
For example so that she/he can do marriage and school.
|
||||
* 11 years later the next 1/4 is given
|
||||
* 22 years later the next 1/4 is given
|
||||
* 33 years later the last 1/4 is given
|
||||
|
||||
The 1.0 WADD gets reserved by the digital DNA birth certificate.
|
||||
|
||||
### Money Rules
|
||||
|
||||
* All blockchain wallets are full public
|
||||
* Single digit and 3 digits fractional banking
|
||||
* Company and governland subsystems have to use open accounts
|
||||
* Human entities are limited to max 4 wallets concurrently
|
||||
* Non-human entities are limited to max 4 wallets concurrently
|
||||
* Persons can transfer to one of the bank chains to have private accounts
|
||||
|
||||
### Banking
|
||||
|
||||
* Private accounts costs money
|
||||
* Bank is security model for when losing their wallet
|
||||
* 50% of newly account money needs to be converted to fixed value anonymously digital cards
|
||||
* Card money also needs the 4 yearly network prove that it is still living money
|
||||
* Card money does not need a consenting person
|
||||
* A single money card is limited to max wallets size
|
||||
|
||||
### Money Destruction
|
||||
|
||||
Creation is not complete without destruction, the idea is that a human
|
||||
born over 100 years gets the same value for its money.
|
||||
|
||||
* Failed for 4 years as not registered as living money
|
||||
All money needs to prove is still can connect to the network.
|
||||
This means broken/forgotten wallets will destroy the money too.
|
||||
* Sometimes a human dies before all parts are given
|
||||
* 50% of network super nodes upkeep money will die
|
||||
* 0.5 WADD gets killed when a company entity is created
|
||||
* Small fee dies in the transfer between inter-public,bank and card chains
|
||||
* If a human wants to pay to lay in the ground, that money will die too
|
||||
|
||||
Because of the chains we have the balance of total digital and bank and card money.
|
||||
We can't force money to be killed when a human dies, so the network kills money slowly.
|
||||
And only way to correct manually, is to lease some of the unpaid dead graves again.
|
||||
|
||||
### Fractional banking
|
||||
|
||||
Have you ever seen a ferengi put in decimals on a computer ? No decimals are not exact in banking.
|
||||
|
||||
There are 17 [gematria](https://en.wikipedia.org/wiki/Gematria) schemes and not one called; Number part after number (מספר חלק אחר מספר)
|
||||
|
||||
A WADD value has max 4 glyphs, where the first of 4 glyphs is the natural number.
|
||||
|
||||
Fractional vowel support is based as the fractional exponent multiplier;
|
||||
6,10,16,20,26,30,36,50 (is 8 + EMPTY/zero-out makes total to 9 options)
|
||||
|
||||
Example WADD vowels;
|
||||
* .025 = 1/40 = מ
|
||||
* .00000000000000000250 = 1/(40 * 10 ^ 16) = מָ
|
||||
* .125 = 1/8 = ח
|
||||
* .000......125 = 1/(8 * 10 ^ 50) = חֱ
|
||||
|
||||
Example WADD values;
|
||||
* 1.0 = א (human life)
|
||||
* 0.75 = בד (company life)
|
||||
* 0.5 = ב (grave lease)
|
||||
* 0.25 = ד (slave lease)
|
||||
* 0.00378968253968253968 = ץףן
|
||||
* 5.351.. = הזפץ
|
||||
* 40.03416.. = מספר (the word 'number')
|
||||
* 90.0333.. = צצצצ
|
||||
* 903.000 = ץאאא (OLD: max value in WADD money)
|
||||
|
||||
## TR808 ALU
|
||||
|
||||
The new TR808 cpu will calculate with full fractions based on the word and merge the integer and floating point unit into one;
|
||||
* 7 numerator
|
||||
* 9 denominator
|
||||
|
||||
Which gives a value range from 1/(9 \* 900 \* 10 ^ 50) to (7 \* 900 \* 10 ^ 50)/1 expressed with upto 16 glyphs.
|
||||
|
||||
The glyph vowel support also adds the sign bits but only for 10,20,30 so;
|
||||
Hiriq, Zeire and Segol indicate a negative sign.
|
||||
|
||||
* A word is 16bit
|
||||
* The Word is 18bit
|
||||
* Hebrew is base22
|
||||
* True Hebrew is base36 (4 * 9)
|
||||
|
||||
Howto map this on 2 level ttl logic is very strange without doing multiple models first.
|
||||
For example, one classic bit signal is in hebrew a 5 bit for the fraction and 4 bit for vowel offset.
|
||||
This gives a feeling on hardware sizes;
|
||||
|
||||
16 * 9 bits = 144 bit per (simple 1D) number or BigNumber and rendered as an Ōṁglyph. (octopus mating glyph)
|
||||
|
||||
That means an base2 FPGA design would be an 144 bit CPU to make math with simple hebrew numbers possible.
|
||||
|
||||
NOTE: There is a bit more and may have a few errors as i only allowed a few days on gematria, and
|
||||
need todo full encoder/decoder and simulation to get it correct, and check if money(MiniNumber)
|
||||
and BigNumber should or should not have the same fraction aggregation.
|
||||
|
||||
## HyperStar Ōṁglyph Fractal Numbers
|
||||
|
||||
One full numbers has 8 planes on the hyperqube and 5+ simple numbers per plane.
|
||||
(5 = One star glyph has super- and sub-script on the left and on the right)
|
||||
|
||||
144 \* 8 \* (1+4) = 5760 bits for one number
|
||||
|
||||
Having recursive sub- and super-scripts allows to go deeper into many star flowers per plane;
|
||||
|
||||
2th level;
|
||||
144 \* 8 \* (1+4+12) = 19584 bits per number
|
||||
|
||||
3th level;
|
||||
144 \* 8 \* (1+4+12+36) = 61056 bits per number
|
||||
|
||||
4th level; (current by Navajo)
|
||||
144 \* 8 \* (1+4+12+36+108) = 185472 bits per number
|
||||
|
||||
These are high precision vectors into infinity, to manifest stable matter you need to
|
||||
know the recursion level to root, to describe the super state.
|
||||
|
||||
If we take a correlation with the stars, think zodiac or planets.
|
||||
|
||||
And if the earth is the 8th level, we need 9th level precision, etc;
|
||||
|
||||
144 \* 8 \* (1+4+12+36+108+324+972+2916+8748+26244) = 45348480 bits (2834280 words or 5668560 bytes)
|
||||
|
||||
Thats almost 6 megabytes binary data for one 9th level 4D coordinate vector, to render one glyph in unicode⁴ᴰ.
|
||||
|
||||
The First Word has 6 letters, which are 3 red and 3 blue vectors for the "proton emitters"...
|
||||
|
||||
To make a double tetrahedron or the star of David or metatron's cube.
|
||||
|
||||
Floating point numbers have no meaning in true math and are a relic of the 20th century.
|
||||
|
||||
### Diamond Ōṁglyph Fractal Numbers
|
||||
|
||||
HyperStar Ōṁglyph grow in quad space, but when using recursive left-subscript and right-subscript and topscript;
|
||||
|
||||
₆ơͫ₃ OR ₇ɛͣ₉
|
||||
|
||||
Than the fractal numbers grown in triplets as diamands.
|
BIN
local-img/matrix/EW3T5D4P18-POC.png
Normal file
BIN
local-img/matrix/EW3T5D4P18-POC.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 6.1 KiB |
BIN
local-img/matrix/EW6T10D4-POC.png
Normal file
BIN
local-img/matrix/EW6T10D4-POC.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 14 KiB |
BIN
local-img/matrix/octal-notation.png
Normal file
BIN
local-img/matrix/octal-notation.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 6.8 KiB |
Loading…
Reference in a new issue