mizcausevic-dev/campaign-taxonomy-governor

Purpose and principal workflow

Campaign Taxonomy Governor is a synthetic-data operator surface for reviewing campaign naming changes, audience and attribution blockers, and launch readiness. An external HTTP client—typically an operator’s browser—initiates the main workflow by requesting a page or API route; the Express application serves rendered HTML or JSON derived from the sample campaign data. The repository also has a separate prerender path that writes static pages and JSON for the documented GitHub Pages deployment.

Components

HTTP application

• HTTP client — Path: null (external). Requests the operator pages or JSON endpoints; the README documents both route sets.

• Express route application — src/app.ts. Defines the page and API routes, invokes render or data-service functions, and sends HTML or JSON responses.

Governance data and presentation

• Campaign governance data — src/data/sampleCampaigns.ts. Defines typed synthetic taxonomy changes, audience risks, and launch packets; these are the source records used by the service.

• Governance views and payloads — src/services/campaignTaxonomyGovernorService.ts. Computes summary counts and recommendations, exposes the three record collections and verification statements, and combines them into a sample payload.

• Operator page rendering — src/services/render.ts. Builds HTML for the overview and governance lanes using service results; the sampled excerpt shows page renderers calling the service functions directly.

Static publishing

• Static site prerenderer — scripts/prerender.ts. Calls the same service and rendering functions, writes page HTML and JSON files under site, and copies the CNAME for static hosting.

Relationships

• HTTP client -> Express route application: sends page or API requests; the route definitions establish the endpoints.

• Express route application -> Operator page rendering: calls the relevant renderer for HTML page requests.

• Operator page rendering -> Governance views and payloads: reads summary and governance records to populate rendered pages.

• Express route application -> Governance views and payloads: calls service functions for JSON API responses.

• Governance views and payloads -> Campaign governance data: imports and reads the synthetic collections to compute summaries and return records.

• Static site prerenderer -> Governance views and payloads: calls service functions to produce static JSON payloads.

• Static site prerenderer -> Operator page rendering: calls page renderers to produce static HTML.

• Static site prerenderer -> Static output files: writes rendered pages and JSON under site and copies the domain file; static output is the prerenderer’s filesystem result, not a repository component.

Coverage limits

Source excerpts do not include the full renderer, deployment workflow, or runtime hosting configuration. The README documents GitHub Pages deployment, but the sampled inputs do not establish the precise deployment steps or whether the Express server is used in production. No external campaign, CRM, ad-platform, or analytics integrations are evidenced; the service uses synthetic local data.