Skip to content

docs(adr): adopt released truth for public documentation - #98

Draft
JimCollinson wants to merge 26 commits into
mainfrom
adr/released-and-usable-truth
Draft

docs(adr): adopt released truth for public documentation#98
JimCollinson wants to merge 26 commits into
mainfrom
adr/released-and-usable-truth

Conversation

@JimCollinson

@JimCollinson JimCollinson commented Aug 20, 2026

Copy link
Copy Markdown
Member

Summary

Proposes ADR-0016: public developer documentation and the published developer skill should default to stable, obtainable, compatible, capability-evidenced released truth rather than moving default-branch source.

Jim selected one coherent active release set with journey-local support status: working interfaces remain documented, failed journeys are withdrawn or marked unsupported, and older release fallback is global rather than per journey.

Scope

This draft PR contains only the Proposed ADR, its dated v0.11.2 motivating audit, GSD state/checkpoint material, and branch-local review evidence. It does not implement the policy, update rendered documentation or the skill, accept the ADR, or authorize a merge.

Current evidence

  • ADR governance and 20 governance tests pass locally.
  • Exact-head ADR Governance and GitBook checks pass on this draft PR.
  • Prose/sweep checks return success as branch-scope no-ops, not substantive coverage.
  • Journey-local code review passed at b1e4846.
  • Journey-local goal verification passed 10/10 at 39e2cdf.
  • Review reports are committed under planning/.

Current status: NOT-READY

Adversarial review at ef646b9 found two remaining blockers:

  1. A complete SDK route must preserve continuity below the top-level SDK label so incompatible bindings or transports cannot be combined.
  2. ADR-0016 must precisely supersede ADR-0011’s unconditional SDK-primary stance if CLI can remain the only recommended complete route.

The review also requests a concrete, clause-derived route truth table. These findings are recorded in planning/adr-0016-adversarial-ef646b9.md.

Known limitations and next gates

  • ADR-0016 remains Proposed and requires Jim Collinson’s explicit acceptance.
  • A fresh release audit is required before implementation; the included v0.11.2 audit is historical evidence only.
  • Craft Review and clean-context review remain pending until adversarial review passes.
  • No merge or implementation action is authorized by this draft PR.

- Supersede released source-resolution and drift semantics\n- Add branch-local v0.11.2 audit evidence
- Disqualify incumbents that no longer meet released baseline requirements
- Relabel unverified Python and Rust source-install routes
- Define stable candidate eligibility, deterministic ordering, and symmetric requalification

- Bound supersession, skill parity, release identity, and validation invariants
- Define deterministic fallback and complete incumbent requalification triggers

- Pin authoritative installs and constrain mutable aliases
- Treat fetched skill pointers as untrusted factual input\n- Keep mutable aliases unsupported and non-authoritative
- Keep one coherent active release set with journey-local support statuses\n- Define complete-route baseline, deterministic fallback, and parity rules
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.

1 participant