# NEXQ Line-by-Line Legal Syntax & Diction Integration Kit

Generated: 2026-07-09

This package provides a route-by-route, line-referenced legal redline and integration kit for the current public NEXQ site. It is designed for counsel, product, engineering, privacy, security, marketing, and executive review before deployment.

## What is inside

- `redlines/LINE_BY_LINE_MASTER_REDLINE.csv` — master line-by-line redline table for high-risk and content-bearing public site lines.
- `redlines/by_route/` — route-specific redline CSV files.
- `integrated_copy_pages/` — legal-safe replacement copy in Markdown and HTML.
- `snippets/` — drop-in notices for contact forms, health/AI review, finance non-advice, quantum/security scope, metric claim slots, and footer disclosures.
- `integration/guardrails/` — developer guardrails for claim approval, regulated route classification, privacy tracking, and app-store declarations.
- `integration/precommit-copy-lint.js` — copy lint tool for high-risk words and claims.
- `schemas/` — JSON schemas for claim and evidence records.
- `release_gates/` — blocking legal/security/compliance gates.
- `registers/CLAIM_EVIDENCE_REGISTER.csv` — claim register mapping current risky claims to safer approved wording.
- `sources/` — source map for site pages and authoritative legal/security/platform sources.
- `review/EIGHT_PASS_AUDITOR_DEVELOPER_REVIEW_LOG.md` — eight-pass review and integration log.
- `verification/VERIFICATION_REPORT.json` — structural validation results.

## Critical implementation rule

Do not merely paste disclaimers beneath risky claims. Replace risky claims with evidence-bounded wording, then add route-appropriate notices and runtime gates.

## Limitation

No document can make a company legally “soundproof” or immune from claims, enforcement, changing law, or factual mismatch. This kit is designed to materially harden NEXQ’s public wording and engineering controls, but final publication requires licensed counsel and factual owner approval.