mizcausevic-dev/vertical-benchmark-comparator

Purpose and principal workflow: Vertical Benchmark Comparator turns synthetic vertical-lane data into board-oriented comparisons of benchmark strength, evidence depth, commercial pull, repeatability, and execution drag. The main workflow begins when a board or executive user requests a page or JSON endpoint over HTTP; an operator can also initiate a separate analysis by running the CLI against a JSON file. The product is read-only and explicitly does not present its sample as live financial or investment advice.

Components

HTTP presentation and routes

• Executive and board user — Path: null (external actor). Initiates the main workflow by requesting a page or API response.

• Express application — Path: src/app.ts. Creates the Express app, maps the documented page and API routes, and starts listening when run directly.

• Board-facing views — Path: src/services/render.ts. Renders overview, register, comparison, investment, verification, and documentation pages as HTML, drawing on the report-data functions.

• Prerendered site and API artifacts — Path: dist-static/index.html. The README documents a prerendered static site with route-specific pages and JSON payloads; this tree establishes generated output exists, but not how it is served or deployed.

Benchmark data and analysis

• Synthetic benchmark lanes — Path: src/data/sampleVerticalBrief.ts. Supplies representative lane records with narrative, ownership, evidence, action, and score fields; the excerpt shows several sectors and is partial.

• Benchmark analysis engine — Path: src/analyze.ts. Assesses score strength and execution drag, computes composite priorities, and aggregates report-level counts, averages, revenue, and a leading message.

• Benchmark data contract — Path: src/types.ts. Defines the input lane, assessment, report, summary, and exported-payload shapes used by analysis and consumers.

• Vertical brief projections — Path: src/services/verticalBriefService.ts. Analyzes the sample at module initialization and exposes summary, register, matrix, investment, risk, verification, and combined-payload projections.

Programmatic access

• CLI operator — Path: null (external actor). Starts the separate command-line workflow by supplying an input JSON file and optional output format.

• Analysis CLI — Path: src/cli.ts. Reads and parses the supplied file, invokes the analysis engine, then emits JSON or a formatted text summary.

• Summary formatter — Path: src/format.ts. Converts report summary fields into the CLI’s human-readable, line-oriented output.

• Library entry point — Path: src/index.ts. Exports the analysis functions, sample data, and public types for programmatic consumers.

Relationships

• Executive and board user -> Express application: sends HTTP requests for pages or JSON; the app defines the routes and handles their responses.

• Express application -> Board-facing views: calls render functions for HTML routes.

• Board-facing views -> Vertical brief projections: calls projection functions to populate page content.

• Express application -> Vertical brief projections: calls projection functions for API responses.

• Vertical brief projections -> Synthetic benchmark lanes: reads the sample records to produce register, matrix, and payload data.

• Vertical brief projections -> Benchmark analysis engine: analyzes the sample and uses report results for summary, investment, and risk outputs.

• Benchmark analysis engine -> Benchmark data contract: uses the defined lane, assessment, and report shapes; the cited analysis code supplies the calculations.

• CLI operator -> Analysis CLI: invokes the command-line program with an input path and optional format.

• Analysis CLI -> Benchmark analysis engine: passes parsed lane records to analyze.

• Analysis CLI -> Summary formatter: passes the report summary for text output; JSON mode instead serializes the report directly.

• Library entry point -> Benchmark analysis engine: re-exports analysis functions for library consumers.

• Library entry point -> Synthetic benchmark lanes: re-exports the sample dataset.

• Prerendered site and API artifacts: the README documents prerender generation, but the sampled source does not establish the generation or deployment wiring.

Coverage limits: The excerpts do not include the prerender script, deployment workflow details, or the complete sample dataset. Therefore, the exact static-generation flow, hosting arrangement, and full lane coverage cannot be established here.