Direct computing, native compatibility and user-controlled technology.
DOS64 is a modern operating-system project built around a simple proposition: progress should not require abandoning compatibility, direct control or understandable computing.
DOS64 combines a 64-bit multitasking architecture with native legacy compatibility, modular system design, cross-platform development and knowledge-aware computing.
DOS64 is not an attempt to reproduce the limitations of early DOS systems. The name identifies a direct, predictable and compatible operating-system interface carried forward into a modern 64-bit, multitasking environment.
DOS64 is designed to provide DOS-compatible interrupt services directly to applications and users even while the system is multitasking. Compatibility interfaces are intended to remain immediate and deterministic rather than being treated merely as slow emulation layers added on top of an unrelated operating-system architecture.
Legacy compatibility is a native architectural objective. Older programs, command conventions, file-handling expectations and established application workflows should remain usable wherever technically practical without forcing users to maintain an obsolete operating system solely to preserve access to their software and information.
DOS64 uses a case-insensitive file system and command interface by default so traditional DOS-style commands, batch files and applications can refer to files without regard to capitalization. Unix-style case-sensitive behavior remains available when a particular application, development environment or interoperability requirement needs it.
DOS64 development is guided by four architectural principles: modularity, replaceability, security and expandability.
Operating-system functions should be divided into understandable components with explicit interfaces rather than accumulated into an inseparable body of dependencies.
A module, driver, service or subsystem should be replaceable without requiring the entire operating system or application environment to be redesigned. Replaceability protects users from technological dead ends and allows superior implementations to be introduced incrementally.
Security should be architectural, visible and controllable. DOS64 seeks to minimize unnecessary privilege, hidden communication paths, opaque dependency chains and externally imposed services while allowing users and organizations to determine which functions their systems expose.
The system should permit new hardware, new services, new application models and new forms of computational intelligence to be added without abandoning existing programs or rebuilding the operating environment around every new technology.
DOS64 is intended to follow a governance model different from both vendor-controlled operating systems and contributor-controlled industry foundations. Its technical direction will be privately managed so that companies whose commercial interests depend upon operating-system complexity, platform tying, mandatory services or protection mechanisms do not obtain governance authority merely by contributing code, money or personnel.
The purpose is not to exclude outside technology. DOS64 can adopt standards, interfaces and useful contributions from anywhere. The distinction is that industry participation does not confer control over the operating system's objectives.
Governance is therefore centered on the requirements of the people and organizations that actually use computers: independence, longevity, compatibility, security, local control, understandable operation and freedom to replace one technology with another. Those objectives are frequently the opposite of the economic incentives confronting dominant technology corporations whose extraordinary market valuations depend upon preserving proprietary platforms, recurring service revenues, controlled ecosystems, technological dependencies and barriers to replacement. The problem extends beyond proprietary operating systems. Much of the infrastructure commonly described as "open" is developed, financed and governed with extensive participation by the same technology industry whose products an independent operating system would compete against. Corporate employment of developers, corporate sponsorship, foundation membership, standards participation and board representation create an unavoidable question of conflicting incentives. DOS64 begins with a different premise: an operating system intended to challenge industry dependency cannot be governed by the industry whose dependencies it is intended to eliminate. This distinction is fundamental. DOS64 may use technology developed by Intel, Microsoft, Linux developers, universities, standards organizations or any other source. It may remain compatible with their products and may cooperate technically with them. But contribution of technology will not confer authority over DOS64 governance. The economic consequence of the existing structure deserves public examination. Decades of open-source development have produced an extraordinary volume of operating-system technology, particularly around Linux, yet that technological abundance has not produced a comparable proliferation of independent mass-market desktop operating systems competing directly for ordinary consumers and small businesses. The end-user market remains concentrated around a very small number of dominant platforms. DOS64 contends that this outcome cannot be understood solely as a technical failure. Where the employers, sponsors, platform providers, development-tool providers and major commercial participants in an ostensibly independent software ecosystem also derive enormous economic value from the continuation of the existing platform structure, an inherent and unavoidable conflict of interest exists. That conflict and the technological mechanisms through which DOS64 contends competition has been restrained is also the subject of ongoing federal litigation brought by the founder of DOS64. The litigation is not presented here as proof that every allegation has already been established. It is the public judicial forum in which those allegations, supporting evidence and competing explanations can be examined.Effective governance begins by reducing the conditions that make policing, insurance, litigation, and centralized security intervention continuously necessary. Modern computing and Internet architectures often externalize security risk to users while concentrating technical control in privileged software, platform vendors, network intermediaries, and security providers. Vulnerabilities, unrestricted privileged execution, opaque communications, and destination-side attack mitigation increase both the cost of protection and the economic value of services that manage the resulting risk. DOS64 takes the opposite architectural approach: prevent unauthorized capability at its source, identify causal paths, contain malicious communications near their origin, and make security an inherent property of the system rather than a product purchased after failure. As preventable risk is removed architecturally, the need for insurance, policing, litigation, centralized cybersecurity services, and other institutions devoted primarily to managing that risk can correspondingly decline.
DOS64 exists in part to demonstrate the alternative: an operating system whose governing question is not "What protects the existing industry?" but "What gives the owner of the computer the greatest capability, independence, security and freedom of choice?"
DOS64 exists to introduce independent computing technologies, including low-power architectural intelligence and knowledge-aware systems, that extend and amplify both human intelligence and current language-model AI.
AI is a tool. Like every useful tool, its purpose should be to extend the capabilities of the individual using it. DOS64 therefore develops AI as an extension of human knowledge, memory, reasoning, creativity, and action, while giving language models persistent objectification, deterministic knowledge, causal relationships, and architectural capabilities that linguistic processing alone does not provide.
The project is designed around local control, compatibility, modularity, replaceability, security, and technological independence. These objectives can conflict with prevailing industry incentives favoring centralized services, recurring access fees, telemetry, platform dependency, and remote control because those models can increase continuing revenue and strengthen control over users and markets.
DOS64 takes the opposite direction: move intelligence and capability toward the user, reduce unnecessary dependence on centralized intermediaries, lower computational and energy cost where architectural processing can replace repeated computation, and make the computer an increasingly powerful extension of its owner's intelligence and agency.
DOS64 is intended to interoperate with prevalent computing environments—from Windows and Unix/Linux systems to mobile and Android environments—and to provide practical bridges between otherwise incompatible application and data ecosystems.
The development environment is intended to allow programmers to create and maintain software that can target multiple operating systems instead of forcing each application into an isolated toolchain and dependency universe.
Modern software development has accumulated layers of dependencies, DLLs, header files, framework versions, package managers and incompatible updates. DOS64 seeks to reduce that complexity through stable interfaces, modular components and new development technologies including knowledge-aware database and application-development systems.
DOS64 is intended to introduce knowledge-aware architecture as an operating environment in which information, objects, relationships, context and actions can be represented directly rather than existing only as disconnected files and application-specific data.
For AI systems, this architecture can complement current language models with deterministic object, relationship and action capabilities. For human users, it can provide transparent and immediate normalized access to information as part of an integrated knowledge system rather than forcing the user to search through independent applications, formats and storage locations.
DOS64 include FSP (FRED Service Protocol) which is positioned not merely as a replacement for conventional server service management such as Linux SystemD , but as a distributed runtime infrastructure for VARs, subscribers, and application providers.
Traditional service managers such as SystemD operate primarily within a single administrator-controlled host. FSP extends service management across multiple independent computers and servers, allowing services to register dynamically, remain available independently of individual login sessions, move between execution nodes, and be selected transparently according to availability, capability, workload, location, or policy.
Applications and forms may therefore execute on remote subscriber or provider systems while continuing to appear under the originating domain and user interface. This makes FSP both a service-management architecture and a transparent multi-server load-balancing fabric in which participating users and VARs can contribute computing resources without exposing the underlying routing or deployment complexity to the application user.