From 838f906a64133de8be1b312950d76fbe344c4a67 Mon Sep 17 00:00:00 2001 From: "Harol A. Reina H." Date: Fri, 25 Sep 2026 15:05:27 -0500 Subject: [PATCH] =?UTF-8?q?docs(openspec):=20say=20where=20work=20runs=20?= =?UTF-8?q?=E2=80=94=20this=20repo,=20or=20another=20repo=20via=20/xr:chan?= =?UTF-8?q?ge=20(verbara-meta/ADR-0023)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Rollout of the 2026-09-25 amendment to verbara-meta/ADR-0023, which carries the escalation half of the verbara-meta/ADR-0006 ruling (work runs where its commits land) on the one tracked channel that reaches every propose, apply and archive: context:. --- openspec/config.yaml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/openspec/config.yaml b/openspec/config.yaml index 03046ff5..8db81959 100644 --- a/openspec/config.yaml +++ b/openspec/config.yaml @@ -28,6 +28,14 @@ context: | Cross-repo standards (CI gating, context hygiene, branch protection) live in the private verbara-meta repo as ADRs. + Where work runs (verbara-meta/ADR-0006): a change whose commits land only in this repo is + proposed, applied and archived here. A change that needs a commit in another repo is hosted from + the verbara-meta cockpit via `/xr:change`, not here — if a change turns out to need one, record + the finding in `tasks.md` and recommend `/xr:change` before capturing more. + The hub rule (verbara-meta/ADR-0005) is unchanged and is not a cross-repo change for this rule: a + Web-behaviour change keeps its OpenSpec change in Verbara.Platform while its code lands in + Verbara.Platform.Web. + rules: proposal: - "Set a `tier` in frontmatter: GRANDE (cross-repo, >3 days, or a product decision), MEDIANO (one repo, 1-3 days), or PEQUEÑO (bug fix, <1 day). PEQUEÑO may keep the proposal light." @@ -44,7 +52,7 @@ rules: - "Honor the AOT constraint: no reflection, [JsonSerializable] source-gen for every DTO, NO Dapper — use Verbara.Sdk.Data.Npgsql." - "Record any durable architectural decision as an ADR in docs/decisions/, not only in this design." tasks: - - "When the change spans repos, spell out the cross-repo sequence: edit Sdk/Pro -> dotnet pack to local-nuget-feed -> clear NuGet cache -> dotnet restore the consumer." + - "When a change here must be verified against a locally built Sdk/Pro, spell out the local sequence: dotnet pack the producer to local-nuget-feed -> clear NuGet cache -> dotnet restore here. Verification only — a change that needs a commit in Sdk or Pro is hosted via `/xr:change` (verbara-meta/ADR-0006)." - "Verification tasks MUST include `dotnet test` green and CI green, with zero warnings (TreatWarningsAsErrors). EXCEPTION — frontend-only changes hosted here under the hub rule (verbara-meta/ADR-0005): verification is the Web gate set instead (`npm run build`, `npx vitest run`, `npx eslint .`, i18n parity green)." - "Order execution in three phases — A foundation (batched), B critical components (one focused subagent each), C integration (batched) — with a fresh subagent per task, never inline in the main session." - "For a bug fix, write the failing regression test first, against the unfixed code, and paste its failure verbatim into `tasks.md`. For new capability, tests may batch into Phase C."