Skip to main content

​
Adoption guide

Adoption should reduce context, not add another layer of duplicate rules.

​
New repository

Start with the canonical templates from: github.com/datarelay-labs/engineering-system Base adoption requires:
Pin the Engineering System version used by the repository. If you use Cursor and session continuity, add the tool adapter and continuity files separately:
This distinction matters: base engineering governance and AI session continuity are related, but not the same feature.

​
Existing repository with many AI rules

Do not blindly add another always-on rule. First classify the existing rules:
Keep product-specific invariants and stricter valid rules. Move generic duplicated engineering guidance back toward the canonical Engineering System so Cursor context becomes smaller rather than larger.

​
Adoption-pending repositories

A valid Work Packet may exist before the repository has completed Engineering System adoption. When AGENTS.md or .engineering/* are missing during resume:
  • record ENGINEERING_SYSTEM_ADOPTION=ABSENT_OR_PENDING
  • continue under the canonical Engineering System default when the Work Packet is otherwise valid
  • do not silently create, merge, or modify adoption files unless the active workstream explicitly authorizes adoption work
This lets release or feature work continue without accidentally mixing governance adoption into the product change.

​
Install the Cursor user /resume command

On the machine running Cursor:
Then /resume can be used in any adopted repository.

​
Add ChatGPT routing, not the whole standard

ChatGPT Custom Instructions should stay short. They only need to say:
  • use the canonical Engineering System
  • resolve the repository first
  • use Work Packets for Cursor handoff and chat continuity
  • read only minimal relevant context
  • never claim unexecuted or different-HEAD evidence as PASS
Do not copy every Engineering System standard into Custom Instructions.

​
Optional: connect Desktop Commander

For direct development-host audit, connect Desktop Commander Remote MCP and restrict it to the intended development paths. This is optional. GitHub remains the durable baseline even when remote audit is available.

​
Adoption success test

A simple smoke test is enough:
If the same workstream resumes without copying a large prompt, the continuity path is working.
Last modified on September 19, 2026