mizcausevic-dev/contract-clause-obligation-graph

Purpose and principal workflow

This is a deterministic TypeScript control plane for making contract clauses, linked obligations, owners, deadlines, and review blockers visible together. An external HTTP client—typically a browser user or API consumer—initiates the main workflow by requesting an HTML route or JSON endpoint; the app serves a rendered view or a computed response from bundled sample data. It is a static demo, not a live contract-ingestion or AI-extraction system.

Components

HTTP application

• Express routes — src/app.ts: Creates the Express app, exposes the documented HTML and JSON routes, calls the corresponding rendering or data functions, and listens on the configured port when run directly.

Clause and obligation model

• Sample agreement dataset — src/data/sampleClauses.ts: Defines the clause, obligation-edge, and review-packet types and supplies the in-memory records used throughout the demo.

• Control-plane computations — src/services/contractClauseService.ts: Derives dashboard counts, category coverage, and the clause, obligation, review, verification, and combined payload responses from those records.

Operator-facing surfaces

• HTML renderers — src/services/render.ts: Builds the overview and detail-page HTML, using control-plane functions to display clause lanes, obligation relationships, review posture, and verification content.

• HTTP client or browser — null (external): Calls the app’s routes; the README documents both operator pages and JSON API endpoints.

Static publishing

• Static site prerenderer — scripts/prerender.ts: Calls the same renderers and data functions, writes HTML and JSON snapshots into site/, and rewrites page links for static hosting.

• GitHub Pages hosting — null (external): The README documents deployment of the prerendered site to GitHub Pages; the sampled source does not establish the workflow’s exact build-and-deploy steps.

Relationships

• HTTP client or browser -> Express routes: Sends HTTP requests to the app’s HTML or JSON endpoints; routes are registered in the application.

• Express routes -> HTML renderers: Calls page render functions for HTML responses.

• Express routes -> Control-plane computations: Calls data functions and returns their results as JSON.

• HTML renderers -> Control-plane computations: Reads summary, clause, obligation, review, category, and verification results to construct page content.

• Control-plane computations -> Sample agreement dataset: Reads the bundled records to calculate dashboard and category values and provide clause, edge, and review data.

• Static site prerenderer -> HTML renderers: Calls the page render functions to produce static HTML files.

• Static site prerenderer -> Control-plane computations: Calls the data functions to produce static JSON files.

• Static site prerenderer -> GitHub Pages hosting: Supplies the generated site as the documented deployment artifact; exact workflow wiring is not established by the sampled source.

Coverage limits

The sample does not include the full renderer or deployment workflow source, so exact page composition and CI deployment sequencing cannot be confirmed. No live ingestion, persistence, external AI/provider integration, or contract-processing runtime is evidenced; the README and sampled code describe a deterministic demo backed by in-memory data.