Core Concepts

ANT has a hierarchical structure adapted to be immediately implemented in the conventional tree structure.
However, due to it’s has a decentralized modular infrastructure, it follows a specific structural rules that ensures its proper functioning.
To understand this, we must first grasp the terms Levels, Nodes and Modules within this system;

Levels

The term “Levels” refers to the depth of the folder in relation to her root folder

Although we advise keeping 3 Levels, there may be more.
However, it is recommended not to have too many levels and to use them only in certain cases. Because it adds complexity to the system and can make it difficult to navigate.

Nodes

The term “Node” refers to each folder.

This system is structured in a way that each folder its conected and follow thier way/path.
Each node or “folder” have one or more in/out ways, Its being part of a module, and in some cases having a lifespan (existence).

Modules

The term “Module” refers to a grouping of nodes in relation to their level, It is a category.

It means that, regardless of their connections, nodes should maintain a hierarchical grouping and these itself consistent within the conventional Tree data structure.
This keeping a logical, consistent and easy to navigate, tho doesn’t take away their flexibility.

Lifespan

Some nodes may have a lifespan, such as a workboard or a temporal folder.
That means that these nodes are useful in a period of time and should be deleted after use.

Lifespan node Cycle:

1. Creation:
   Some nodes are created from templates presets for quickly join to storage.
   This ones must be immediately identifiable and their content inside does not always have to have a strict order.

2. Active Use:
   Commonly its used as a repository with a self-contained role, Although is constantly followed by the system itself aid with trackers or special marks.

3. Delivery:
   When the goal is done (e.g. finished the project), their content can become useless.

4. Review and Archive:
   Here the content is valued to know if it may be reused in the future:
   ● If the content is useful, it can be archived there or move another places.
   ● Else the content is deleted.

5. Death:
   Once it is considered obsolete, the node is removed from the system.