docs: read compensation guide

.github/COMPENSATION.md

@@ -0,0 +1,27 @@
+# Compensation Guide
+
+**Goal:** Reward impact, not titles or location. Pay based on merit—what you deliver independently.
+
+> Open roles: [holdex.io/c/jobs](https://holdex.io/c/jobs) | Mission: [holdex.io/about](https://holdex.io/about)
+
+## Core Rules
+1. **Clear incentives** — Same job, same level = same pay. More results = more rewards.
+2. **Simple framework** — Consistent rules for growth.
+
+## Levels & Core Skills
+
+| Level | Key Traits & Expectations | Team Culture | Goals | Problems & Solutions |
+|-------|---------------------------|--------------|-------|----------------------|
+| **Entry** | Student mindset: Bug-free. Execute tasks. Research. Learn fast. Communicate clearly. Take feedback. | Follow [principles](https://holdex.io/c/learn/principles) & [GitHub rules](https://holdex.io/c/learn/github-strategy). | Understand goals. | Solve, estimate, research, present. Help juniors. |
+| **Intermediate** | Confident executor: Solve complex problems. Lead small parts. Help Entry. Strong opinions. | Follow principles. Remind team. | Break into problems. Research solutions. | Identify real problems. Break down. Prioritize. Review juniors. |
+| **Lead** | Project owner: Run full projects. Delegate. Coach team. Align with business. Inspire. | Coach others. Lead in projects. | Set timelines. Ensure delivery. | Delegate. Distribute to best fit. |
+| **Partner** | Big-picture leader: Own multiple projects. Shape strategy. Say no when needed. Grow culture. | Improve rules/values. | Define business goals & priorities. | (All above + strategic input) |
+
+## Growth Path
+
+| Level | Focus |
+|-------|-------|
+| **Entry** | Learn → Execute → Ask |
+| **Intermediate** | Solve → Teach → Lead small |
+| **Lead** | Own → Delegate → Coach |
+| **Partner** | Strategize → Scale → Say No |

.github/CONTRIBUTING.md

@@ -77,7 +77,7 @@ Different problems may require different sets of skills.
 Whether it’s code, design, or marketing material, we expect a lean and clean solution from the contributor.
 
 > [!NOTE]
-> Solution is presented in GitHub as [Pull Requests (PR)](https://docs.github.com/en/pull-requests) in compliance with [PR Requirements](#pr-requirements).
+> Solution is presented in GitHub as a [Pull Request (PR)](https://docs.github.com/en/pull-requests) in compliance with [PR Requirements](#pr-requirements).
 
 ### Referencing
 
@@ -151,9 +151,10 @@ The required checks are as follows:
 
 ## Drafting
 
-When start working on a Problem, you must open a [draft PR](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests) right away. Do not mark PR as "ready to review" unless you are confident it is ready.
-
-When creating a PR, you must [link it](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) to the corresponding Problem (issue).
+When starting to work on a Problem, you must:
+1. Open a [draft PR](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests) right away. Do not mark PR as "ready to review" unless you are confident it is ready.
+2. [Link opened PR](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) to the corresponding Problem (issue).
+3. Before marking your PR as ready for review, assign **at least one reviewer** (team or individual). Do not merge without approved review.
 
 ### Design PRs
 

.github/PRINCIPLES.md

@@ -0,0 +1,44 @@
+# Our Principles
+
+**We build great things together—fast, smart, and with full ownership.**
+
+## The 6 Rules We Live By
+
+1. **Start with the Goal**  
+   Keep the big picture. Break it into clear problems. Solve one at a time.
+
+2. **Own It Like a Founder**  
+   No one assigns tasks. You spot problems, claim them, and deliver results.
+
+3. **Ship Daily, Small & Often**  
+   No task >4 hours. Finish, push, move on. Momentum beats perfection.
+
+4. **Respect Time—Yours & Others**  
+   One team sync/week. Work async. No meetings unless needed.
+
+5. **Wear Many Hats**  
+   Code, design, test, write, explore. We grow by doing.
+
+6. **Figure It Out**  
+   Research. Read. Ask. Learn fast. No waiting for instructions.
+
+---
+
+## Do This | Not That
+
+| ✅ **Do** | ❌ **Don’t** |
+|----------|-------------|
+| Solve what moves the goal | Work on low-value tasks |
+| Own it end-to-end | Pass the buck |
+| Test your work | Expect others to QA |
+| Leave clear updates | Vanish without trace |
+
+---
+
+## ⏰ Core Hours  
+**2–6 PM HKT** — Be online. Rest is flexible.
+
+---
+
+**Be bold. Be fast. Be kind.**  
+That’s how we win.

README.md

@@ -1,14 +1,15 @@
 # Developer Guidelines
-Welcome to the Developer Guidelines!
+Welcome to our Developer Guidelines!
 Your journey to shape the future starts here.
 
 ## For Developers
 
 _Developers_ are everyone creating value—business developers, designers, engineers, marketers, and beyond. We build businesses, products, partnerships, customer relationships, processes, and delivery methods, crafting the future we envision.
 
 Align with:
+- [Principles](./.github/PRINCIPLES.md)
 - [Contributing Guidelines](./.github/CONTRIBUTING.md)
-- [DOs & DON'T](.github/DONTS.md)
 - [Sick Leave Policy](./.github/LEAVE_POLICY.md)
+- [Compensation Guide](./.github/COMPENSATION.md)
 
 Subscribe to repository notifications to stay updated with frequent fixes and improvements.