From f4d48e247d703bd0b858355062977fe304821dca Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Sat, 15 Aug 2026 17:17:23 -0400 Subject: [PATCH] docs: permit a time-boxed parallel packaging evaluation Section 10 said "native packaging and runtime contracts stay local to their host." Read literally that forbids a single package set spanning two hosts, including one built only to assess whether a cross-host packaging format is worth adopting. That is the one sentence blocking a decided evaluation, so this adds a carve-out scoped to assessment and nothing wider. The change is additive. No existing sentence is edited or removed, so both standing prohibitions survive verbatim: no repository is generated from another at install time, and no automatic synchronization is introduced. The carve-out restates both, adds the runtime cross-loading prohibition that PLUGIN-PHILOSOPHY already carries, and requires every host repository to stay the source of truth for its host with its native catalog retained. Retirement is explicitly NOT authorized here. The carve-out names the gate a later retirement amendment must clear: the section 8 matrix exercised per skill with evidence published per section 9, and every mapped trigger verified from a clean consumer repository. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Dm3XHznFdU1M4TysnJ26gu --- docs/MIGRATION-PLAYBOOK.md | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/docs/MIGRATION-PLAYBOOK.md b/docs/MIGRATION-PLAYBOOK.md index 753a453..d49552a 100644 --- a/docs/MIGRATION-PLAYBOOK.md +++ b/docs/MIGRATION-PLAYBOOK.md @@ -203,3 +203,34 @@ may be ported in either direction using this playbook, but no repository is generated from another at install time and no automatic synchronization is introduced. Shared concepts stay conceptual; native packaging and runtime contracts stay local to their host. + +### Evaluation carve-out: parallel packaging for assessment + +The packaging-locality sentence above has exactly one exception, and nothing +wider. A deliberate, hand-built, time-boxed parallel package set MAY be +produced in a separate evaluation repository to assess a cross-host packaging +format, when all of the following hold: + +- every existing host repository remains the source of truth for its host and + keeps its own manifests, releases, tests, and native adapters; +- every native marketplace catalog is retained, because a format that defines + no catalog or listing format does not replace one; +- the parallel set is built by hand and reviewed by a human, never emitted by + a tool that reads one repository and writes another; and +- the evaluation has a written end date and a named owner who reports the + outcome. + +Both prohibitions above continue to apply, to the evaluation set as much as to +anything else: no repository is generated from another at install time, no +automatic synchronization is introduced, and no host loads another host's +packages at run time. + +This carve-out authorizes assessment only. It does not authorize retiring a +host repository, merging host-specific content, collapsing plugins that share +a skill name across hosts, or dropping a native catalog. Retiring a host +repository is a separate decision and needs its own amendment, resting on +evidence that does not exist yet: the section 8 matrix exercised per skill +with the evidence published per section 9, and every mapped trigger verified +by invocation from a clean consumer repository. A package that loads is not a +package at parity; section 9 already forbids claiming parity for a component +that was dropped, replaced, or remains untested.