Bilingual Navigation: Versión en Español
↑ Evolith Tracker position within the E2E Product Vision · MD3 — click to enlarge
Evolith Tracker is the Governance Control Plane satellite of Evolith Core.
It enforces the Governed Composition architecture: centralizing SDLC governance and auditing,
while delegating execution to best-in-class external providers (SCM, CI/CD, Work Systems).
The Core defines. Providers execute. Evaluators assess. Tracker decides and audits.
Goal: execute the Software Development Life Cycle through 6 sequential Phase Gates.
Objectives:
- Digitize and automate Intake, Discovery, Design, Construction, QA, and Release.
- Give every phase its own hub with the related domain documents.
The six phases below run from conception to operations; each section lists that phase's worked documents and its entry hub.
Phase 00 - Strategic Intake · Worked
| Link (URL) | Description (brief explanation) | Goal / Objective | Typification (category or type) |
|---|---|---|---|
| Strategic Intake Hub | Phase 0 hub with full detail: technical feasibility and PPM integrations | Evaluate and approve strategic business opportunities | Hub |
The Funnel 0 is the boundary layer (Boundary) of Evolith Tracker that connects business strategy with engineering execution. Before an idea enters the construction flow (SDLC), it must be processed as an "Opportunity" to evaluate its technical feasibility, budget, and expected ROI.
To keep Evolith Tracker agnostic and avoid contamination with financial logic or third-party portfolios (Vendor Lock-in), Funnel 0 supports two operating models:
Opportunities are managed autonomously within Evolith Tracker.
- The Product Manager or Business Sponsor creates the opportunity directly in the Tracker UI, defining the key metadata (Maximum budget, expected ROI, Risk Level).
- The Loop Engineer reviews the opportunity and executes an initial Technical Feasibility Filter. If viable, the opportunity is approved and formally becomes an "Initiative", transitioning to Phase 1 (Discovery Hub).
Evolith Tracker acts as a receiver for external Project Portfolio Management (PPM) systems, such as Meisterplan, Jira Align, or SAP.
- Evolith exposes an Anti-Corruption Layer (Inbound ACL) through a standardized event-driven API.
- The external system triggers a Webhook with the financial portfolio data.
- The Evolith Tracker ACL intercepts the payload, adapts it to the ubiquitous language of the Evolith ecosystem (discarding unnecessary financial complexity), and automatically generates the opportunity in Funnel 0.
- From this point on, Evolith Tracker takes control of the execution governance, emitting webhooks back to the external system to update on effort deviations, architectural risks (Drift), or efficiency metrics (DORA).
Phase 01 - Discovery · Worked
| Link (URL) | Description (brief explanation) | Goal / Objective | Typification (category or type) |
|---|---|---|---|
| Discovery Hub | Phase 1 hub with the full detail: functional scopes and user stories | Navigate the complete phase document set | Hub |
| Diagramas Conceptuales | Master flow + 6 diagramas por modulo: sistema completo, variantes, zonas de configuracion, agregados | Entender el Tracker completo visualmente | Diagram hub |
Phase 02 - Design · In progress
| Link (URL) | Description (brief explanation) | Goal / Objective | Typification (category or type) |
|---|---|---|---|
| Design Hub | Phase 2 hub with the full detail: consolidated domain model (DDD) and the technical design suite | Navigate the complete phase document set | Hub |
Phase 03 - Construction · Not started
| Link (URL) | Description (brief explanation) | Goal / Objective | Typification (category or type) |
|---|---|---|---|
| Construction Hub | Empty hub — phase not started; will produce Technical Stories and DoD evidence | Index the phase documents as they are worked | Hub |
Phase 04 - QA · Not started
| Link (URL) | Description (brief explanation) | Goal / Objective | Typification (category or type) |
|---|---|---|---|
| QA Hub | Empty hub — phase not started; will produce the Test Summary Report and acceptance evidence | Index the phase documents as they are worked | Hub |
Phase 05 - Release · Not started
| Link (URL) | Description (brief explanation) | Goal / Objective | Typification (category or type) |
|---|---|---|---|
| Release Hub | Empty hub — phase not started; will produce Release Notes and deployment evidence | Index the phase documents as they are worked | Hub |
Before contributing, read:
- Satellite Manifest — Machine-readable declaration of the satellite ↔ Core boundary (role, upstream, invariants)
- AGENTS.md — Agent rules and conventions
- DECISIONS.md — Architectural decisions log
- Gaps & Opportunities Tracking — Product-level gaps and improvement opportunities
Dual licensed. See LICENSE and NOTICE.