Documentation System

Summary: This guide defines how NEFE documentation is organized, maintained, and interpreted. It is the editorial source of truth for the documentation package.

#Purpose

NEFE Business Network is documented as a business-first commercial platform. Documentation should explain the commercial outcome first, then the workflow, data, and technology that support it.

#Capability labels

Every product statement must use one of these maturity labels when status could be ambiguous:

The frontmatter status field describes the documentation page, not every capability mentioned on it. Page content remains responsible for labeling capabilities accurately.

#Information architecture

• Getting Started introduces the network and adoption path.
• Platform explains core commercial concepts.
• Merchants covers merchant operations.
• Consumers covers customer experiences.
• Business covers commercial architecture and deployment.
• Ecosystem covers optional participation layers.
• Security covers controls, privacy, and access.
• Developers sets safe integration expectations.
• Reference provides definitions, changes, and answers.

#Authoring rules

1. Use sentence-case headings and plain business language.
2. Keep YAML frontmatter complete and accurate.
3. Use relative Markdown links and verify each target.
4. Never describe a proposed API, token mechanism, or automated decision as live.
5. Record material documentation changes in the changelog.

#Page frontmatter

---
title: Page title
summary: One-sentence description.
category: Platform
order: 1
status: live
updated: 2026-07-24
---

#Ownership and review

• Business owners validate commercial claims.
• Product owners validate capability status.
• Security owners validate control language.
• Documentation maintainers validate structure and links.

Release notes should identify changes without exposing confidential implementation details.