Facts and Taxonomy

RWS Architecture folder

Facts provide stable constraints and shared vocabulary that architecture and ADRs rely on.

RWS Architecture Vault / Facts and Taxonomy

  1. Direct notes12
  2. Folders0
  3. Articles12
  4. Statusactive

Rendered folder index

Direct articles in this section

Folders and articles are both available in the left browser. This panel promotes actual notes first.

index
fact / activeArchitecture model sidecars

Architecture roadmap metadata lives in `.model.yaml` sidecar files next to, or near, the human-facing Markdown note. The Markdown note remains the narrative source for architects a

fact / activeFact Definition and Boundary

Facts are stable truths that architecture and decisions rely on.

fact / activeOpenShift Platform — Hardware Specs (Node BOM)

Validated hardware bill-of-materials (BOM) for OpenShift platform node types.

index / activeFacts Catalog

This page is the complete inventory of notes under `40-facts/`.

fact / activePull Request Preview Access

Pull request preview sites for `rws-arch-wb` use HTTP Basic authentication.

index / activeVault Taxonomy

This note defines the core vocabulary used in the RWS Architecture Vault: note types, statuses, and how `domain` is used.

fact / activeWay of Working — RWS Architecture Vault

**How We Document, Decide, and Not Make a Total Mess**

fact / activeWorkflow - Architecture Promotion Checklist

Use this checklist to move architecture notes through maturity with low overhead.

fact / activeWorkflow - Change Existing Architecture and Deprecate Safely

Use this when architecture already exists and you need to introduce a new dynamic while preserving history and traceability.

fact / activeWorkflow - Draft Architecture First

Use this when final architecture feels too heavy to start. The goal is to lower the barrier: create a small, valid architecture draft early, then evolve it.

fact / activeWorkflow - New Capability to Final Architecture

Use this when a capability does not yet exist in the vault and you need to go from idea to an approved architecture.

fact / activeZero Trust Network Access (ZTNA)

Zero Trust Network Access (ZTNA) is an identity-aware access approach that grants access to specific applications and services instead of broad network-level connectivity.

Facts provide stable constraints and shared vocabulary that architecture and ADRs rely on.

Purpose

  • Keep reusable facts, taxonomy, and governance conventions in one stable place.
  • Provide a curated entrypoint for contributors and reviewers.
  • Link to inventory views without duplicating detailed catalogs here.

Start Here

Quick Workflows

Key Fact Notes