Skip to content
Beskid Platform specification

Beskid

Jump to a Beskid service

Beskid

Jump to a Beskid service

Domain, Area, Feature, and Article frontmatter templates

Use these templates when creating new platform-spec nodes. They match current CI validators and trudoc Zod contracts.

---
title: <Domain title>
description: <Domain summary>
specLevel: domain
owner:
name: <Owner name>
email: <owner@example.com>
submitter:
name: <Submitter name>
email: <submitter@example.com>
relatedTopics: []
---
---
title: <Area title>
description: <Area summary>
specLevel: area
owner:
name: <Owner name>
email: <owner@example.com>
submitter:
name: <Submitter name>
email: <submitter@example.com>
relatedTopics: []
---
---
title: <Feature title>
description: <Feature summary>
specLevel: feature
status: Standard
owner:
name: <Owner name>
email: <owner@example.com>
submitter:
name: <Submitter name>
email: <submitter@example.com>
relatedTopics: []
---
---
title: <Article title>
description: <Article summary>
specLevel: article
status: Standard
owner:
name: <Owner name>
email: <owner@example.com>
submitter:
name: <Submitter name>
email: <submitter@example.com>
relatedTopics: []
---
  • status is required for feature and article.
  • status is not allowed on domain or area.
  • owner and submitter must include non-empty name and valid email.
  • Use layout.json for every domain/area/feature hub directory.

No open decisions. Closed maintenance ADR under adr/D-COMM-META-0001 (reader ADRs tab).