Skip to content

PRODUCT_VISION.md

Latest commit

 

History

History
36 lines (27 loc) · 3.14 KB

PRODUCT_VISION.md

File metadata and controls

36 lines (27 loc) · 3.14 KB

Product Vision Manifest: EVOLITH TRACKER

Bilingual Navigation: English (this document) · Versión en Español

1. What is Evolith Tracker?

Evolith Tracker is the Governance Control Plane for AI-Native software engineering. It is not a traditional task manager (not a Jira or Trello) nor does it intend to replace specialized industry tools. Its purpose is to digitize, automate, and audit the entire software development lifecycle (SDLC) by strictly applying Evolith's architectural rules.

It inverts the traditional development equation: AI builds and executes; external tools operate; Evolith governs and orchestrates.

2. Governed Composition

Evolith Tracker adopts the Governed Composition model. This means we build the irreducible governance kernel (Phase Gates, traceability, Core rules, and the Evidence Graph) and consume mature commodity capabilities through Ports and Adapters.

  • Core defines: Rules, schemas, taxonomies, and contracts (evolith_arch32).
  • Providers execute: Repositories, CI/CD, work management systems (Jira), LLM observability, and Analytics tools.
  • CLI / MCP evaluates: Executes stateless technical validations (Technical Evaluation Result).
  • Tracker decides: Centralizes and consolidates evidence to issue the canonical decision (Gate Decision) and advance the phase.

3. The Architectural Pillars (The Engine)

  • Multi-Tenant Progressive Monolith Ecosystem: Prepared for Cloud SaaS with absolute data isolation per TenantID.
  • Dependency Inversion (Ports & Adapters): Its core is shielded. External providers (e.g., Langfuse, Jira, GitHub) connect through an Anti-Corruption Layer (ACL) ensuring their schemas do not contaminate the Tracker's domain.
  • Delegated Identity (UMS): Consumes AuthN, AuthZ, and roles (RACI) directly from the independent SaaS UMS.
  • Upstream Governance: Evolith Core contains the immutable guidelines. The Tracker inherits, applies, and can propose improvements (ADRs) to the Core based on operational evidence.

4. The Value Stream: The 5 Modular Blocks

Tracker models the SDLC through 5 consecutive gates (Phase Gates), where it acts as the sole final authority to allow transitions:

  1. Discovery & Ideation Hub: Validate ROI and KPIs; ensure the proposed solution aligns with the "Build vs Compose" strategy.
  2. Architecture Spec-Driven (Design): Consolidate contracts (OpenAPI/AsyncAPI) and approved ADRs.
  3. Construction Tracking: Validate evidence from external repositories and CI/CD against design contracts (strict Architecture Drift control).
  4. Automated QA & Integration: Reception of test results, security, and deep integration via ports.
  5. Dynamic Release Planner: Command board for deployments. In case of a block, agents propose a contingency flow ("Re-Do") and a human authorizes.

5. The Analytical Brain (Scorecards)

Tracker consolidates the immutable Evidence Graph. Through Analytics ports, it exposes validated metrics of the entire value stream:

  • DORA & SPACE Metrics
  • Architecture Adherence Index: Early warnings of architecture deviation detected during pre-deployment phases.