New Entity OS™ is the fully-integrated result of all New Entity Operations™ technology projects. New Entity Operations LLC was founded in 2013 by Ryan McKenna and in 2019 the company was incorporated in Delaware. Historically, New Entity Operations Inc. has developed novelty software libraries in the RTC and new media segments while also releasing a variety of draft-stage technology-standards within the "data interchange" space (EntityScript™).
Most of the standards being developed are backed up by innovative software implementations beyond what you could spin up in a few hours with a AI assistant. These are deeply integrated systems with robust capabilities built upon actual software stacks available in the real world or when required - have been custom built to satisfy a broad or niche computing objective. These objectives span across all of the segments of the computing experience and there is now a working version of the prototype OS. The focus from the beginning of the project has been on providing robust tool sets that are open-natured in automating data storage and retrieval in tightly-mapped local-first systems. This means creating computing fabrics that aren't flimsy, or closed, but are more big-picture, interoperable, and interchangable. For our current prototype this was achieved by utilizing many layers to meet our desired objectives and by later auditing the system and writing the entire system-level documentation out at the same time. The system-level documentation is rough, but complete now.
OS Objective
Create a seamless and transparent base-line system for local-first AI
- Must be based on an open standard kernel
- Must provide an open standard operations enclave for data operations
- Must provide open standard driver support
- Must be documented
- Must provide use-case AI within a local-first environment that reaches industry standards of entry-level publicly available proprietary models
- Must be able to be self-scaled into evolving data-interchange needs, remaing interchangeable with widely used formats such as json and xml.
- Must be politically unswayed from the core system principles above.
Provide an integrated and complete experience for both the most advanced users and entry levels without appealing too much to either one category
- Complex features must be available to power users
- Starting interfaces and drivers must be enabling for everyday users
- Must integrate into current gaming, streaming, media, and rights-management landscape
- Must provide basic and complex audio-mapping possiblities to preserve sound fidelity as a key component of the system
- Features must adhere to the least privileged mentality being governed by layered security approaches accessible to power users and completely unknown by the everyday user
- Must provide basic anonymity features such as unhooked DNS, easy proxy implementation, and simple network management
- Must provide 1 clear and undisputed system control framework on top of the systemctl baseline system integrations. It must also provide an environment that allows for the seemless execution of a variety of user-defined yet common tasks, such as backups and gaining the required runtime hooks to perform a majority of the creative tasks the end-user may wish to participate in within the general-consumer market.