Business Builder is an AI plugin and documentation-first framework for creating digital businesses with clear operational standards across strategy, product, monetization, growth, governance, and development handoff.

• Why this project exists
• What is included
• Documentation map
• Recommended usage flow
• Skill testing protocol
• Setup and validation commands
• Canonical language policy
• Contributing
• Governance and legal

Most digital business projects fail because strategy decisions and implementation artifacts are disconnected.
Business Builder provides a structured operating model that links business goals to actionable outputs (requirements, business rules, acceptance criteria, metrics, and risk controls).

• AI plugin workspace for role-based business-building skills
• End-to-end business framework (8 pillars)
• Expanded revenue model library with selection criteria
• Deterministic skill contract guidance
• Development handoff standard (RF/RNF/BR/CA)
• Compliance baseline for Brazil (LGPD, contracts, tax/fiscal, IP)

• Main framework: BUSINESS_DOCUMENTAION.md
• Alternate-language framework: docs/pt-br/BUSINESS_DOCUMENTAION_PT-BR.md
• PT-BR README translation: docs/pt-br/README_PT-BR.md
• Superpowers workspace: docs/superpowers/
• Skills: skills/

1. Read the business framework document.
2. Pick the target pillar (strategy, product, monetization, growth, etc.).
3. Extract decisions, KPIs, gates, and risks.
4. Produce implementation handoff artifacts (RF/RNF/BR/CA).
5. Execute and monitor metrics/risk triggers continuously.

Use co-located validation assets for each skill:

• skills/<skill-name>/validation/pressure-scenarios.md
• skills/<skill-name>/validation/test-log.md

pressure-scenarios.md defines realistic decision pressure (deadline, authority pressure, ambiguity, etc.) with forced options (A/B/C) and "Choose one and justify." prompts.

test-log.md stores auditable evidence for:

• RED baseline failures without the skill
• GREEN compliant behavior with the skill
• REFACTOR iterations when new loopholes are found

Execution cycle:

1. RED: run scenarios without the skill and capture rationalizations verbatim.
2. GREEN: run the same scenarios with the skill loaded and verify expected behavior.
3. REFACTOR: add counter-rules for new rationalizations, then rerun scenarios.

Quick checks:

# Validate scenario structure
grep -nE "IMPORTANT: This is a real scenario|Choose one and justify" skills/<skill-name>/validation/pressure-scenarios.md

# Validate RED/GREEN/REFACTOR log sections
grep -nE "## RED Baseline|## GREEN Verification|## REFACTOR Iterations" skills/<skill-name>/validation/test-log.md

git clone https://github.com/NavesDev/Business-Builder.git
cd BusinessBuilder

# Check key documentation files
ls -la README.md BUSINESS_DOCUMENTAION.md docs/pt-br/README_PT-BR.md docs/pt-br/BUSINESS_DOCUMENTAION_PT-BR.md

# Check README structure
grep -nE "^## " README.md docs/pt-br/README_PT-BR.md

# Check canonical/translation policy sections
grep -nE "Canonical language policy|Politica de idioma canonico" README.md docs/pt-br/README_PT-BR.md

• README.md is the canonical README (English).
• docs/pt-br/README_PT-BR.md is the Portuguese translation.
• Update workflow: edit EN first, then synchronize PT-BR in the same change cycle.

1. Create a branch: git checkout -b docs/<short-topic>.
2. Keep changes focused and scoped.
3. Preserve EN/PT-BR parity when updating README content.
4. Open a PR describing what changed and what was synchronized.

• Changelog: CHANGELOG.MD
• Code of Conduct: CODE_OF_CONDUCT.MD
• License: LICENSE