Antora Tracer — Self-Traceability Example

Tracer Spec Workflow

    • Home
    • Getting Started
    • How-to Guides
      • How to scaffold a project
      • How to drive the workflow
    • Reference
      • CLI
      • Skills
      • Roles
      • Configuration
    • Explanation
      • Workflow
      • Traceability
    • Changes
    • Requirements
    • Decisions
Tracer Spec Workflow
  • Antora Tracer
    • main
    • 0.25
    • 0.24
  • Blog
    • 0.1
  • Demo
    • main
  • Tracer Spec Workflow
Edit this Page
REQ-020 — Record requirements as observable behaviour, not mechanisms

The system SHALL record each proposed requirement as observable behaviour, with any mechanism it names recorded as a decision instead.

Addressed by

  • CHG-009 — Gate proposed requirements against implementation detail

This page was built using the antora-ui-conemso theme

Built from 3191517.

Source: branch/main@https://github.com/antora-tracer/tracer-spec.git(486bca50511de51c04810dbf3480396707fdc2c9)

The source code for this UI is licensed under the terms of the MPL-2.0 license.