A shared vocabulary for architecture

Architecture should mean the same thing everywhere.

A portable way to express architectural intent across teams, tools, and environments.

Keep the meaning stable while implementations evolve.

Token library · security

security.encryption.at-rest

applied
kind: token-library
namespace: security
domains: [security]
version: 0.1.0
name: Security
tokens:
  - id: security.encryption.at-rest
    kind: applied
    name: Encryption at rest
    description: Stored data is encrypted.
    appliesTo:
      elementKinds: [component]
      componentTypes: [common:database]
    valueSchema:
      type: object
      required: [algorithm]
      properties:
        algorithm: {type: string}

Stable meaning, flexible implementation

One meaning. Many implementations.

The architectural intent stays constant while each environment chooses an implementation that satisfies it.

Architecture intentStored data is encryptedsecurity.encryption.at-rest
  • AWSRDS encryptionKMS-backed storage
  • AzureAzure SQL TDETransparent data encryption
  • Google CloudCloud SQL encryptionEncrypted storage

The v0.1 premise

A vocabulary built to travel.

  • 01
    Shared meaning

    People and tools interpret the same architectural intent.

  • 02
    Vendor neutral

    Implementation choices do not own the vocabulary.

  • 03
    Composable

    Tokens combine into architecture models that can be checked.

Open specification

Help shape the vocabulary.

Architecture Tokens is an open draft. Review it, challenge it, and extend it with real architecture work.

Contribute on GitHub