Contract framework with markdown-native contracts utilizing fenced YAML blocks
This commit is contained in:
parent
3cfda33bc9
commit
e3e13ee45a
36 changed files with 2877 additions and 13 deletions
23
examples/documents/adr-valid.md
Normal file
23
examples/documents/adr-valid.md
Normal file
|
|
@ -0,0 +1,23 @@
|
|||
---
|
||||
document_type: adr
|
||||
status: accepted
|
||||
---
|
||||
|
||||
# Use Markdown Contracts
|
||||
|
||||
## Context
|
||||
|
||||
The problem is that plain heading counts do not explain whether content is
|
||||
useful. Authors and agents need a contract that names the expected sections and
|
||||
the job each section must do.
|
||||
|
||||
## Decision
|
||||
|
||||
We will use markdown-native document contracts with deterministic diagnostics as
|
||||
the foundation for generation, validation, and later semantic assessment.
|
||||
|
||||
## Consequences
|
||||
|
||||
The tool can check author intent before generation or review work continues.
|
||||
Future adapters can add form prefill and LLM rubrics without replacing the core
|
||||
diagnostic model.
|
||||
Loading…
Add table
Add a link
Reference in a new issue