Portfolio engineering roadmap: validation depth and release readiness

[Alaamo7]

Goal

Move the curated Pine Script portfolio from presentation-ready documentation to a more mature engineering workflow without overstating trading performance.

Next engineering milestones

• Re-test the five curated indicators across multiple EGX symbols and at least two timeframes. Use docs/REGRESSION-TEST-MATRIX.md as the canonical test plan.
• Record bar-close vs live-bar behavior for signal-producing indicators. The required observations are defined in docs/REGRESSION-TEST-MATRIX.md.
• Add regression notes for pivots, higher-timeframe data, labels/tables, alerts, object stability, and signal timing. See docs/REGRESSION-TEST-MATRIX.md.
• Review naming consistency across case-study files and documentation paths. Stable public case-study paths are retained intentionally; the canonical mapping is documented in the case-study index and docs naming policy.
• Define a versioning and release policy for the portfolio. See docs/VERSIONING.md.
• Create the first formal tagged portfolio release after refreshed validation evidence is complete.
• Add release notes that distinguish compile/render validation from strategy profitability.
• Add lightweight automated checks for repository structure, required documentation files, curated indicator/screenshot sets, and relative Markdown links. See scripts/validate_repo.py and .github/workflows/repository-validation.yml.

Release gate

Before the first tagged release:

• Complete the minimum matrix across at least three EGX symbols and both 15m and 1D.
• Confirm compile/render status for all five curated indicators.
• Record live-bar versus bar-close behavior for signal-producing indicators.
• Resolve critical regression issues.
• Refresh screenshots/evidence where behavior materially changed.
• State explicitly in release notes that software validation is not profitability validation.

Guardrails

• Do not claim profitability without separate backtest/out-of-sample evidence.
• Keep code, screenshots, case studies, and verification notes synchronized.
• Preserve the curated portfolio separately from the larger archival repository.
• Treat a software release tag as a technical/versioning milestone, not as evidence of trading profitability.