Pulsebook

Development practices, workflows, and technical architecture guide for Equevu

---

Equevu Pulsebook Documentation

Welcome to the Equevu Pulsebook documentation. This guide serves as a comprehensive resource for understanding our development practices, workflows, and technical architecture at Equevu.

Table of Contents

Development Workflow

• Pull Requests (PR) - Guidelines for creating and managing pull requests
• Code Review - Best practices for conducting thorough code reviews
• Sprint Cycle - Our sprint planning and execution process
• Branch Naming Convention - Standardized branch naming rules and examples
• Deployment Strategy - Release process and deployment pipeline

Coding Standards

• Python & Django Standards - Python/Django coding conventions and repository pattern guidelines
• Code Architecture - Code design patterns

Team Culture

• Communication Unwritten Rules - Team communication guidelines and expectations

Technical Documents

• Decision Making - Templates for documenting technical and business decisions
• Incident Report Template - Standardized incident documentation and postmortem process

---

Quick Start

If you’re new to the team, we recommend reading the documentation in this order:

1. Communication Unwritten Rules
2. Code Architecture
3. Sprint Cycle
4. Pull Requests
5. Code Review

Contributing

To update this documentation, please follow our PR guidelines and ensure all changes go through the code review process.