Public / NDA disclosure split

Context

Public marketing claims about an infrastructure platform are fact-checked. State CTOs, Managed Care Organization (MCO) general counsels, and procurement architecture teams read these pages with skepticism trained by years of vendor over-promising. At the same time, implementation details (function signatures, schema column names, file paths, internal architectural identifiers) are intellectual property that leaks competitive advantage to anyone who reads the public site. Generic AI-generated visuals and SaaS-flavored prose erode credibility with technical buyers in ways that are easy to underestimate. The platform needs a content discipline that resolves all three pressures.

Decision

Public-facing pages route capability claims through a MechanismCard primitive: depth indicators, enforcement-surface descriptors, and public statutory or precedent citations only. The richer CodeEvidence primitive (with full source citations, line numbers, and code excerpts) is retained in the codebase but reserved for NDA-gated channels: briefing decks shared under signed agreement, internal documentation, and any future authenticated-access page. Public marketing copy avoids em dashes, AI-cadence hedge words, and stack-disclosure phrasing. Real photography is preferred over AI-generated imagery; the brand is intentionally anti-AI-slop.

Consequences

Procurement officers can fact-check every public claim against the underlying SHIPPED capability without the platform exposing implementation IP. Source-citation requests route through security@civitascom.com for NDA-gated review. Marketing maintenance is more disciplined than the typical SaaS site: ad-hoc copy additions go through the same content-discipline filter as the original launch content. The discipline is itself a positioning statement. The kind of buyer who reads the page closely will notice the absence of AI tells, the presence of statutory citations, and the explicit NDA pathway, and will rate the platform accordingly.

Alternatives considered

• Full code citations on public pages (the original /platform v1.1 launch posture). Rejected after launch: exposes function signatures, schema column names, and file paths to competitors without compensating credibility benefit. The depth indicators in MechanismCard convey rigor without leaking IP.
• No precedent or statutory citations on public pages, NDA-only. Rejected: precedent and statutory citations are public legal record by definition; citing them publicly is descriptive, not advisory, and the credibility lift for procurement audiences is meaningful.