docassert 0.1.0__tar.gz

docassert-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 C4G Enterprises Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

docassert-0.1.0/NOTICE

@@ -0,0 +1,4 @@
+docassert
+Copyright 2026 C4G Enterprises Inc.
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).

docassert-0.1.0/PKG-INFO

@@ -0,0 +1,125 @@
+Metadata-Version: 2.4
+Name: docassert
+Version: 0.1.0
+Summary: Unit testing for business documents — validate structured Markdown docs against a configurable audit standard.
+Author: C4G Enterprises Inc.
+License: Apache-2.0
+Project-URL: Homepage, https://docassert.com
+Project-URL: Repository, https://github.com/c4g-john/docassert
+Project-URL: Issues, https://github.com/c4g-john/docassert/issues
+Keywords: pmo,documentation,validation,governance,markdown,audit,traceability,ci
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Documentation
+Classifier: Topic :: Text Processing :: Markup :: Markdown
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: python-frontmatter>=1.1
+Requires-Dist: PyYAML>=6.0
+Requires-Dist: jsonschema>=4.0
+Provides-Extra: ai
+Requires-Dist: anthropic>=0.40; extra == "ai"
+Provides-Extra: convert
+Requires-Dist: python-docx>=1.1; extra == "convert"
+Requires-Dist: pypdf>=4.0; extra == "convert"
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: ruff>=0.6; extra == "dev"
+Dynamic: license-file
+
+# docassert
+
+**Unit testing for business documents.** Validate structured Markdown documents
+(charters, BRDs, PRDs, risk registers, …) against a configurable audit standard:
+deterministic structural checks that gate a merge, plus optional AI-graded
+semantic checks that advise. Requirements trace end to end, and project status is
+derived from the documents rather than self-reported.
+
+docassert is the reference implementation of **[PMO as Code](https://c4g-john.github.io/pmo-as-code/)** —
+a vendor-neutral standard for running a PMO from version-controlled, declarative files.
+
+## Install
+
+```bash
+pip install "docassert @ git+https://github.com/c4g-john/docassert"   # PyPI release coming
+# with the AI advisory extra:
+pip install "docassert[ai] @ git+https://github.com/c4g-john/docassert"
+```
+
+## Quickstart
+
+```bash
+docassert init                        # scaffold criteria/schema/profiles/templates into your repo
+docassert validate documents/**/*.md  # unit-test your documents
+docassert consistency                 # cross-document traceability + profile completeness
+docassert status --index              # derived RAG per project
+docassert pages --out _site           # a portfolio dashboard + a page per project
+```
+
+Config resolves **local override → packaged default**: docassert ships sensible
+defaults, and your repo's own `criteria/` (or `schema/`, `profiles/`,
+`consistency.yaml`) wins when present. `docassert init` copies the defaults in so
+you can customize them.
+
+## Commands
+
+| Command | What it does |
+|---|---|
+| `docassert validate <globs>` | Validate documents against their kind's criteria. Exit code = number of blocking failures. |
+| `docassert consistency` | Cross-document checks: referential integrity, coverage, required links, profile completeness. |
+| `docassert rtm [--project ID]` | Requirements traceability matrix (Markdown or CSV). |
+| `docassert status [--project ID] [--index]` | Derived project status (md / json / html). |
+| `docassert pages --out DIR` | Build the portfolio site (index + a page per project). |
+| `docassert projects [--out] [--check]` | Generate / verify the project registry. |
+| `docassert init [DIR]` | Scaffold the default config into a repo. |
+
+## Document kinds
+
+Twenty kinds, each a `templates/<kind>.template.md` + `schema/<kind>.schema.json`
++ `criteria/<kind>.criteria.yaml` trio: `project`, `charter`, `business-case`,
+`brd`, `prd`, `frnfr`, `user-story`, `test-cases`, `adr`, `risk-register`,
+`raci-stakeholder`, `qa-test-plan`, `data-migration-plan`,
+`release-cutover-plan`, `rollback-plan`, `hypercare-plan`, `runbook`,
+`status-report`, `post-implementation-review`, `benefits-realization`. Adding a
+kind is adding a trio — no code for the common cases.
+
+## Two tiers of checks
+
+- **Structural — deterministic, blocking.** Required fields and sections,
+  measurable success criteria, risks with owner + mitigation, resolving
+  references, unique ids. Plain Python, reliable enough to gate a merge.
+- **Semantic — AI-graded, advisory.** Scored via the Anthropic API and posted to
+  the PR — never blocking. Set `ANTHROPIC_API_KEY` to enable; skipped otherwise.
+
+## Development
+
+```bash
+python3 -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+pytest
+ruff check .
+```
+
+This repo ships example `documents/` (four sample projects) that the test suite
+validates against.
+
+## The reference deployment
+
+[**pmo-as-code-pipeline**](https://github.com/c4g-john/pmo-as-code-pipeline) is a
+living example — sample projects, the gate on every pull request, and a published
+dashboard at
+[c4g-john.github.io/pmo-as-code-pipeline](https://c4g-john.github.io/pmo-as-code-pipeline/).
+The standard's site is [c4g-john.github.io/pmo-as-code](https://c4g-john.github.io/pmo-as-code/).
+
+## License
+
+Apache-2.0 — see [LICENSE](LICENSE) and [NOTICE](NOTICE). © 2026 C4G Enterprises Inc.

docassert-0.1.0/README.md

@@ -0,0 +1,87 @@
+# docassert
+
+**Unit testing for business documents.** Validate structured Markdown documents
+(charters, BRDs, PRDs, risk registers, …) against a configurable audit standard:
+deterministic structural checks that gate a merge, plus optional AI-graded
+semantic checks that advise. Requirements trace end to end, and project status is
+derived from the documents rather than self-reported.
+
+docassert is the reference implementation of **[PMO as Code](https://c4g-john.github.io/pmo-as-code/)** —
+a vendor-neutral standard for running a PMO from version-controlled, declarative files.
+
+## Install
+
+```bash
+pip install "docassert @ git+https://github.com/c4g-john/docassert"   # PyPI release coming
+# with the AI advisory extra:
+pip install "docassert[ai] @ git+https://github.com/c4g-john/docassert"
+```
+
+## Quickstart
+
+```bash
+docassert init                        # scaffold criteria/schema/profiles/templates into your repo
+docassert validate documents/**/*.md  # unit-test your documents
+docassert consistency                 # cross-document traceability + profile completeness
+docassert status --index              # derived RAG per project
+docassert pages --out _site           # a portfolio dashboard + a page per project
+```
+
+Config resolves **local override → packaged default**: docassert ships sensible
+defaults, and your repo's own `criteria/` (or `schema/`, `profiles/`,
+`consistency.yaml`) wins when present. `docassert init` copies the defaults in so
+you can customize them.
+
+## Commands
+
+| Command | What it does |
+|---|---|
+| `docassert validate <globs>` | Validate documents against their kind's criteria. Exit code = number of blocking failures. |
+| `docassert consistency` | Cross-document checks: referential integrity, coverage, required links, profile completeness. |
+| `docassert rtm [--project ID]` | Requirements traceability matrix (Markdown or CSV). |
+| `docassert status [--project ID] [--index]` | Derived project status (md / json / html). |
+| `docassert pages --out DIR` | Build the portfolio site (index + a page per project). |
+| `docassert projects [--out] [--check]` | Generate / verify the project registry. |
+| `docassert init [DIR]` | Scaffold the default config into a repo. |
+
+## Document kinds
+
+Twenty kinds, each a `templates/<kind>.template.md` + `schema/<kind>.schema.json`
++ `criteria/<kind>.criteria.yaml` trio: `project`, `charter`, `business-case`,
+`brd`, `prd`, `frnfr`, `user-story`, `test-cases`, `adr`, `risk-register`,
+`raci-stakeholder`, `qa-test-plan`, `data-migration-plan`,
+`release-cutover-plan`, `rollback-plan`, `hypercare-plan`, `runbook`,
+`status-report`, `post-implementation-review`, `benefits-realization`. Adding a
+kind is adding a trio — no code for the common cases.
+
+## Two tiers of checks
+
+- **Structural — deterministic, blocking.** Required fields and sections,
+  measurable success criteria, risks with owner + mitigation, resolving
+  references, unique ids. Plain Python, reliable enough to gate a merge.
+- **Semantic — AI-graded, advisory.** Scored via the Anthropic API and posted to
+  the PR — never blocking. Set `ANTHROPIC_API_KEY` to enable; skipped otherwise.
+
+## Development
+
+```bash
+python3 -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+pytest
+ruff check .
+```
+
+This repo ships example `documents/` (four sample projects) that the test suite
+validates against.
+
+## The reference deployment
+
+[**pmo-as-code-pipeline**](https://github.com/c4g-john/pmo-as-code-pipeline) is a
+living example — sample projects, the gate on every pull request, and a published
+dashboard at
+[c4g-john.github.io/pmo-as-code-pipeline](https://c4g-john.github.io/pmo-as-code-pipeline/).
+The standard's site is [c4g-john.github.io/pmo-as-code](https://c4g-john.github.io/pmo-as-code/).
+
+## License
+
+Apache-2.0 — see [LICENSE](LICENSE) and [NOTICE](NOTICE). © 2026 C4G Enterprises Inc.

docassert-0.1.0/docassert/__init__.py

@@ -0,0 +1,8 @@
+"""docassert — unit testing for business documents.
+
+Validate structured Markdown business documents against a configurable audit
+standard: deterministic structural checks that gate a merge, plus optional
+AI-graded semantic checks that advise.
+"""
+
+__version__ = "0.1.0"

docassert-0.1.0/docassert/__main__.py

@@ -0,0 +1,6 @@
+import sys
+
+from .cli import main
+
+if __name__ == "__main__":
+    sys.exit(main())

docassert-0.1.0/docassert/_data/consistency.yaml

@@ -0,0 +1,51 @@
+# Cross-document traceability rules.
+#
+# The chain: BR (business req) ◀ PR (product req) ◀ FR/NFR (spec)
+#            PR ◀ AC (acceptance criterion) ◀ TC (test case)
+#
+# Broken references are ALWAYS blocking. The rules below (required links and
+# coverage) block only when the owning document is `status: approved`, so
+# work-in-progress is never punished.
+
+# Each downstream item prefix must declare at least one target via this
+# relation (else it's an orphan).
+required_links:
+  PR: traces        # a product requirement must trace to a business requirement
+  FR: traces        # a functional requirement must trace to a product requirement
+  NFR: traces       # a non-functional requirement must trace to a product requirement
+  US: traces        # a user story must trace to a product requirement
+  AC: verifies      # an acceptance criterion must verify a requirement
+  TC: tests         # a test case must test an acceptance criterion
+
+# Every parent item (by prefix) must be covered by >=1 child of `by_prefix`
+# linking to it via `relation`.
+coverage:
+  - parent: BR
+    relation: traces
+    by_prefix: PR
+    label: business requirement covered by a product requirement
+  - parent: PR
+    relation: verifies
+    by_prefix: AC
+    label: product requirement covered by an acceptance criterion
+  - parent: AC
+    relation: tests
+    by_prefix: TC
+    label: acceptance criterion covered by a test case
+
+# Advisory AI alignment: for each relation, judge whether the child genuinely
+# fulfils the parent it links to. Never blocks.
+alignment:
+  - relation: traces
+    prompt: >
+      Judge whether the CHILD requirement genuinely refines or implements the
+      PARENT requirement it traces to, rather than being merely topically
+      related. Penalise links that don't actually follow from the parent.
+  - relation: verifies
+    prompt: >
+      Judge whether the acceptance criterion actually verifies the requirement
+      it targets: testable, and covering the requirement's intent.
+  - relation: tests
+    prompt: >
+      Judge whether the test case actually exercises the acceptance criterion
+      it targets.

docassert-0.1.0/docassert/_data/criteria/adr.criteria.yaml

@@ -0,0 +1,36 @@
+# Audit criteria for the Architecture Decision Record (ADR) kind.
+#
+# Modeled as a decision log: one document holds many **ADR-###** decision items,
+# each optionally affecting a requirement. (Distinct from the portfolio-level
+# "Decision" concept.)
+kind: adr
+
+required_sections:
+  - Overview
+  - Decisions
+
+item_sections:
+  - section: Decisions
+    prefix: ADR
+
+checks:
+  - id: frontmatter-schema
+    type: structural
+    blocking: true
+    description: Frontmatter is valid against schema/adr.schema.json.
+  - id: required-sections
+    type: structural
+    blocking: true
+    description: Every required section is present and non-empty.
+  - id: items-well-formed
+    type: structural
+    blocking: true
+    description: Every decision is a valid **ADR-###** item.
+  - id: adr-items-have-status
+    type: structural
+    blocking: true
+    description: Every decision declares a valid Status (proposed | accepted | superseded | deprecated | rejected).
+  - id: unique-id
+    type: structural
+    blocking: true
+    description: The document id is unique across documents/.

docassert-0.1.0/docassert/_data/criteria/benefits-realization.criteria.yaml

@@ -0,0 +1,30 @@
+# Audit criteria for the Benefits Realization kind.
+kind: benefits-realization
+
+required_sections:
+  - Overview
+  - Benefits
+  - Measurement
+  - Realized Value
+
+# Bullets in these sections must state a measurable threshold.
+measurable_sections:
+  - Benefits
+
+checks:
+  - id: frontmatter-schema
+    type: structural
+    blocking: true
+    description: Frontmatter is valid against schema/benefits-realization.schema.json.
+  - id: required-sections
+    type: structural
+    blocking: true
+    description: Every required section is present and non-empty.
+  - id: measurable-items
+    type: structural
+    blocking: true
+    description: Every benefit states a measurable target.
+  - id: unique-id
+    type: structural
+    blocking: true
+    description: The document id is unique across documents/.

docassert-0.1.0/docassert/_data/criteria/brd.criteria.yaml

@@ -0,0 +1,30 @@
+# Audit criteria for the Business Requirements Document (BRD) kind.
+kind: brd
+
+required_sections:
+  - Purpose
+  - Business Requirements
+  - Out of Scope
+
+# Sections whose bullets are traceable items.
+item_sections:
+  - section: Business Requirements
+    prefix: BR
+
+checks:
+  - id: frontmatter-schema
+    type: structural
+    blocking: true
+    description: Frontmatter is valid against schema/brd.schema.json.
+  - id: required-sections
+    type: structural
+    blocking: true
+    description: Every required section is present and non-empty.
+  - id: items-well-formed
+    type: structural
+    blocking: true
+    description: Every Business Requirement is a valid **BR-###** item.
+  - id: unique-id
+    type: structural
+    blocking: true
+    description: The document id is unique across documents/.

docassert-0.1.0/docassert/_data/criteria/business-case.criteria.yaml

@@ -0,0 +1,23 @@
+# Audit criteria for the Business Case kind.
+kind: business-case
+
+required_sections:
+  - Problem Statement
+  - Options Considered
+  - Recommendation
+  - Costs
+  - Benefits
+
+checks:
+  - id: frontmatter-schema
+    type: structural
+    blocking: true
+    description: Frontmatter is valid against schema/business-case.schema.json.
+  - id: required-sections
+    type: structural
+    blocking: true
+    description: Every required section is present and non-empty.
+  - id: unique-id
+    type: structural
+    blocking: true
+    description: The document id is unique across documents/.