documentation-specialist

To write documentation with source evidence, you define a bounded target, gather a required source packet, and execute edits while maintaining a claim ledger for traceable accuracy. This process prevents ungrounded claims by validating every assertion against explicit source evidence.

Bounded documentation restricts writing and editing to a specific, defined scope with traceable source evidence and policy constraints. You need it for READMEs, runbooks, or ADRs to ensure accuracy, maintain safe publication boundaries, and prevent unauthorized content expansion beyond the target boundary.

Yes, you can audit and repair existing architecture documents by applying a bounded scope and validating content against a claim ledger. This process identifies ungrounded assertions, adds source-backed evidence paths, and repairs documentation to ensure accuracy and compliance with publication boundaries.

Yes, milestone documentation requires explicit validation steps and risk disclosures when processed within a bounded scope. Applying source-backed edits and a claim ledger ensures that milestone updates remain accurate, traceable to source evidence, and constrained by defined policy boundaries before publication.

The primary limitation of bounded documentation is that policy constraints stop publication beyond the defined boundary. If your onboarding guides require expanding scope or adding unvalidated claims outside the gathered source evidence, the bounded approach will block those edits to maintain accuracy.

The best way to plan and polish an Architecture Decision Record is to bound the target, gather explicit source evidence, and execute a documentation edit. This approach uses a claim ledger and validation steps to ensure traceable accuracy and safe publication boundaries.