trpg/docs/justification/feature_justification.txt
austin f1b6a4f521
All checks were successful
studiorailgun/trpg/pipeline/head This commit looks good
sort docs
2025-01-01 14:19:54 -05:00

23 lines
1.0 KiB
Plaintext

Arguments justifying different features
Information Priority
Pieces of information have different priorities and should be handled accordingly.
Keep a 'hot' web of the most important parts of info that should immediately be searchable every frame.
This can link into 'colder' webs that store lower priority information.
Will have this with both relations and nodes in the web.
To justify for nodes, some people in your life are of higher importance than others to remember.
You don't keep all people you know immediately accessible in your brain.
To justify for relations, relations between specific numbers are thrown out almost immediately when done solving a math problem.
Layered webs
If you have a conversation about the color of a hat, you will not store the color of the hat in your immediately accessible brain long term.
This lets you not constantly scan a huge repertoire of information when you want to perform day-to-day tasks.
Thus, I want to create an information heirarchy to mimic this and make engineering potentially easier.