Future Work – STRVCT

Design ideas, architectural discussions, and potential future improvements.

Adding an async phase to the object initialization lifecycle.

Deferring object loading until first access, so large object graphs don't pay for what they don't touch.

Automatic async getter generation with promise caching and dependency-driven invalidation.

Expanding auto-generated JSON Schema coverage across slots, classes, and the domain model.

Formalizing the many undeclared interface contracts throughout the codebase.

Tile subclasses for presenting individual subnodes in specialized ways.

Layout strategies for presenting a node's subnodes.

Capabilities that the naked objects architecture makes possible at the framework level.

Validating and refining the framework's ARIA implementation across screen readers, devices, and applications.

Rearchitecting the navigation stack to support asynchronous loading at every level.

Long-term direction: replacing the current cloud storage backend with a native graph database.