███████╗ ██████╗  ██████╗ ██╗███████╗████████╗
██╔════╝██╔════╝ ██╔═══██╗██║██╔════╝╚══██╔══╝
█████╗  ██║  ███╗██║   ██║██║███████╗   ██║   
██╔══╝  ██║   ██║██║   ██║██║╚════██║   ██║   
███████╗╚██████╔╝╚██████╔╝██║███████║   ██║   
╚══════╝ ╚═════╝  ╚═════╝ ╚═╝╚══════╝   ╚═╝   

SYSTEMS > SENTENCES
OUTPUT > OPINION
EXECUTION > EXCUSES

Engineering with intent. Systems over noise. Execution over talk.

🧠 WHO AM I (NO MARKETING, ONLY SIGNAL)

Engineering with intent. Systems over noise. Execution over talk.

• Senior-level engineer by output, not by title
• Systems thinker. Constraint enforcer. Failure-mode hunter
• Obsessed with performance, clarity, determinism
• Allergic to:
  • buzzwords
  • cargo-cult frameworks
  • fake "impact"

If it can't be measured, it doesn't exist.

🛠️ TECH STACK (WEAPONS, NOT TOYS)

⚙️ Languages

📱 Mobile / UI

☁️ Backend / Infra

🧠 Engineering Mindset

⚡ REPO AUTONOMOUS SCORE

📊 STATS (RAW SIGNAL)

⏱ TIME ALLOCATION (REAL DATA)

Note: Replace YOUR_WAKATIME with your Wakatime username to enable time tracking stats.

🧩 COMPETITIVE PROGRAMMING

LeetCode

Codeforces

Note: Replace YOUR_LEETCODE and YOUR_CODEFORCES with your usernames to enable competitive programming stats.

🐍 ACTIVITY TRACE

⚔️ ENGINEERING DOCTRINE

1. Correctness is binary
If it sometimes works, it doesn't work.

2. Abstractions pay rent
If it reduces clarity or performance → delete it.

3. Benchmarks > beliefs
Every performance claim without numbers is fiction.

4. Defaults are hostile
Assume frameworks lie until proven otherwise.

5. Readability is a scaling strategy
Unreadable code is future downtime.

6. Refactors are not optional
Entropy is real. Fight it or drown.

7. Automation over trust
Humans forget. Pipelines don't.

8. Failure modes are requirements
If you can't name how it breaks, you don't understand it.

9. Tests are documentation
If tests don't exist, the behavior is undefined.

10. Performance is a feature
Slow code is broken code.

🔥 OPERATING PRINCIPLES

• Readability beats cleverness
• APIs are contracts, not suggestions
• Every abstraction pays rent
• Defaults are usually wrong
• Speed without correctness is failure
• Complexity must be justified with benchmarks
• Documentation is code that doesn't compile

🧪 CURRENT FOCUS

• High-performance Android architecture
• Compose Multiplatform at scale
• Build systems & CI hardening
• Prompt engineering & agent workflows
• Removing human error via automation
• Systems that fail gracefully

🚫 HARD NO LIST

❌ Tutorials without production relevance
❌ Magic libraries with no benchmarks
❌ "Trust me bro" engineering
❌ Passive code reviews
❌ Fragile systems
❌ Code without failure modes documented ❌ Performance claims without numbers

🧪 FAILURE CASE HALL OF FAME

Broken systems taught more than successful demos ever did.

How This Repo Will Fail

graph TD
A[Traffic Spike] --> B[Cache Saturation]
B --> C[OOM]
C --> D[Process Kill]
D --> E[Cold Restart]
E --> F[Latency Spike]
F --> G[User Impact]
G --> H[Circuit Breaker]
H --> I[Graceful Degradation]

🧠 DESIGN AUTOPSY

Every system here ships with a death certificate in advance.

Template

Every serious repo must contain this section.

Problem

What exact pain exists. No narrative.

Constraints

• Latency:
• Memory:
• Scale:
• Platform:

Chosen Architecture

Why this. Why not alternatives.

Trade-offs Accepted

What is worse by design. Intentionally.

Failure Modes

• What breaks first
• Under what load
• How it degrades

Kill Criteria

Exact conditions under which this system must be rewritten.

🧪 BENCHMARKS (REAL NUMBERS)

Enforcement Rule: No performance claims without benchmarks. CI enforces this.

🔐 SECURITY POSTURE

If it isn't threat-modeled, it isn't secure.

Threat Model

• Attacker: external
• Data at risk: tokens, PII
• Surface: API, local storage, logs

Protections

• TLS enforced
• Secrets rotated
• Input validation mandatory
• No plaintext storage

Explicit Non-Goals

• Nation-state defense
• Zero-day immunity

Disclosure Policy

Responsible disclosure only.
Unverified reports ignored.

📐 QUALITY GATE

A repo is NOT MERGEABLE if:

• ❌ No README with architecture
• ❌ No benchmarks for perf claims
• ❌ No tests for core logic
• ❌ No failure modes documented
• ❌ No CI enforcement
• ❌ No code review approval
• ❌ No security scan passed

Gate Status:

• ✅ Architecture documented
• ✅ Benchmarks present
• ✅ Tests mandatory
• ✅ Failure modes defined
• ✅ CI enforced
• ✅ Security scanned

If it passes → ship
If it fails → rewrite or delete

🧨 PHILOSOPHY (UNFILTERED)

Comfort is technical debt.
Simplicity is earned, not declared.
Systems don't fail — assumptions do.
Code without tests is legacy code.
Performance is a feature, not an afterthought.

📫 CONTACT (ONLY IF SERIOUS)

🧱 ANTI-COPYPASTE NOTICE

Learn freely. Clone nothing.

See LICENSE-EXTENSION.md for anti-copypaste clause.

This profile is a signal weapon. Use it wisely.

⚠️ PUBLIC TECH-DEBT HEATMAP (BRUTALLY HONEST)

Rule (Explicit):

🔴🔴🔴 = rewrite scheduled
🔴🔴 = refactor pending
🟡 = tolerable
🟢 = clean

This prevents bullshit excuses.

🤖 AI REVIEWER — ACTIVE

This repository assumes every PR is wrong until proven otherwise.

Psychological effect: Contributors slow down. Quality goes up.

See PR Template for review criteria.

📊 LIVE METRICS DASHBOARD

Velocity

Quality

Stability

Performance

⚠️ LEGAL NOTICE

See LICENSE-EXTENSION.md for anti-copypaste clause.

This profile is a signal weapon. Use it wisely.

🎯 VISUAL SUMMARY

What This Profile Signals

✅ Engineering Excellence - Not just code, but systems thinking
✅ Zero Tolerance - For mediocrity, excuses, and hand-waving
✅ Measured Impact - Every claim backed by data
✅ Failure Literacy - Learning from mistakes, not hiding them
✅ Automation First - CI/CD, testing, quality gates enforced
✅ Security Minded - Threat modeling, not checklist compliance
✅ Production Ready - Benchmarks, monitoring, observability

What This Profile Filters

❌ Junior Engineers - Can't handle the standards
❌ Buzzword Users - No substance behind claims
❌ Copy-Paste Artists - Anti-copypaste clause active
❌ Hand-Wavers - Performance claims need numbers
❌ Excuse Makers - Tech debt heatmap exposes reality

🚀 DEPLOYMENT STATUS

Last Updated: Auto-updated via GitHub Actions
Workflow Status: ✅ All workflows operational
Profile Grade: A (Weaponized Edition)

🎯 PROFILE METRICS EXPANDED