Maker.sh

Maker.sh introduces a novel build and automation protocol designed to streamline the rapidly evolving landscape of AI-assisted software development. The challenge lies in managing multi-file project setups and ensuring system security when generating complex, multi-modular applications. To address this, maker.sh combines the flexibility of shell scripting with modern package manager disciplines, creating an architectural framework known as MakerChain, alongside MakerCompiler as the executing engine.

The protocol is built upon a core philosophy centered around a Bash script known as maker.sh. Unlike traditional setup scripts, maker.sh employs embedded comment metadata tags to transform it into a declarative manifest readable by both humans and machines, including compilers and AI agents. This feature enhances backward compatibility, as standard Bash interpreters entirely ignore these lines.

One of the key elements of maker.sh is its file generation mechanism using Heredoc-Driven syntax. This approach avoids errors caused by quote or escape-character issues commonly found in multi-line code blocks. Instead, it uses cat EOF target_file to generate heredoc-driven files, ensuring smooth execution.

Maker.sh syntax and rules consist of logically isolated blocks delineated by #part-start and #part-finish tags. These tags serve various purposes, including importing external maker.sh files, defining target files, specifying file nature, setting distribution restrictions, outlining software and hardware requirements, managing temporary environment variables, and defining automation hooks.

For large-scale projects, MakerChain enables sequential compilation of specified target blocks. The MakerChain engine connects and executes these targets sequentially or concurrently, similar to how GCC links and compiles C/C++ source files. Execution syntax involves the maker build -chain command followed by comma-delimited module identifiers.

MakerCompiler, the executing engine, translates maker.sh files into structured, secure system actions through four core layers. The State-Machine Parser reads the file top-to-bottom as a state machine, ensuring robust parsing regardless of block order. This parser captures all instructions until reaching #part-finish, enabling localized debugging.

The Static Firewall, or Built-in Antivirus Layer, protects against destructive commands generated by AI models. It performs static analysis before executing any line, blocking critical commands targeting root directories or attempting system formatting. The Hardware and Environment Validation layer parses resource blocks {} to verify available RAM, CPU thread counts, and software dependencies, triggering alerts or sandbox prompts if missing resources are found.

Lastly, MakerCompiler presents an execution summary to the user, requiring explicit consent before writing to disk. The command-line interface (CLI) provides standardized commands for complete process governance, including maker init for generating boilerplate templates, maker build for executing the build process, maker build -chain for sequential compilation, maker build -a for recursive scanning, maker build --dry-run for simulating the build workflow, and maker build --debug for displaying line-by-line parser tracking and security logs.