Yokseekan

Boxstorage

Boxes are objects that denote a specific idea, specifically one that can be identified on its own and as an interlacing node between two or more “entities.” Boxes are entities, but entities are not boxes, because entities specify a broader range than that which “boxes” cannot circumscribe within its definition. So entities are a broader range; one can view the different entities as different types of boxes. But that is semantics. This is all semantics. The goal here is to concretize the idea of an “idea”, within something grounded, tangible, and measurable as objects.

This is the framework of “Boxstorage”.

If ideas exist within systems, then we can easily assume that systems are composed of ideas. This means that ideas are only as much as systems compose them so as to be (in all its parts, but not necessarily its emergent features and underlying emergent characteristics).

Imagine a dog, but not just any dog. Imagine a dog in a box. A dog in a box is confined within measurable square surfaces, that of the six faces—top, bottom, north, south, east, and west.

In Minecraft, there is a similar tendency toward how different armor pieces are denoted when it comes to their position within the armor slots—numbers, as seen in the following:

  • Head armor slot: 103

  • Chest armor slot: 102

  • Leg armor slot: 101

  • Feet armor slot: 100

  • Mainhand: 98

  • Offhand: 99

But ideas are more than just ID numbers, the same way boxes are not just ideas circumscribed. Instead, we can adjust our viewpoint to consider the folllowing whole:

  1. boxes as objects that can be defined as a specific idea, specifically one that can be identified on its own

  2. those specific ideas as interlacing nodes between two or more entities

  3. boxes as entities, but entities not as boxes.

  4. different entities as different types of boxes

  5. boxes as grounded, tangible, and measurable objects

  6. Boxstorage

  7. ideas existing within systems

  8. systems being composed of ideas

  9. ideas are only as much as systems compose them so as to be (in all its parts)

  10. emergent features and underlying emergent characteristics, which typify systems, as separate from “in all its parts” in the context of “ideas being only as much as systems compose them so as to be”

  11. similarity to Minecraft armor pieces differentiated by armor slot IDs

As soon as all of these ideas are well-considered, we can move on to the next stage.

Before that, let me first state that ideas are perpetual. At least, we can assume they are. This means that we’re rather focusing on everything else besides the impermanence of ideas (one that bypasses specifically the “man is not the same man and river is not the same river” notion), similar to the oceans of water we re-use and recycle it everyday within this earth.

Given the fullness of our discussion, the following prompts dare you to use what was talked about in more visceral scenarios:

  • If we can imagine then ideas as external constructions, then we can ameliorate any rough edge knowing that we are engaging with the abstract formation.

  • If we imagine then ideas as prominent figures, we can easily insert such ideas into varied frameworks and systems that require specific qualifications. The analogy of prominent figures can serve as a means to intensify themes of collaborative resilience across qualifications, professions, and specializations.

  • If we imagine the feeling of an idea, then we can assume its qualities, flavors, and distinct characteristics. We can define up to the essence, including creating and removing topological properties that essentialize the idea. Imagine a dog and removing what makes a dog, but retaining still the reserved framework of a dog as is needed to give a representation a physical body.

built with btw btw logo