---
schema_version: 1
id: RAC-KTQ63DVKK49N
type: requirement
---
# v0.4 Artifact Inspection

## Problem

As product knowledge grows, it becomes difficult to understand what a document contains and whether it follows an expected structure.

Before RAC can offer guidance or AI-assisted analysis, it must first understand what kind of artifact it is inspecting.

RAC should provide a lightweight inspection capability that identifies artifact types and reports structural completeness without modifying content.

## Requirements

[REQ-001] User can inspect a Markdown document
[REQ-002] RAC attempts to identify the artifact type
[REQ-003] RAC reports artifact type confidence
[REQ-004] RAC supports detection of Requirement artifacts
[REQ-005] RAC supports detection of Decision artifacts
[REQ-006] RAC reports Unknown when confidence is insufficient
[REQ-007] RAC identifies expected sections for the detected type
[REQ-008] RAC reports sections present
[REQ-009] RAC reports sections missing
[REQ-010] RAC reports inspection results without modifying content
[REQ-011] Inspection results are available as human-readable text and JSON
[REQ-012] User can inspect a file path or stdin
[REQ-013] RAC reports unsupported file types with actionable guidance

## Success Metrics

- RAC correctly identifies Requirement and Decision artifacts in the repository
- Inspection completes in under one second for typical artifacts
- Results are understandable by both humans and machines
- Inspection output can support future guidance workflows

## Risks

- Artifact structures may vary significantly between teams
- Documents may partially match multiple artifact types
- Confidence scoring may require refinement as artifact types are added

## Assumptions

- Roadmap, Prompt, and Meeting artifacts are deferred until their schemas are formalized
- Inspection is observational only; improvement guidance belongs to a later release
