pressroute-ai - Sell Project

PressRoute AIPressRoute AI is an independent publishing and advertising inquiry concierge demonstration. It gives a publisher one public front door for advertising, subscriptions, and editorial requests, plus a role-aware staff workspace for triage, routing, proposals, analytics, knowledge, and human-controlled AI suggestions. The implementation is original, clean-room code. The supplied PressRoute screenshots are the visual authority. The five uploaded application archives were audited for product ideas, security risks, provenance, and licensing; no source code or protected assets were copied from them. What is implemented 17 public routes, 5 staff-access routes, and 20 staff-workspace routes from the 42-page atlas. Responsive public, authentication, and operations shells with shared PressRoute branding. Deterministic advertising, subscription, editorial, and fallback routing concepts. Demonstration inquiry, campaign, organization, proposal, analytics, knowledge, team, routing, settings, and Copilot experiences. Working client-side routing tester, settings tabs, and constrained AI-assistant demo. Social preview, an original wordless favicon/PWA/avatar system, route/security/accessibility contract tests, and both Next.js/Vercel and Sites build targets. This is a front-end product prototype. It does not yet include production authentication, a durable database, private object storage, outbound email, background jobs, or a paid model provider. All visible records are synthetic. Run locally Requirements: Node.js 22.13 or newer and npm. cd web Copy-Item .env.example .env.local npm ci npm run dev Open http://localhost:3000. Validate cd web npm run verify npm run verify:vercel npm audit --omit=dev npm run verify checks the Sites/Vinext target. npm run verify:vercel runs the same whitespace, lint, TypeScript, unit, route, asset, security, and accessibility contracts before a native Next.js production build. Release configuration The application fails closed as a synthetic portfolio demonstration. Configure these names in Vercel without committing values: APPURL - canonical absolute origin used for metadata. DEMOMODE - keep enabled for the portfolio release. EMAILDELIVERYENABLED - keep disabled; no outbound delivery integration is present. AIFEATUREENABLED - keep disabled; the bounded deterministic assistant remains available without live provider calls. Vercel target: team princeinobas-projects, project pressroute-ai, root directory web, framework Next.js, build command npm run build:vercel. The release flow is Preview verification followed by promotion of the same immutable deployment to Production at https://pressroute-ai.vercel.app. The existing Sites target remains a separate deployment. Vercel configuration and releases must not mutate or remove it. Brand assets The route-network mark is original artwork and contains no text or copied corporate logo. Rebuild and verify the raster set with: cd web python scripts/generatebrandassets.py python scripts/verifybrandassets.py npm run test:e2e Project map web/app - route dispatcher, root layout, metadata, and not-found handling. web/components - shared public and staff application shells. web/features - public, inquiry, authentication, workspace, and interactive feature modules. web/styles - responsive design-system and page-family styles. web/tests - policy, security-boundary, route, and accessibility checks. web/docs/design/reference - retained screenshot references; never shipped as application assets. docs/audit - archive inventory, provenance, license boundary, and findings. docs/architecture - system boundaries, data model, routing, AI policy, and decisions. docs/security - threat model and retention guidance. docs/design - page atlas, screenshot manifest, and visual review. docs/deployment - Vercel release, environment matrix, Sites separation, verification, and rollback. Safety boundaries Editorial material is excluded from AI context by policy. AI output is suggestion-only and cannot send, publish, price, reroute, or mutate records. Cross-department access is denied by default in the documented production model. Attachments are private by design in the production architecture. Preview and production data must remain isolated. The interface labels itself as an independent demonstration and makes no affiliation claim. See product audit, architecture overview, threat model, and deployment verification for the handoff details.