Skip to content

docs: drop the Orchestrate principle and scope the upstream rule - #572

Merged
Tryanks merged 1 commit into
mainfrom
docs/principles-upstream-scope
Oct 1, 2026
Merged

Tryanks merged 1 commit into
mainfrom
docs/principles-upstream-scope

Conversation

@Tryanks

@Tryanks Tryanks commented Oct 1, 2026

Copy link
Copy Markdown
Owner

Changes

  • Removes principle 6 (Orchestrate is core). The WASM plugin roadmap is a long-term plan, not a development constraint. Principles 7–9 become 6–8, and the one reference by number ("Principle 9 governs anything beyond this repository") now points to 8.
  • Narrows the upstream principle (now 8). A problem caused by Tcode (its code, its tests, or how it uses a dependency) is fixed where it is found, as part of the current work. Only a problem caused by the upstream itself is carried and reported. The rest of the principle is unchanged.
  • Localize step in "Problems that may be a dependency's". It now says that when the cause is Tcode's, you fix it and stop; the later steps apply only when the cause is in the dependency.

Checks

This changes documentation only, with no code or tests. CI runs the full suite on this push.

Orchestration's plugin roadmap is a long-term plan, not a development
constraint, so it leaves Principles; the remaining principles are
renumbered and the one cross-reference follows.

The upstream principle now separates the two cases: a problem whose cause
lies within Tcode is fixed where it is found as part of the work at hand;
only a cause in the upstream itself is carried and reported. The
dependency-problem procedure's Localize step says the same.
@Tryanks
Tryanks merged commit 860f66c into main Oct 1, 2026
7 checks passed
@Tryanks
Tryanks deleted the docs/principles-upstream-scope branch October 1, 2026 18:58
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