Skip to content

rfc: implementation status — DX-0/1/2 complete, DX-3 next (design first)#28

Merged
ryandmonk merged 1 commit into
mainfrom
docs/dx-status-tracker
Jul 22, 2026
Merged

rfc: implementation status — DX-0/1/2 complete, DX-3 next (design first)#28
ryandmonk merged 1 commit into
mainfrom
docs/dx-status-tracker

Conversation

@ryandmonk

Copy link
Copy Markdown
Contributor

Post-DX-2 tracker update to the accepted RFC, as directed:

  • ✅ DX-0 / ✅ DX-1 / ✅ DX-2 recorded with one-line completion evidence; ▶ DX-3 marked next, design-first.
  • The emitter-profile correction is inherited by the roadmap: ADOPTING.md + PROFILES.md become canonical over the RFC's earlier in-repo-profile assumption.
  • The four walkthrough findings are preserved as DX-3 design inputs (standalone validation surfacing, export publish/v0.4 bottleneck, output-naming surprise, the snapshot→enrich preservation invariant), explicitly separated from any implementation.

Docs only; no DX-3 implementation.

🤖 Generated with Claude Code

Records milestone completion, the emitter-profile correction the roadmap
inherits from DX-2 (profiles are external data; the guides are canonical
over this RFC's Sec 2 step 12 where they disagree), and the four DX-3
design inputs extracted from the guide walkthrough — evidence separated
from implementation, per the RFC's own design-first DX-3 definition.

Co-Authored-By: Claude Fable 5 <[email protected]>
Copilot AI review requested due to automatic review settings July 22, 2026 19:34
@ryandmonk
ryandmonk merged commit 0864dee into main Jul 22, 2026
2 checks passed

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the DX adoption RFC to record post–DX-2 completion evidence, clarify which documents are canonical for emitter profiles/adoption, and preserve DX-2 walkthrough findings explicitly as DX-3 design inputs (without adding any DX-3 implementation).

Changes:

  • Adds an “Implementation status” section with a DX-0–DX-3 status table and dated update.
  • Documents a roadmap correction: adopter profiles are authored in consumer codebases against the published package, with ADOPTING.md / PROFILES.md as canonical.
  • Captures four DX-2 walkthrough findings as explicit DX-3 design inputs, separated from implementation.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread rfc/dx-adoption-review.md
| DX-2 · The adoption guide | ✅ Complete — [`ADOPTING.md`](../ADOPTING.md) (12 steps, each labeled automated / human review / design decision) and [dspack-emit `docs/PROFILES.md`](https://github.com/aestheticfunction/dspack-emit/blob/main/docs/PROFILES.md); verified by executing the guide end to end from clean checkouts, with the walkthrough's clarifications folded back before completion. |
| DX-3 · Bootstrap parity | ▶ Next — **design first, then code**, per this RFC's DX-3 definition. |

### Correction the roadmap inherits (from DX-2)
Comment thread rfc/dx-adoption-review.md
|---|---|
| DX-0 · Ops debt | ✅ Complete — ds-mcp 0.3.2 released on the exact dspack-gen v0.1.2 tag commit; studio range mismatch resolved (stale drift, not isolation); all synchronization and pin-drift signals green. |
| DX-1 · Truth & wayfinding | ✅ Complete — D1–D7 resolved (D4 via compatibility-aware rename); breadcrumb + charter in every public README; studio backlinked; ds-mcp docs single-sourced; owner decision recorded: **aesthetic-function is paused**. All links and quick-starts executed from clean environments. |
| DX-2 · The adoption guide | ✅ Complete — [`ADOPTING.md`](../ADOPTING.md) (12 steps, each labeled automated / human review / design decision) and [dspack-emit `docs/PROFILES.md`](https://github.com/aestheticfunction/dspack-emit/blob/main/docs/PROFILES.md); verified by executing the guide end to end from clean checkouts, with the walkthrough's clarifications folded back before completion. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants