Documentation & Artifacts

Last Audited: 2026-08-21
NUP AI-Native Verified
ISO/IEC 42001:2023 Cl. 7.5 (Documented Info)EU AI Act Art. 11 & Annex IVISO 27001:2022 A.8.25 (Secure Coding)
In Plain Language

In cross-functional AI initiatives, teams frequently experience confusion over documentation deliverables: developers assume product managers write safety dossiers, compliance writers assume engineers maintain context schemas, and technical writers lack clear templates for AI retrieval. This topic establishes a unified, RACI-lite inventory across three clearly-owned groups: AI Development Governance (owned by Dev Leads & AppSec), AI Product Documentation (owned by Data Scientists & Compliance Writers), and AI-Native Technical Communications (owned by DevRel & Technical Writers).

Architectural Orientation: Eliminating Documentation Ambiguity

A successful probabilistic engineering transition requires distinct artifacts produced at different stages of the development and operational lifecycle. Without explicit ownership boundaries, organizations either suffer from redundant documentation or, more critically, discover missing regulatory evidence right before launch.

The Netspective Unified Process (NUP) Artifact Inventory defines thirteen core deliverables organized into three functional domains with explicit Accountable Owner (A) and Informed Consumer (I) roles.

Probabilistic Artifacts RACI-Lite TaxonomyA visual mapping of NUP AI-native artifacts across three distinct ownership domains: Governance, Product Documentation, and Technical Communications.NUP Artifact Inventory & RACI-Lite OwnershipAssigning explicit authorship accountability and consumer roles across the 3 core documentation domains.1. GOVERNANCEAI Development GovernanceOwner: Dev Leads & AppSecConsumer: Developers & LegalAI Tool Usage PolicyIDE assistants & secret protectionCode Provenance RegisterAI synthesis & license trackingSecurity Review ChecklistAppSec & prompt injection auditTech Debt AssessmentAI code bloat & maintainability2. PRODUCT DOCSAI Product DocumentationOwner: ML Eng & ComplianceConsumer: Regulators & CustomersModel Cards & System DossiersOperational bounds & intended useData Sheets for DatasetsKnowledge base lineage & bias notesContext Engineering SpecsPrompt schemas & token budgetsRAG Pipeline ArchitectureChunking & vector index topologyBias & Robustness AuditsSubgroup fairness & red teaming3. TECH COMMSAI Technical CommsOwner: DevRel & Tech WritersConsumer: LLM Agents & DevelopersRetrieval Structure TemplatesHeadings & chunkable syntaxMetadata Frontmatter SchemasJSON tags & cryptographic hashFeedback Loop GuidesUser correction ingestion pipelineAI-First Writing GuidelinesHigh-density plain-text syntax

1. AI Development Governance Artifacts

Governs developer workflow policies, assistant configurations, and code review standards:

AI Tool Usage & IDE Assistant Policy

GOV-01

Defines approved coding assistants (Claude Code, Cursor, Copilot), required opt-outs for training on customer code, and API key protection standards.

Owner: CISO / Eng LeadConsumer: All Engineers

Code Provenance & Authorship Register

GOV-02

Tracks AI synthesis markers in PRs, attributing code generation sources to ensure open-source licensing compliance and auditability (ISO 27001 A.8.25).

Owner: Dev Lead / ArchitectConsumer: IP Legal & QA

Security Review Checklist for AI Code

GOV-03

AppSec checklist targeting AI-generated anti-patterns: hallucinated dependencies, insecure deserialization, and missing authorization guards.

Owner: AppSec LeadConsumer: PR Reviewers

Tech Debt Assessment Framework

GOV-04

Measures code bloat, cyclomatic complexity creep, and architectural drift resulting from rapid AI generation.

Owner: Principal ArchitectConsumer: VP Eng / Leads

2. AI Product Documentation Artifacts

Technical and compliance documentation required for product safety, model transparency, and audit dossiers:

Model Cards & System Operational Dossiers

PROD-01

Documents model architecture, intended use, known operational boundaries, and performance benchmarks (EU AI Act Annex IV / NIST AI RMF).

Owner: Data Scientist / ML EngConsumer: Regulators & Customers

Data Sheets for Knowledge Bases & Datasets

PROD-02

Cryptographic provenance, collection methodology, representation balance, and data cleansing logs for RAG knowledge bases (EU AI Act Art. 10).

Owner: Data Engineer / ComplianceConsumer: AI Auditors

Context Engineering Specs & Prompt Manifests

PROD-03

Version-controlled prompt templates, system instructions, token allocation budgets, and dynamic middleware injection rules.

Owner: AI Architect / Prompt EngConsumer: Backend Engineers

RAG Pipeline Architecture & Index Topology

PROD-04

Documents chunking strategies, embedding models, vector database schemas, hybrid keyword weighting, and reranking parameters.

Owner: Search Infra EngineerConsumer: DevOps & SRE

Bias, Fairness & Robustness Audit Reports

PROD-05

Results from subgroup disparity evaluations, toxicity probes, adversarial jailbreak red-teaming, and statistical confidence intervals.

Owner: QA Lead / AI EthicistConsumer: Compliance Officers

3. AI-Native Technical Communications Artifacts

Authoring templates and schemas optimized for dual human-and-AI ingestion (RAG, agent context, tool discovery):

Structured Retrieval Templates

COMM-01

Standardized Markdown/HTML document structures optimized for chunk boundary alignment and high-precision embedding retrieval.

Owner: Technical Writer / DevRelConsumer: Ingestion Agents

Metadata & Frontmatter Schemas

COMM-02

JSON/YAML header schemas defining content freshness, domain classification, and cryptographic chunk signatures.

Owner: Content EngineerConsumer: Vector Indexers

Feedback Loop Implementation Guides

COMM-03

Protocols for capturing user corrections and downvotes, routing them back to documentation maintainers to patch knowledge gaps.

Owner: UX / Product WriterConsumer: Content Maintainers

Writing Guidelines for AI-First Docs

COMM-04

Editorial style guide emphasizing concise declarative phrasing, explicit type signatures, and avoidance of ambiguous pronouns.

Owner: Editorial / Lead WriterConsumer: Technical Authors
Full Category Deep Dive AvailableExplore comprehensive templates, schema specifications, and automation pipelines in our dedicated curriculum.
Explore AI-Native Technical Comms

Master RACI-Lite Inventory Matrix

Artifact NameDomainAccountable Owner (A)Informed Consumer (I)Standard
AI Tool Usage PolicyGovernanceCISO / Eng LeadAll DevelopersISO 42001 Cl. 6
Code Provenance RegisterGovernanceDev Lead / ArchitectLegal & ComplianceISO 27001 A.8.25
Security Review ChecklistGovernanceAppSec LeadPR ReviewersNIST CSF 2.0
Model Cards & System DossiersProduct DocsData Scientist / ML EngRegulators / CustomersEU AI Act Annex IV
Data Sheets for DatasetsProduct DocsData Engineer / ComplianceAI AuditorsEU AI Act Art. 10
Context Engineering SpecsProduct DocsAI Architect / Prompt EngBackend EngineersISO 42001 Cl. 8
Bias & Robustness AuditsProduct DocsQA Lead / AI EthicistCompliance OfficersNIST AI RMF
Structured Retrieval TemplatesTech CommsTechnical Writer / DevRelIngestion AgentsNUP Comms
Metadata Frontmatter SchemasTech CommsContent EngineerVector IndexersNUP Comms
Try This with AI: Project Artifact Checklist Generator

Use this prompt in your AI assistant to generate a tailored RACI artifact checklist for your upcoming AI initiative.

Act as a Principal Technical Documentation & AI Governance Architect. Generate a tailored RACI artifact checklist for this project: - Project Title: [e.g., Enterprise Clinical RAG Assistant] - Team Composition: [e.g., 3 Backend Engineers, 1 ML Engineer, 1 AppSec Reviewer, 1 Technical Writer] - Target Compliance Standard: [e.g., ISO/IEC 42001 and EU AI Act High-Risk] Generate: 1. The exact subset of the 13 NUP artifacts required for this initiative. 2. Explicit primary owner and reviewer assignments based on the team composition. 3. A milestone delivery schedule mapped to the 6-stage NUP lifecycle.
Next in Core Concepts

Topic 8: Integration with an existing QMS

Proceed to Topic 8
Previous Section
Deterministic Unified Process
Next Track
The Four Layers of LLM Engineering

Community Discussion & Feedback

Attributed peer feedback and official Netspective architecture notes.

Was this documentation helpful?(100% found this helpful • 0 ratings)

Leave Feedback or Question

○ Loading user info...
0/2000 chars

Discussion (0)

Loading discussion thread...