Define short-lived Go build-tag rollback levers for Ward extraction work #1268

Open
opened 2026-07-14 10:08:13 +00:00 by coilyco-ops · 0 comments
Member

Decision

Go, from coilysiren/inbox#211 follow-up.

Use short-lived Go build tags as rollback levers during Ward extraction work. These are compile-time switches such as //go:build legacy_profile, not git tags or release tags.

Scope

  • Define the allowed transitional build tags and their owner/removal condition.
  • Initial candidates: legacy_cli, legacy_ops, and legacy_profile.
  • Use tags only to preserve a working adapter or fallback while a seam is being cut.
  • Document which CI jobs build the default path and which jobs, if any, prove the legacy path still compiles during the transition.
  • Add removal tickets or explicit acceptance criteria so the tags expire after the relevant extraction step lands.

Non-goals

  • Do not use build tags as permanent architecture.
  • Do not hide default behavior behind non-default tags.
  • Do not use git tags, release tags, or branch labels for this purpose.
  • Do not add the tags before there is an actual extraction change that needs a rollback lever.

Parent: coilysiren/inbox#211.
Related: coilyco-flight-deck/ward#1245, coilyco-flight-deck/ward#1246, coilyco-flight-deck/ward#1247, coilyco-flight-deck/ward#1265.

## Decision Go, from coilysiren/inbox#211 follow-up. Use short-lived Go build tags as rollback levers during Ward extraction work. These are compile-time switches such as `//go:build legacy_profile`, not git tags or release tags. ## Scope - Define the allowed transitional build tags and their owner/removal condition. - Initial candidates: `legacy_cli`, `legacy_ops`, and `legacy_profile`. - Use tags only to preserve a working adapter or fallback while a seam is being cut. - Document which CI jobs build the default path and which jobs, if any, prove the legacy path still compiles during the transition. - Add removal tickets or explicit acceptance criteria so the tags expire after the relevant extraction step lands. ## Non-goals - Do not use build tags as permanent architecture. - Do not hide default behavior behind non-default tags. - Do not use git tags, release tags, or branch labels for this purpose. - Do not add the tags before there is an actual extraction change that needs a rollback lever. Parent: coilysiren/inbox#211. Related: coilyco-flight-deck/ward#1245, coilyco-flight-deck/ward#1246, coilyco-flight-deck/ward#1247, coilyco-flight-deck/ward#1265.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/ward#1268
No description provided.