straymark-status

You can verify documentation compliance by running a status check that identifies recently modified source files and flags likely missing documentation based on code complexity and change categories like security, architecture, or AI/ML.

A StrayMark documentation compliance audit identifies which documentation artifacts were created or updated recently and which recent source changes lack corresponding records across requirements, decisions, ADRs, ethical reviews, and security assessments.

You can find recently modified ADR and security assessment files by scanning expected filename prefixes and directory mappings to detect StrayMark documents modified within a specific timeframe, using git-based discovery or file modification times as a fallback.

Yes, the documentation compliance check uses git-based discovery to find gaps when available, applying git log analysis to connect code changes to documentation needs, with a fallback to file modification times if git is unavailable.

No, you cannot automatically generate missing ADRs and ethical reviews during a code audit, because the compliance check reports gaps and actionable recommendations without creating or modifying any files.