PROBLEM
We have to start somewhere.
SOLUTION
The Thing is MTREES simple boilerplate for making anything you want on any device. Blazingly fast with a simple storage system, templating and data management with unlimited flexibility, try the Seed Spec platform today, because its not a spec it is a modular design system mentality. Not approved for public release.intangibles
The Node Navigator is the recursive context cursor at the heart of The Thing, responsible for traversing the node tree from any entry point downward through its children, maintaining positional context at each level so the renderer knows what it is looking at, what it came from, and how deep it has gone. It does not walk the tree once and cache the result. It walks the tree on demand, following the children arrays from node to node, loading each JSON file as it goes, and building a live context object that the rest of the platform can interrogate at any depth. The recursive nature is the feature: a node at any level can contain anything, and the Navigator does not need to know what is down there before it goes. It finds out by going. This is either elegant or terrifying depending on the size of the tree and the time of day. Currently being fully built.
InspectThe Template Renderer is the class responsible for taking a node context object from the Node Navigator and turning it into rendered HTML output using the appropriate template file for that node type. It maps node type to template, passes the node data as available variables, and returns the compiled output. The renderer is intentionally thin — it does not make decisions about content, it does not transform data, it just binds the node to its template and steps back. The template does the visual work. The renderer does the binding. This separation is the thing that makes the whole system swappable: change the template, the output changes; change the data, the output changes; the renderer itself stays the same and does not care. Currently needs to be cleaned up a bit.
InspectGlobulous Maximus is the full-tree recursive loader that attempts to resolve and return the entire node universe as a single deeply nested data structure in one call, walking every branch, loading every child, following every reference, and assembling the complete picture of everything The Thing knows about from the root node down to the last atomic component at the bottom of the deepest branch. It is the nuclear option of data retrieval. It is what you call when you need the whole tree and are prepared to wait for it and not entirely sure what you will do with it when it arrives. Whether it will perform acceptably at universe scale is an open question the documentation describes as a known risk and the engineering notes describe as a known risk with a specific emoji next to it. Does not exist yet. Might not. The name however is perfect and was never going to be anything else.
InspectA path resolver that maps an incoming request to the correct handler or destination based on defined rules. No one quite knows where the cat videos go, we just know it says error 502.
Inspectcomponents
No confirmed uses. Automagically instantiated at every recursive loop.
InspectInputs
Outputs
TREE
-
van()