Help us shape the future of Go! Take the 2026 Go Developer Survey

payments-engineering-sample/

directory
v0.6.0 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Oct 30, 2026 License: MIT

README

Sample Layered Architecture + EARS Project

This sample demonstrates the new layered architecture direction where authored design is stable and runtime/code realization is inferred.

Authored architecture centers on:

  • Functional Groups (FG-*)
  • Functional Units (FU-*)
  • Actors
  • Attack Vectors
  • Referenced Elements

Inferred layers are represented by example ownership and runtime hints:

  • Runtime inferred from infra/terraform, infra/flux, infra/helm
  • Code ownership inferred from package/module-level owner annotations in src/
  • Fine-grained requirement traces from TRLC-LINKS markers in code
  • Verification mappings and outcomes inferred from tests/ and test-results/ artifacts

The implementation files are intentionally dummy but believable:

  • they include trace markers for requirement linkage
  • they include coarse ownership markers for FU mapping
  • they log/print expected actions in each subsystem
  • they are meant for documentation and traceability, not production execution

Story highlights:

  • checkout and authorization are authored in FG-PAYMENTS
  • risk scoring and support review are authored in FG-FRAUD
  • cluster provisioning and GitOps operations are authored in FG-PLATFORM
  • Flux/Terraform artifacts annotate ownership upward with engmodel.dev/owner-unit

Files

  • engmod.yml
  • model/catalog.yml
  • model/requirements.yml
  • model/architecture.yml
  • model/behavior.yml
  • model/assurance.yml
  • model/compliance.yml
  • model/views.yml
  • model/decisions.yml
  • infra/terraform/main.tf
  • infra/flux/...
  • infra/helm/...
  • src/...
  • tests/... (sample e2e/integration/contract verification fixtures)
  • tests/unit/... (sample code-level unit verification fixtures)
  • test-results/... (sample run artifacts mapped to requirements)

Note:

  • This example is intentionally synthetic and focuses on documentation/traceability behavior.
  • Verification artifacts are sample fixtures intended to demonstrate requirement-to-test-to-result mapping.

Upstream References

These are known working upstream projects/docs for the same stack:

Directories

Path Synopsis
ENGMODEL-OWNER-UNIT: FU-CHECKOUT ENGMODEL-CODE-DESCRIPTION: accepts checkout requests and forwards payment authorization flow input
ENGMODEL-OWNER-UNIT: FU-CHECKOUT ENGMODEL-CODE-DESCRIPTION: accepts checkout requests and forwards payment authorization flow input

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL