Overview
What the project is designed to do
An independent publishing and advertising concierge demonstration combining public inquiry routes with a synthetic role-aware workspace for triage, campaigns, proposals, analytics, knowledge, routing, and human-controlled suggestions.
The public experience routes advertising, subscription, editorial, and fallback requests through clear entry points and includes a client-side request tracker.
A broad staff workspace demonstrates synthetic inquiry and campaign operations while keeping editorial material outside AI context and every suggested action under human control.
Intended users
Who the release supports
Publishing audiences submitting advertising, subscription, or editorial inquiries, plus fictional operations teams reviewing and routing those requests.
Problem
What needed to change
Publishing inquiries arrive through different departments and formats, making responsible routing difficult without blurring editorial separation or overstating automated capability.
Solution
How the release responds
Provide one branded intake surface, deterministic department routing, and a role-aware synthetic workspace where AI remains suggestion-only and editorial content stays excluded.
Key features
What visitors can use
- Advertising, subscription, and editorial inquiry routes
- Request tracking experience
- Synthetic staff triage and campaign workspace
- Interactive routing-policy tester
- Constrained human-reviewed Copilot demonstration
Implementation
How it was built
- 01
A Next.js and React application lives in the repository's web workspace and exposes public, access, and operations shells.
- 02
TypeScript modules centralize release policy, deterministic routing, workspace fixtures, and interactive tools.
- 03
The same source supports a native Next.js Vercel build and a separately preserved Vinext Sites target.
Architecture
Delivery shape
A TypeScript application separates public inquiry pages, staff-access routes, and synthetic workspace routes, with no production data or messaging backend.
Product boundary
What this release does not claim
- All visible records are synthetic and the interface makes no affiliation claim
- No production authentication, durable database, private object storage, outbound email, background jobs, paid model provider, autonomous pricing, publishing, routing, or sending
