# Engineering Standards

The engineering standards an implementation artifact may cite in `standards[]` (CONVENTIONS §10.4). Each lives in its repository; this registry names it once so an artifact cites an id, never a copy (one home per fact). Tribal keeps its cross-cutting standards under its implementation corpus as `system/` documents; Rhythm's live with the code that enforces them, and this table is the corpus's index of them.

| Id | Title | Lives at | Governs |
|---|---|---|---|
| `STD-DEP` | Macroservice dependency architecture | `services-platform:docs/standards/macroservice-dependency-architecture.md` | Which service may depend on which; Platform, CRM, Accounting, Commerce, Membership in order; everything above is peers |
| `STD-WRITE` | Record write contracts | `services-platform:docs/standards/record-write-contracts.md` | How a record is created, changed, archived and deleted through one contract; refusals, stamps, history |
| `STD-SUBMIT` | Submission-compatible operations | `services-platform:docs/standards/submission-compatible-operations.md` | The operation shape published to Submissions (R2-ARCH-002) |
| `STD-CUSTOM` | Custom field capability | `services-platform:docs/standards/custom-field-capability.md` | How a module declares objects that carry custom fields, layouts and forms |
| `STD-BASELINE` | Baseline configuration | `services-platform:docs/standards/baseline-configuration.md` | The configuration every workspace starts with and how a module contributes to it |
| `STD-MILESTONE` | Milestone development and acceptance | `services-platform:docs/standards/milestone-development-and-acceptance.md` | How a milestone is planned, built, tested and accepted |
| `STD-TEST-SVC` | Service testing standard | `services-crm:docs/platform-testing-standards.md` and each module's `tests/README.md` | The four tiers of a macroservice module's tests, how a spec is written, refusals by mechanism, own data only |
| `STD-TEST-UI` | Console acceptance testing | `react-console:acceptance/crm/playwright/README.md` and `product-acceptance-testing/references/playwright-architecture.md` | The Playwright acceptance suite: personas, guardrails, run markers, one spec per catalogue journey, independent verification through the APIs |
| `STD-V0` | Driving v0 | `react-console:scripts/v0/README.md` | How a screen prompt is run against v0, its cost rules and the one project every chat belongs to |