Developer documentation should cover API, SDK, MCP, authentication, model identity, and examples only when those surfaces are real and available.
Developer access is a controlled surface. Public documentation can state the intended boundary before keys or private examples are issued.
The page should explain what relationship a visitor is entering: research, media, partner, investor, developer, access, contact, status, or trust.
API, SDK, MCP, authentication, and model identity surfaces.
Public developer material distinguishes documentation from approved API or private deployment access.
Accounts, SSO, API keys, model entitlements, benchmark downloads, and private research surfaces remain separate approval states.
Examples should be published only when they match a real available interface.
Lab records carry credibility, lineage, collaboration, and access signals.
Institutional pages establish CognitivityX Labs, Mourad's authorship, public artifacts, operating boundaries, and access channels.
Labs record in the public site architecture.
Developer documentation should cover API, SDK, MCP, authentication, model identity, and examples only when those surfaces are real and available.
The record separates released claim, evidence class, boundary condition, and access path.
Use the access route for model review, benchmark packet, system walkthrough, or institutional collaboration.
For developers material, request access to the relevant card, benchmark packet, workflow demo, or review session.
