chore: init

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "snyk.advanced.autoSelectOrganization": true
+}

README.md

@@ -1,2 +1,316 @@
 # central-de-estudo
 
+```txt
+what is a issue on repository?
+```
+
+In a software repository (like on GitHub or GitLab), an **issue** is a tracked item that represents:
+
+* 🐛 a bug
+* ✨ a feature request
+* 📌 a task
+* ❓ a question
+* 📖 a discussion about improvement
+
+Think of an issue as a **structured to-do item with context and history**.
+
+---
+
+## Where you see issues
+
+For example, on:
+
+* GitHub
+* GitLab
+
+Every repository has an **Issues tab**.
+
+---
+
+## What an Issue Usually Contains
+
+A typical issue includes:
+
+* **Title** → short summary
+* **Description** → detailed explanation
+* **Author** → who created it
+* **Comments** → discussion thread
+* **Labels** → categories like `bug`, `enhancement`, `urgent`
+* **Assignee** → who is responsible
+* **Status** → open or closed
+
+---
+
+## Example
+
+Imagine you have a project:
+
+> 🗂️ todo-app
+
+You find a problem:
+
+> “When clicking Save, the app crashes.”
+
+You create an issue:
+
+**Title:** App crashes when clicking Save
+**Description:** Steps to reproduce + expected behavior
+
+Now:
+
+* The problem is documented
+* Others can comment
+* Someone can be assigned
+* When fixed → the issue is closed
+
+---
+
+## Why Issues Are Important
+
+Issues help with:
+
+* 📋 Organizing work
+* 👥 Team collaboration
+* 🧠 Recording decisions
+* 🔍 Tracking progress
+* 🔁 Connecting to commits and pull requests
+
+For example:
+A commit message might say:
+
+```
+Fix crash when saving (#42)
+```
+
+That automatically links to issue #42.
+
+---
+
+## Simple Definition
+
+An **issue** is:
+
+> A tracked discussion or task related to a repository.
+
+---
+
+Since you work with structured workflows and PRD → Spec pipelines, you can think of an issue as:
+
+> The smallest unit of tracked work before code exists.
+
+If you want, I can also explain the difference between:
+
+* Issue vs Pull Request
+* Issue vs Task in Jira
+* Issue vs Requirement (PRD)
+
+Which comparison would help you most?
+
+
+---
+
+```txt
+Can I have use a git repository to manager my study plan, using issues to keep tracked some kind of task?
+```
+
+Yes.
+Not only **can** you — for someone with your profile (structured, versioned, automation-oriented), it’s actually a very powerful approach.
+
+Using a Git repository to manage your study plan turns your learning into a **versioned, auditable, evolvable system** — which fits very well with how you already think about projects.
+
+Let’s break it down.
+
+---
+
+# 🧠 Why Using Issues for Study Works
+
+On platforms like:
+
+* GitHub
+* GitLab
+
+An issue is basically a:
+
+> structured, trackable, discussable unit of work
+
+That maps perfectly to:
+
+* 📚 Study topics
+* 🧩 Exercises
+* 🔬 Experiments
+* 📝 Reflections
+* 🎯 Weekly goals
+
+---
+
+# 🎯 What This Gives You
+
+### 1️⃣ Traceability
+
+You can see:
+
+* When you started studying something
+* How long it stayed open
+* What doubts you had
+* When you "closed the learning loop"
+
+### 2️⃣ Historical Learning Log
+
+Issues become a **learning journal with timestamps**.
+
+### 3️⃣ Structured Thinking
+
+You already like:
+
+* Templates
+* Formalization
+* Agents
+* Reproducible processes
+
+Issues enforce structure.
+
+### 4️⃣ Integration with Your Workflow
+
+You could:
+
+* Link issues to markdown notes
+* Use branches for experiments
+* Use milestones like:
+
+  * `Logarithms`
+  * `Clean Architecture`
+  * `Linux Networking`
+* Even automate weekly summaries
+
+---
+
+# 📂 Example Structure
+
+Repository: `personal-academia`
+
+## Labels
+
+* `math`
+* `english`
+* `backend`
+* `algorithms`
+* `review`
+* `deep-dive`
+* `exercise`
+* `blocked`
+
+---
+
+## Milestones
+
+* Q1-2026
+* Potentiation Mastery
+* English Reading Level A2
+* Linux Admin Foundations
+
+---
+
+## Example Issue
+
+**Title:** Master log2 intuition
+**Labels:** math, deep-dive
+**Milestone:** Potentiation Mastery
+
+**Description Template:**
+
+```markdown
+## Objective
+Understand log2(20) mentally without brute forcing.
+
+## Why
+Improve exponential intuition.
+
+## Prerequisites
+- Powers of 2 memorized
+- Multiplication properties
+
+## Tasks
+- [ ] Memorize powers of 2 up to 2^12
+- [ ] Solve 20 log exercises
+- [ ] Explain to imaginary student
+
+## Reflection (to fill when closing)
+...
+```
+
+When you close it → that topic is consolidated.
+
+---
+
+# 🔁 Advanced Version (Very Tiago-style 😄)
+
+You could:
+
+* Create issue templates
+* Create study "epics" using milestones
+* Use Projects (Kanban board)
+* Use GitHub Actions to:
+
+  * Generate weekly report
+  * Export study metrics
+* Use AI to:
+
+  * Ask you review questions when closing an issue
+  * Generate spaced repetition prompts
+
+---
+
+# ⚖️ When This Works Well
+
+This approach is ideal if:
+
+* You think in systems
+* You like version control
+* You want measurable progress
+* You want to avoid mental overload
+
+It may not work well if:
+
+* You want something very visual like Notion
+* You prefer handwritten journaling
+
+---
+
+# 🧠 Important Psychological Insight
+
+In university, external structure exists:
+
+* Deadlines
+* Grades
+* Professors
+
+Issues simulate that structure.
+
+Closing an issue gives a small dopamine loop similar to finishing a ticket at work.
+
+That may help you recreate your “personal university” at home.
+
+---
+
+# 🏗 Minimal Viable Setup (Start Simple)
+
+1. Create repo: `academia`
+2. Add:
+
+   * README.md (vision)
+   * Labels
+   * 1 milestone
+3. Create 5 study issues only
+4. Don’t over-automate yet
+
+---
+
+# 🚀 Next Level Question
+
+Would you like me to:
+
+* Design a **complete study management architecture** for you?
+* Create a **minimal GitHub template repository structure**?
+* Or help you define a **methodology (like PDCA + Issues)** for learning?
+
+Given how your brain works, we can design something very powerful but still sustainable.