---
schema_version: 1
id: RAC-KTQ63DVM2EE9
type: requirement
---
# v0.4.1 Inspection Expansion

## Problem

v0.4.0 inspects individual Markdown files.

As repositories grow, users need visibility across collections of artifacts rather than one file at a time, along with more transparency into how a file was classified.

RAC should support inspecting directories, explaining classifications, and tolerating common heading variants — while remaining purely observational.

## Requirements

[REQ-001] User can inspect a directory
[REQ-002] Directory inspection summarizes detected artifact types
[REQ-003] Directory inspection reports the total files inspected
[REQ-004] Unknown artifacts are included in summary results
[REQ-005] Directory inspection is recursive by default
[REQ-006] User can limit inspection to top-level files
[REQ-007] Directory inspection supports JSON output
[REQ-008] JSON output includes artifact counts by type
[REQ-009] User can request verbose single-file inspection
[REQ-010] Verbose output shows matched and missing sections
[REQ-011] Verbose output shows the confidence calculation
[REQ-012] RAC supports artifact-specific heading synonyms
[REQ-013] Synonym matching is deterministic and case-insensitive

## Success Metrics

- Repository inspection correctly classifies well-formed artifacts
- Inspection remains deterministic and explainable
- JSON output supports future automation workflows

## Risks

- Large repositories may impact performance
- Synonym matching may introduce ambiguity
- Classification confidence may require tuning

## Assumptions

- No new artifact types are introduced in this release
- Inspection remains observational; improvement guidance is a later release
