Skip to content

memory(detect-changes pattern): sibling-repo parallel-optimized external anchor (Aaron 2026-05-01)#1130

Merged
AceHack merged 7 commits intomainfrom
backlog/b0157-detect-changes-pattern-stcrm-parallel-optimization-aaron-2026-05-01
May 1, 2026
Merged

memory(detect-changes pattern): sibling-repo parallel-optimized external anchor (Aaron 2026-05-01)#1130
AceHack merged 7 commits intomainfrom
backlog/b0157-detect-changes-pattern-stcrm-parallel-optimization-aaron-2026-05-01

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented May 1, 2026

Summary

Aaron 2026-05-01: "../no-copy-only-learning-agents-insight is the best repo in github i've seen setup to be parallel."

Direct inspection (DST grade-A pull-to-sibling-repo + gh-api-on-host disciplines) revealed seven load-bearing parallel-optimization patterns. Memory file captures them as substrate; company name redacted per the no-copy-only-learning principle.

Patterns captured

  1. detect-changes.yaml workflow emitting per-change-class outputs — PRs only run relevant workflows
  2. 42 fine-grained workflows (vs our ~15 monolithic)
  3. Test parallelism at script level (bash + PS1 pair)
  4. 5 concern-aligned rulesets — empirically validates B-0155 architecture
  5. Branch protection effectively empty (zero contexts, all migrated to rulesets) — empirical proof B-0155 Phase 3 cleanup endpoint works at production scale
  6. Sibling repo uses Wiki not Pages — Aaron's prior Jekyll-on-Pages was workaround, not preference ("bun is probably enough")
  7. AGENTS.md learning-discipline — convergence with our existing patterns (lessons-in-PR / joint-learning / source-investigation / search-first authority)

Attribution

The sibling repo's host config is deliberate-by-others (multi-engineer org-scale design); Zeta is Aaron-clicked-alone. High-credibility external anchor for design patterns we extract. Sharpens the click-vs-decision distinction across actors.

Carved candidate

"The detect-changes pattern is the parallel-PR primitive. Without it, every PR contests for every check. With it, PRs that touch different concerns don't see each other."

composes_with

B-0153 (lint suite) + B-0154 (Pages + Wiki) + B-0155 (ruleset-split) + B-0156 (TS port) + Otto-235 (4-bash + PS) + task #305 (install.ps1) + task #341 (TS migration) + Otto-352 (external-anchor-lineage)

Test plan

  • markdownlint clean
  • MEMORY.md paired-edit included in same PR
  • Company-internal names redacted to placeholders (`/`)
  • memory-edge schema used (composes_with + caused_by)

🤖 Generated with Claude Code

Copilot AI review requested due to automatic review settings May 1, 2026 17:51
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9fa46b923c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new memory entry capturing a “detect-changes workflow + fine-grained workflow split” CI parallelization pattern observed in a sibling repository, and updates the memory index to reference it (plus related redaction updates).

Changes:

  • Added a new memory file documenting the external “detect-changes” CI pattern and how it composes with existing Zeta backlog/ruleset work.
  • Updated memory/MEMORY.md to include the new entry and to replace several existing index entries with redacted “sibling org” placeholders.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 10 comments.

File Description
memory/feedback_detect_changes_pattern_sibling_repo_parallel_optimized_external_anchor_aaron_2026_05_01.md New memory entry documenting CI parallelization patterns and rollout guidance.
memory/MEMORY.md Adds an index entry for the new memory and updates multiple existing index links/labels.

Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
AceHack added a commit that referenced this pull request May 1, 2026
… new content only (Aaron 2026-05-01)

Aaron 2026-05-01 calibration: *"../it's folder name was fine"* +
*"that's why i named it that."*

The `../no-copy-only-learning-agents-insight` directory name IS
the abstraction discipline Aaron designed. New substrate uses
generic placeholders (`<sibling-org>/<sibling-repo>`); existing
filenames with company names are GRANDFATHERED per the
established naming + scope-of-org-access rule (2026-04-28).

My prior commit's `<sibling-org>` substitution was over-
aggressive — it broke valid existing MEMORY.md link targets to
real files (feedback_servicetitan_naming_*,
project_account_setup_snapshot_codex_servicetitan_*,
project_frontier_burn_rate_ui_*_servicetitan_*,
feedback_servicetitan_demo_*, etc.). The link TEXT was
already redacted to "the sibling-repo external anchor" /
generic phrasing; the link TARGETS need to point at real files.

Restored link targets to the real filenames. New content (memory
body + MEMORY.md link text) keeps the redacted phrasing per the
no-copy-only-learning principle for new substrate.

Resolves PR #1130 review threads
PRRT_kwDOSF9kNM5_BSNv + PRRT_kwDOSF9kNM5_BSNx.
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6ab8ff9776

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

AceHack added a commit that referenced this pull request May 1, 2026
…e the" duplicate

Two threads from PR #1130 review:

1. Copilot + chatgpt-codex-connector (line 11): composes_with
   referenced `feedback_otto_352_external_anchor_lineage_for_substrate_credibility_2026_04_26.md`
   which doesn't exist on disk. The "external-anchor-lineage"
   concept is captured in the Beacon promotion memo
   (`feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md`)
   which IS shipped. Repointed.

2. Copilot (line 281): "the the sibling repo team" — duplicate
   "the". Removed.

Note: the 8 stale `<sibling-org>` placeholder threads on
MEMORY.md are outdated post-restoration commit 6ab8ff9 and
will resolve as outdated.
Copilot AI review requested due to automatic review settings May 1, 2026 18:24
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

AceHack added a commit that referenced this pull request May 1, 2026
… new content only (Aaron 2026-05-01)

Aaron 2026-05-01 calibration: *"../it's folder name was fine"* +
*"that's why i named it that."*

The `../no-copy-only-learning-agents-insight` directory name IS
the abstraction discipline Aaron designed. New substrate uses
generic placeholders (`<sibling-org>/<sibling-repo>`); existing
filenames with company names are GRANDFATHERED per the
established naming + scope-of-org-access rule (2026-04-28).

My prior commit's `<sibling-org>` substitution was over-
aggressive — it broke valid existing MEMORY.md link targets to
real files (feedback_servicetitan_naming_*,
project_account_setup_snapshot_codex_servicetitan_*,
project_frontier_burn_rate_ui_*_servicetitan_*,
feedback_servicetitan_demo_*, etc.). The link TEXT was
already redacted to "the sibling-repo external anchor" /
generic phrasing; the link TARGETS need to point at real files.

Restored link targets to the real filenames. New content (memory
body + MEMORY.md link text) keeps the redacted phrasing per the
no-copy-only-learning principle for new substrate.

Resolves PR #1130 review threads
PRRT_kwDOSF9kNM5_BSNv + PRRT_kwDOSF9kNM5_BSNx.
AceHack added a commit that referenced this pull request May 1, 2026
…e the" duplicate

Two threads from PR #1130 review:

1. Copilot + chatgpt-codex-connector (line 11): composes_with
   referenced `feedback_otto_352_external_anchor_lineage_for_substrate_credibility_2026_04_26.md`
   which doesn't exist on disk. The "external-anchor-lineage"
   concept is captured in the Beacon promotion memo
   (`feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md`)
   which IS shipped. Repointed.

2. Copilot (line 281): "the the sibling repo team" — duplicate
   "the". Removed.

Note: the 8 stale `<sibling-org>` placeholder threads on
MEMORY.md are outdated post-restoration commit 6ab8ff9 and
will resolve as outdated.
@AceHack AceHack force-pushed the backlog/b0157-detect-changes-pattern-stcrm-parallel-optimization-aaron-2026-05-01 branch from 5c81e99 to fddbc76 Compare May 1, 2026 18:47
Copilot AI review requested due to automatic review settings May 1, 2026 18:48
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 905119204b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread memory/MEMORY.md Outdated
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 7 comments.

Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
Comment thread memory/MEMORY.md Outdated
AceHack added 6 commits May 1, 2026 14:59
…chor (Aaron 2026-05-01)

Aaron 2026-05-01: *"../no-copy-only-learning-agents-insight is
the best repo in github i've seen setup to be parallel"* +
*"you should be able to use the gh cli i think to see it's
setting in read only mode too"* + *"this has had a lot of
intention put into by others not so much by me the gh config
for that project"* + *"opposite of your Pages-with-Jekyll
preference; not my preference, i've just used it before cause
i didn't want to write ts at the time, bun is probably enough"*.

Direct inspection of `../no-copy-only-learning-agents-insight`
+ `gh api repos/servicetitan/stcrm` (per the DST grade-A
pull-to-sibling-repo + gh-api-on-host discipline) revealed
seven load-bearing patterns:

1. detect-changes.yaml workflow emitting per-change-class
   outputs — PRs only run relevant workflows
2. 42 fine-grained workflows (vs our ~15 monolithic)
3. Test parallelism at script level (bash+PS1 pair)
4. **5 concern-aligned rulesets** — empirically validates
   B-0155 architecture (Copilot review / Flux config /
   Release Pending / Status Checks + Merge Queue /
   deployment-branch protection)
5. **Branch protection effectively empty** (zero contexts,
   strict:null) — empirical proof B-0155 Phase 3 cleanup
   endpoint works at production scale
6. STCRM uses Wiki not Pages — Aaron's prior Jekyll-on-Pages
   was a workaround, not preference; bun makes TS-native
   static gen viable (Astro / Vitepress as B-0154 candidates)
7. AGENTS.md learning-discipline patterns we already have
   analogues for (lessons-in-PR, joint-learning, source-
   investigation, search-first authority)

Attribution: STCRM is deliberate-by-others (multi-engineer
org-scale design); Zeta is Aaron-clicked-alone. High-
credibility external anchor for design patterns we extract.

Carved candidate: "The detect-changes pattern is the
parallel-PR primitive. Without it, every PR contests for
every check. With it, PRs that touch different concerns
don't see each other."
…ect-changes memory

Per the no-copy-only-learning principle (the directory is named
`../no-copy-only-learning-agents-insight` for exactly this reason):
extract patterns/insights, not company-internal names.

Renamed file: feedback_detect_changes_pattern_stcrm_*
            → feedback_detect_changes_pattern_sibling_repo_*

Replaced all in-body references to STCRM / servicetitan / stcrm
with "the sibling repo" / "<sibling-org>/<sibling-repo>" placeholders.
Cleaned up double-mentions from automated sed pass.

The patterns + architectural insights are preserved. The company
name is gone.

Note: prior commit message + PR title still leak the name (history
already on origin); fixing forward only.
… new content only (Aaron 2026-05-01)

Aaron 2026-05-01 calibration: *"../it's folder name was fine"* +
*"that's why i named it that."*

The `../no-copy-only-learning-agents-insight` directory name IS
the abstraction discipline Aaron designed. New substrate uses
generic placeholders (`<sibling-org>/<sibling-repo>`); existing
filenames with company names are GRANDFATHERED per the
established naming + scope-of-org-access rule (2026-04-28).

My prior commit's `<sibling-org>` substitution was over-
aggressive — it broke valid existing MEMORY.md link targets to
real files (feedback_servicetitan_naming_*,
project_account_setup_snapshot_codex_servicetitan_*,
project_frontier_burn_rate_ui_*_servicetitan_*,
feedback_servicetitan_demo_*, etc.). The link TEXT was
already redacted to "the sibling-repo external anchor" /
generic phrasing; the link TARGETS need to point at real files.

Restored link targets to the real filenames. New content (memory
body + MEMORY.md link text) keeps the redacted phrasing per the
no-copy-only-learning principle for new substrate.

Resolves PR #1130 review threads
PRRT_kwDOSF9kNM5_BSNv + PRRT_kwDOSF9kNM5_BSNx.
…e the" duplicate

Two threads from PR #1130 review:

1. Copilot + chatgpt-codex-connector (line 11): composes_with
   referenced `feedback_otto_352_external_anchor_lineage_for_substrate_credibility_2026_04_26.md`
   which doesn't exist on disk. The "external-anchor-lineage"
   concept is captured in the Beacon promotion memo
   (`feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md`)
   which IS shipped. Repointed.

2. Copilot (line 281): "the the sibling repo team" — duplicate
   "the". Removed.

Note: the 8 stale `<sibling-org>` placeholder threads on
MEMORY.md are outdated post-restoration commit 6ab8ff9 and
will resolve as outdated.
…capitalization in non-verbatim text (Copilot 2 threads)
…place; preserve only the new detect-changes index entry (Copilot 7 threads)
@AceHack AceHack force-pushed the backlog/b0157-detect-changes-pattern-stcrm-parallel-optimization-aaron-2026-05-01 branch from 5347ca9 to 2aa55d6 Compare May 1, 2026 19:03
AceHack added a commit that referenced this pull request May 1, 2026
@AceHack AceHack merged commit 949c5b0 into main May 1, 2026
23 checks passed
@AceHack AceHack deleted the backlog/b0157-detect-changes-pattern-stcrm-parallel-optimization-aaron-2026-05-01 branch May 1, 2026 19:13
AceHack added a commit that referenced this pull request May 1, 2026
…ules + carved-sentences-only canonical) + #1130 final 2 threads drained (#1138)
AceHack added a commit that referenced this pull request May 1, 2026
…+ 7 threads drained (#1140)

* hygiene(tick-history): 2026-05-01T19:03Z — #1130 bulk-replace overcorrection revert (7 threads drained)

* fix(tick-history 1903Z): escape pipe in xargs example (Copilot)
AceHack added a commit that referenced this pull request May 1, 2026
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.

2 participants