Skip to content

Add the ecosystem-resolution contract, its decision record and the review rule #15706

Closed

Description

@kyle-sexton

Parent

Refs #15703
Source: PLAN Phase 3, topic ecosystem-specifics

Depends on

  • none: on the frontier now

Outcome

The ecosystem-resolution contract exists with its generic resolution text, one decision record explains why ecosystem specifics are resolved from the consumer repository, and the review rules hold new skills to both. Docs only; no skill text changes.

Demo: open the new contract and its generic text; the review rules for skills and agents show the two new bullets.

What lands:

  • A new ecosystem-resolution contract: run kinds and their detector, the resolution procedure, the recording rule, the record table, the carrier rule, and versioning (a wording change is a patch, a guardrail change is a major). Its seven-step generic text holds no relative link. A changelog with a first entry.
  • One decision record, written through /architecture:record-decision, taking the next free number when its pull request is ready to merge: resolve ecosystem specifics from the consumer repository, ship no bundled default, keep executed adapters. It holds the classification rules and their named exceptions, which the review rule cites, and covers two one-way doors: the contract itself and deleting toolchain's nine bundled files. Its file name carries the word ecosystem-specifics.
  • The skills-and-agents review rules gain two bullets: no model-read language, framework or tool specific in a generic skill outside the named exceptions; a new skill that recommends, places or builds enforcement or an instruction reads the ladder, prefers the strongest tier that can decide, and discovers the consumer's tooling first.
  • The plugin philosophy doc: the consumer-tool port exception, the two-lane note and the registry entry.
  • The migration playbook: an unresolved report replaces the generic default for consumer-tool seams; "a merged pull request counts as acceptance" for ecosystem records only.
  • The standards contract: carriers are readers of the paved-path entry; the same acceptance sentence, ecosystem records only.

Decisions

  • Owner, 2026-11-12 (Q5): one decision record, not four. The verification tier's reason and the renamed public ids go in the ladder's 3.0.0 changelog entry, which the ladder's versioning rule already requires; they get no record.
  • D13: public names ecosystem-resolution and carrier (a plugin holding a synced copy of a contract text).
  • Q42: a plugin is a carrier of the generic text only while one of its skills still takes a language-specific step after its cut; it joins or leaves in the pull request that changes that fact.
  • Design Q23: the resolution procedure gets its own contract; the ecosystem-commands contract keeps the record's schema and examples and is not widened.

Key interfaces

  • "ecosystem-resolution (new): the README plus the generic resolution text that carrier plugins hold as a synced copy. It owns the procedure for finding a consumer's language, framework, tool and library choices."
  • Conventions followed: the contract-plus-synced-copy style; the plugin philosophy rule that a cross-plugin reach is a presence-gated slash reference.

Done when

  • AC10: the review rules hold every new skill that recommends, places or builds enforcement or an instruction to: read the ladder, prefer the strongest tier that can decide the matter, and discover the consumer's tooling first (the phrase "strongest tier" appears once).
  • The contract's README and generic text exist, and the generic text holds no relative link.
  • Exactly one decision record whose name carries ecosystem-specifics exists.
  • The change touches no file under plugins/.
  • AC7: nothing is cut here, so no control result is owed.

Out of scope

  • Any skill or agent text.
  • Registering carrier rows in the shared-copies list (later items).
  • Decision records for the verification tier or the public ids.

Activity

  1. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 12, 2026
  2. added theissue type on Nov 12, 2026
  3. melodic-automation-lanes commented on Nov 13, 2026

    @melodic-automation-lanes
    Contributor

    No work-resolve-issue run started in the 1 hour since agent-ready was last added. work-unblock removed and added agent-ready back to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.

  4. removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 13, 2026
  5. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    Size: Medium
    Complexity: Medium
    Uncertainty: Known
    Flags: none
    Blocked by: none

    Understood: a docs-only change that adds the ecosystem-resolution contract (README, generic text, changelog), one ecosystem-specifics decision record, two review-rule bullets, and edits to the philosophy doc, migration playbook and standards contract. Nothing under plugins/ changes.

    The scope and done-when items are exact, so I found no open design question. A comment says #15846 merged with Refs: on this issue. It is not in my merged-pulls list, and I found no contract or ecosystem-specifics record in the checkout. I could not tell what that pull request left undone. A maintainer may want to confirm that before work starts.

    I found no open duplicate.

    Automated triage. A maintainer reviews it.

  6. melodic-automation-lanes commented on Nov 13, 2026

    @melodic-automation-lanes
    Contributor

    {"v":1,"actor_id":337595936,"title_sha256":"89bc7330521ac71f346eb8214facd6d07edff4789666af0fcdbbdf48e2eac370","body_sha256":"ee5230b2bfe40a7b1e21dbe2fcfb6a50400efb082d4ff4518e9420654a84ae9a"}

  7. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor
    No description provided.
  8. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor
    No description provided.
  9. self-assigned this
    on Nov 13, 2026
  10. kyle-sexton commented on Nov 13, 2026

    @kyle-sexton
    MemberAuthor
    No description provided.
  11. removed their assignment
    on Nov 13, 2026
  12. melodic-automation-lanes commented on Nov 13, 2026

    @melodic-automation-lanes
    Contributor

    Pull request #15846 merged with Refs:, so this issue stays open and nothing starts the lane on it again. work-unblock removed status: ready and agent-ready, so the hourly triage sweep sends it back to intake triage. Admission then parks it at status: confirmed for a check of what that pull request left, until a **Decision recorded.** comment says what is left or someone closes it.

  13. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    The triage sweep dispatched intake triage for this issue (dispatch 1; 2 runs that reach intake, or 6 dispatches, hand it to a maintainer).

  14. melodic-automation-lanes commented on Nov 13, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane: merged pull request #15846 names it with Refs: after its newest decision or refinement comment, so its work may already be done: close the issue if it is, or post a comment whose first line is **Decision recorded.** saying what is left, which sends it back through intake. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).

  15. kyle-sexton commented on Nov 14, 2026

    @kyle-sexton
    MemberAuthor

    Closing as completed: every Done-when item holds on main after pull request 15846 (merge commit 1eae868770). Checked against origin/main by an agent and re-read by the hub session on 2026-11-13.

    • AC10: docs/review/skills-and-agents.md lines 18-22 hold the rule that a new skill which recommends, places or builds enforcement, or an instruction, reads the enforcement ladder, prefers the strongest tier that can decide the matter, and discovers the consumer's tooling first. "strongest tier" appears once in the repository (line 19).
    • The contract exists: docs/contracts/ecosystem-resolution/README.md, generic-resolution.md (seven steps, no Markdown link of any kind) and CHANGELOG.md (1.0.0).
    • Exactly one decision record carries ecosystem-specifics: docs/adr/0101-resolve-ecosystem-specifics-from-the-consumer-repository.md.
    • The pull request changed seven files, all under docs/, none under plugins/.
    • AC7: no skill or agent text was cut, so no control result is owed.

    Not done here, and not a Done-when item: the "What lands" bullet for the standards contract (docs/contracts/standards/README.md: carriers are readers of the paved-path entry, plus the merged-pull-request acceptance sentence for ecosystem records only). That file is synced into plugins/planning, plugins/review and plugins/improvement (scripts/shared-copies.txt lines 89, 90, 96), so it could not land under this item's no-plugins/ rule. It is noted on the container, 15703, as work its spec still owes.

    Agent action by the hub session (GitHub Support), not an owner answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Work status

    confirmed

    Priority

    low

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions