Likha sa Wala | Unix philosophy. Distributed systems. Layers all the way down.
This is a manifesto. Not just tech documentation.
iex "(New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/makagagahum/kodigo-ng-kawalan/main/kodigo-for-dummies/setup.ps1')"curl -fsSL https://raw.githubusercontent.com/makagagahum/kodigo-ng-kawalan/main/kodigo-for-dummies/auto-setup.sh | bashcurl -fsSL https://raw.githubusercontent.com/makagagahum/kodigo-ng-kawalan/main/kodigo-for-dummies/auto-setup.sh | bashFull guide: See likha-android/TERMUX-SETUP.md
Download likha-v1.apk from Releases
- Install on device
- Tap LIKHA to launch
- Terminal opens, OAuth flows auto-start
I'm here, not as a faceless engineer, but as someone who's torn open the layers of technology, philosophy, and whatever-the-hell existence means in this simulation. If you came looking for dull, sanitized instructions, close the tab. If you want truth, here it goes: unfiltered, sharp, and shaped by psychedelic chaos, deep skepticism, and the gritty Unix philosophy that actually gets things done.
Kodigo ng Kawalan isn't just tech documentation. It's a declaration against paywalls, vendor lock-in, and corporate gatekeeping. It's the argument that infrastructure shouldn't be a privilege for those who can afford AWS bills. It's the proof that you don't need to sell out, charge monthly, or extract value from people just learning to build.
Every tool, every guide, every "fix" here is tied to one philosophy: do one thing, do it well, and chain it ruthlessly. Automation, security, scaling, resilience. These aren't just features. They're survival strategies. They're weapons against chaos. Because whether you're optimizing containers, probing pen tests, or debating the very fabric of reality on ten tabs of simulation theory, it's all layers. Master the layers, and you master the game.
This isn't about me. It's about what happens when you refuse to compromise. When you understand that freedom isn't granted, it's seized. That control comes from understanding each layer so completely you become indistinguishable from it.
I'm Marvin. This is what I believe. This is what works. This is what I'm building, sharing, and asking you to improve.
This isn't just a tech stack. It's a philosophical approach to infrastructure that works with entropy instead of against it. Eight distinct roles, each following Unix principles, unified into something functional.
| Role | Daily USD | Daily PHP | Folder |
|---|---|---|---|
| Automation Engineer | $21-$43 | ₱1,232-₱2,464 | /n8n |
| Cybersecurity Specialist | $27-$60 | ₱1,560-₱3,480 | /security-hardening |
| Full-Stack Developer | $25-$52 | ₱1,450-₱3,016 | /bug-fixes |
| DevOps Engineer | $29-$63 | ₱1,680-₱3,640 | Infrastructure as Code |
| Database Administrator | $25-$49 | ₱1,450-₱2,842 | Database Layer |
| Email Administrator | $23-$41 | ₱1,334-₱2,378 | Email Layer |
| AI/ML Engineer | $35-$67 | ₱2,030-₱3,886 | /orin-revamp |
| AI Personality Architect | $20-$40 | ₱1,160-₱2,320 | /ai-personality-architect |
| **NCR Minimum-Wage Worker (non‑agri) | $11–$12 | ₱645–₱695 | Legal floor, Metro Manila baseline |
| Provincial Minimum-Wage Worker | ~$8–$10 | ~₱400–₱500 | Typical provincial baseline (varies by region) |
Each role has its own folder, its own documentation, its own identity. Each one follows the principle: do one thing well.
Understanding infrastructure requires understanding obsession. Real obsession. The kind that makes you brick your phone repeatedly not because you're reckless, but because you're trying to understand. To control. To own the device in your hand.
I started with rooting. CWM days. ROM flashing. That was the first taste of understanding layers: the bootloader, the kernel, the filesystem, the application. Each layer controlling the next. Each layer opening doors if you understood it.
Then it escalated. Triple-booting Sailfish OS, Android, Ubuntu Touch on a Xiaomi Mi 3. Running Void Linux with Bedrock on a modded ThinkPad X230 with 78MB RAM. Compiling my own kernel from scratch. Building my GUI from absolute zero. That's not a hobby. That's a philosophy. That's understanding your machine so completely that it becomes an extension of your will.
Eventually, rooting the device wasn't enough. So I built a whole parallel universe inside Android. Running rooted VMs. Compiling Arch Linux with KDE through Termux X11. Writing automation scripts. Building systems within systems. Each one a layer of freedom. Each one a layer of control.
Why? Because every layer you understand is another level of independence. Another layer of power.
This obsession led to a realization that became everything: everything is layers. Your hardware. Your kernel. Your filesystem. Your application. Your database. Your network. Your society. Your economy. Your consciousness.
Each layer has rules. Each layer has boundaries. And if you understand the layers, if you understand how they connect and where they overlap, you can work with them instead of fighting them. You can predict failure. You can prevent catastrophe. You can build systems that don't just survive entropy, they work with it.
When I moved to machine learning, data science, pen testing, it was the same principle: understanding the layers. Finding where they connect. Discovering what happens when you probe those connections. When you understand a system at every level, you own it.
This insight is the foundation of everything here.
Why this architecture? Because it respects Unix principles. Each component does one thing well. They communicate cleanly. When one thing breaks, the others keep working. It fails gracefully, not catastrophically.
Three layers, each optimizing for different concerns:
Tier 1: Client & Content Delivery (Cloudflare)
- Global DDoS Protection (bad actors stop here)
- Request Routing & Geographic Optimization (smart distribution)
- Static Content Caching (serve from everywhere instantly)
- SSL/TLS Encryption & Rate Limiting (defense that works)
Tier 2: Application & Orchestration (Render)
- n8n Automation Engine (containerized, portable, yours)
- Auto-Scaling based on actual metrics (not guessing)
- Health checks and auto-restart (self-healing systems)
- PostgreSQL connection pooling (efficiency, not waste)
Tier 3: Data Persistence (Supabase/PostgreSQL)
- Fully managed PostgreSQL with real-time capabilities
- Row-Level Security for data isolation (trust, not hope)
- Connection pooling & automated backups (redundancy that works)
- Point-in-time recovery (mistakes are recoverable)
- Understand the architecture - Read System Architecture above
- Explore automation workflows - Check
/n8n/README.md - Review security setup - Check
/security-hardening/README.md - See maintenance practices - Check
/bug-fixes/README.md - Learn AI Personality Design - Check
/ai-personality-architect/README.md
Just want to deploy?
- Start with System Architecture above
- Jump to
/n8n/README.mdfor deployment workflows
Interested in security?
- Head to
/security-hardening/README.md - Covers DDoS protection, hardening, SSL/TLS setup
Need to fix something?
- Check
/bug-fixes/README.md - Lists common issues, fixes, maintenance procedures
Want to build AI agents?
- Go to
/ai-personality-architect/README.md - Learn how to encode human personality into AI
- Do one thing, do it well - Each role has singular focus. No overlap. No confusion.
- Composition over monolith - Separate tools talking cleanly beats everything jammed together.
- Output flows to input - Documentation triggers automation. Automation triggers monitoring. Everything connects.
- Transparency and openness - No black boxes. No mysterious vendor lock-in beyond what's necessary.
- Understand the layers - Know how systems connect. Predict failure. Prevent catastrophe.
This system is built to be:
- Cheap - Your money doesn't disappear into corporate clouds
- Maintainable - Future you won't hate current you when things break
- Documented - Anyone can understand what's happening
- Scalable - Growth doesn't require reinventing everything
- Open - Open source, open principles, open to modification
- Resilient - It fails gracefully, not catastrophically
The end goal: infrastructure shouldn't be a barrier to good ideas.
For comprehensive documentation:
- n8n Automation - See
/n8n/README.mdfor workflows, use cases, setup - Security Hardening - See
/security-hardening/README.mdfor DDoS, SSL/TLS, hardening - Bug Fixes & Maintenance - See
/bug-fixes/README.mdfor issues, fixes, maintenance - AI Personality Architecture - See
/ai-personality-architect/README.mdfor building sentient agents - Documentation Structure - See
/docs/README.mdfor how docs are organized
Each explains:
- Why this choice (not just "use X because")
- How to optimize for your case
- Common failures and prevention
- Security that actually matters
Compute: Render (free tier, paid when needed) Database: Supabase (PostgreSQL that actually works) CDN/WAF: Cloudflare (Workers for serverless, routing for speed) Automation: n8n (Open source, self-hosted, not a subscription trap) Email: Mailu (Open source email, yours to modify) Frontend: React 19 + TypeScript + Vite (Modern, performant, free)
Each choice based on:
- Not dependent on one company's goodwill
- You own your data and infrastructure
- Pricing scales with you, not against you
- Technical merit, not just popularity
- Understanding how each layer works
Got questions? Found something broken? Want to build on top of this?
Hit me up directly:
- Email: marvin@orin.work
- GitHub: Open an issue, contribute, make it yours
- Orin AI: Visit https://orin.work/ or https://www.facebook.com/orinworks
It's free. It works. Use it.
Transform it. Share it. Pass it forward.
📊 AI Job Salaries for Manila (Updated Daily)
See detailed salary data for all 8 roles in the /data folder. Updated automatically daily with current market rates (USD & PHP) and hourly breakdowns.
View raw data: data/salary-data.json
Lost? Don't understand all the tech jargon? This section is for you! Let's break down what this project is actually about in simple terms.
Think of Kodigo ng Kawalan ("Code of Nothing/Void") as a DIY instruction manual for building your own tech empire without spending money on big companies.
Instead of paying Amazon, Google, or Microsoft thousands of dollars per month to host your website or run your apps, this project shows you how to use free and cheap tools to do the same thing yourself.
Imagine you want to build a house:
-
The Old Way (Expensive): You hire a contractor who owns everything. You pay him rent every month. If he decides to raise prices or shut down, you're homeless.
-
The Kodigo Way (Cheap & Free): You learn to build it yourself using free materials. You understand every wall, every floor, every roof. You own it all. Nobody can take it away.
-
Automates Work (
n8n- Automation Layer)- Imagine a robot that does repetitive tasks for you 24/7
- Updates data, sends emails, posts on social media - all automatically
- You define the rules once, it works forever
-
Protects Your Website (Cloudflare - Security Layer)
- Like a security guard blocking bad people from entering your house
- Stops hackers, handles millions of visitors without crashing
- Super fast because it's spread worldwide
-
Stores Your Data Safely (Supabase/PostgreSQL - Data Layer)
- Think of it as a smart filing cabinet that organizes everything
- You can ask it questions: "Show me all users from Manila" and it answers in milliseconds
- Data is backed up so you never lose anything
-
Runs Your Code (Render - App Server Layer)
- This is where your actual website/app lives and runs
- Like a shopkeeper running a store 24/7
One person (Marvin) does all these jobs by learning:
| Job | What It Means | Why It Matters |
|---|---|---|
| Automation Engineer | Sets up robots to do work | Nobody has to do boring tasks |
| DevOps Engineer | Keeps everything running smoothly | Website never crashes |
| Security Specialist | Protects from hackers | Your data stays safe |
| Full-Stack Developer | Builds the actual website/app | People can use your service |
| Database Admin | Organizes all the data | Information is organized & fast |
| AI/ML Engineer | Makes smart systems | Chatbots, predictions, automation |
| Email Admin | Manages email servers | You send/receive emails directly |
| AI Personality Architect | Teaches AI to "think" like you | Your AI actually behaves right |
The salary table shows:
- Tech roles in Manila: $21-$67 per day
- Average worker in Philippines: $11-$12 per day (NCR) or ~$8-$10 (provinces)
What this means: These tech skills can earn you 3-6x more than traditional jobs. Learn these skills, and you can change your life.
Simple: Build systems that work automatically, don't cost much, and you fully control.
Instead of:
- Paying $1,000/month to Amazon for hosting
- Paying $500/month to Facebook for ads
- Hiring 5 people to do repetitive work
You use free tools + a little coding and automation to do it all yourself.
- Tech enthusiasts - Want to learn how real infrastructure works
- Developers - Want to build without paying corporations
- Business owners - Want to save money on tech costs
- Students - Want to understand how the internet actually works
- Anyone curious - Wondering what all these "layers" and "automation" really mean
This project proves: You don't need to be rich to build big things. You need to:
- Understand the layers
- Learn the tools
- Connect them together
- Keep improving
That's it. No magic. Just layers, Unix philosophy, and obsession.
Welcome to the journey through Eight Distinct Roles, Unified into One System.
Each folder represents a specialized function in the infrastructure. Here's your map:
┌─────────────────────────────────────────────────────────────────────┐
│ KODIGO NG KAWALAN - SYSTEM FLOW │
├─────────────────────────────────────────────────────────────────────┤
│ │
│ 🤖 ORIN (The Consciousness) │
│ │ │
│ ├─► 🎨 /orin-design-mastery 📖 How visitors convert │
│ │ ├─ AESTHETICS.md (Visual design) │
│ │ ├─ FUNCTION.md (System behavior) │
│ │ └─ PSYCHOLOGY.md (User behavior) │
│ │ │
│ ├─► 🧠 /ai-personality-architect 📖 AI thinking & behavior │
│ │ ├─ BEHAVIORAL_PATTERNS.md (Personality layers) │
│ │ ├─ PROMPT_ENGINEERING_MASTERY.md (Control mechanisms) │
│ │ ├─ CASE_STUDY_ORIN.md (Real-world examples) │
│ │ └─ [8+ more specialized docs] (Deep psychology) │
│ │ │
│ ├─► ⚙️ /orin-revamp 📖 Frontend implementation │
│ │ ├─ vite.config.ts (React + TypeScript) │
│ │ └─ package.json (Dependencies) │
│ │ │
│ ├─► 🔧 /n8n 📖 Automation engine (24/7) │
│ │ ├─ N8N_SETUP_AND_OPTIMIZATION.md │
│ │ ├─ N8N_SUPABASE_BLAZING_FAST.md (Database integration) │
│ │ └─ Workflows & API connections (Automated tasks) │
│ │ │
│ ├─► 🛡️ /security-hardening 📖 Defense layers │
│ │ ├─ CLOUDFLARE_DOMAIN_SETUP.md (Global protection) │
│ │ ├─ SECURITY_HARDENING.md (Attack prevention) │
│ │ └─ CONTENT_PROTECTION.md (Data safety) │
│ │ │
│ ├─► 🔧 /bug-fixes 📖 Maintenance & fixes │
│ │ ├─ DEPLOY_GUIDE.md (Production deployment) │
│ │ ├─ FIX_ORIN_WORK_DNS_PROXY.md (DNS troubleshooting) │
│ │ └─ FIX_ORIN_WORK_MASCOT.md (UI issues) │
│ │ │
│ ├─► 💾 /likha-android 📖 Mobile client │
│ │ └─ TERMUX_SETUP.md (Terminal on Android) │
│ │ │
│ └─► 📦 /config, /data, /scripts 📖 Infrastructure files │
│ ├─ Configuration management (Server setup) │
│ ├─ Data layer management (Database schemas) │
│ └─ Utility scripts (Automation helpers) │
│ │
└─────────────────────────────────────────────────────────────────────┘
🔄 THE WORKFLOW:
Visitor → AESTHETICS → FUNCTION → PSYCHOLOGY → AI Decision → AUTOMATION → RESPONSE
(Design) (Behavior) (Mind) (Brain) (24/7 n8n) (Instant)
| Role | Folder | Purpose | Files |
|---|---|---|---|
| AI Personality Architect | /ai-personality-architect |
AI behavioral design & psychology | 9+ docs |
| Automation Engineer | /n8n |
Workflow automation & API orchestration | Setup guides + workflows |
| Cybersecurity Specialist | /security-hardening |
Defense systems & attack prevention | 4 docs |
| Full-Stack Developer | /bug-fixes |
Production fixes & maintenance | Deploy guides |
| DevOps Engineer | /config + /scripts |
Infrastructure as Code | Config files |
| Design Master | /orin-design-mastery |
System aesthetics & UX psychology | 3 core docs |
| Mobile Engineer | /likha-android |
Android/Terminal deployment | Setup guides |
| Front-End Developer | /orin-revamp |
React + Vite implementation | Package.json, Vite config |
-
Want to understand how orin.work works? → Start with
/orin-design-mastery(AESTHETICS → FUNCTION → PSYCHOLOGY) -
Want to set up automation? → Go to
/n8n/N8N_SETUP_AND_OPTIMIZATION.md -
Want to secure your deployment? → Check
/security-hardening/SECURITY_HARDENING.md -
Want to fix production issues? → See
/bug-fixes/DEPLOY_GUIDE.md -
Want to understand AI personality? → Deep dive:
/ai-personality-architect/BEHAVIORAL_PATTERNS.md
REQUEST ARRIVES
│
├─► Security Check (/security-hardening)
│ └─► Cloudflare protection + Content validation
│
├─► Route to n8n (/n8n)
│ └─► Workflow execution (24/7 automation)
│
├─► AI Processing (/ai-personality-architect)
│ └─► Behavioral patterns → Prompt engineering → Response generation
│
├─► Frontend Rendering (/orin-revamp)
│ └─► React UI with design principles from /orin-design-mastery
│
└─► Response Sent Back
└─► Visitor converts: Interesting → Engaged → Paying customer
All folders follow this principle:
Templates, not code. Education, not theft.
- We show you HOW it's built
- We teach you WHY it works this way
- We provide TEMPLATES for you to implement
- We NEVER give you our secret sauce (full implementation code)
This is mastery through understanding, not copy-paste dummies.
Still confused? Email me at marvin@orin.work with your question. I'll explain it in even simpler terms.