Skip to main content

SC Execution History

Purpose​

What Symphony Core actually did, derived from git commits rather than from what plans said would happen. Written to be read as context by future agent sessions before proposing work: the record here is the base rate against which any new plan should be judged.

This document describes the past. It does not set direction — that is sc-goals.md — and it does not track the present — that is sc-current-status.md and sc-weekly-scorecard.md.

Scope and window​

Repository history begins 2025-10-23. The window is 9.8 months (297 days) to 2026-08-15, not twelve. Secondary figures are drawn from the personal coreOS repo where they change the reading. Regeneration commands are in Appendix A; unverifiable claims are in Appendix B.

Headline​

MetricValue
Total commits893 (844 non-merge, 49 merges)
Days with at least one commit214 of 297 (72.1%)
Longest silence7 days
Commits carrying Co-Authored-By: Claude800 (89.6%)
Distinct human contributors1

Presence is not the constraint. Something is committed on nearly three days in four, and the longest gap in the repository's life is a week.

Activity by month​

MonthCommitsNote
2025-1025Repo founded 10-23, 9 days
2025-1197Doc-framework build
2025-12102Folder reorganisation phases 1–3
2026-0136Lowest full month
2026-02112People-ops MVP, client document kit
2026-0351Cleanup and migration tail
2026-0457Global-pivot strategy drafted
2026-05122SOP suite, pivot cutover
2026-06138Peak — Meta ads, ClickUp canon, PR workflow
2026-0792Help-centre insourcing, Banyan Tree
2026-0861Partial, 15 of 31 days

Surge months (97–138) alternate with troughs (36–57) on a roughly three-month cycle.

The March–April 2026 trough is not a stall. coreOS took 54 and 83 commits in those months while this repo took 51 and 57. Combined output was flat to rising — attention relocated to the personal repo rather than stopping.

Where the work went​

Commits touching each top-level directory. Rows exceed 100% because a commit can touch several.

DirectoryCommits%
04-operations/27630.9%
08-reference/21724.3%
09-clients/18921.2%
docs/14916.7%
05-platform/11613.0%
03-sales/11112.4%
10-people-operations/839.3%
CLAUDE.md (single file)778.6%
02-marketing-brand/718.0%
06-team-training/667.4%
.claude/535.9%
01-strategy/394.4%
11-engineering/313.5%
07-customer-education/202.2%

The folder holding the company's goals, strategy, roadmap and status received less commit activity than CLAUDE.md alone.

Process versus delivery​

The central measurement. Each commit is assigned a dominant category by counting files touched per bucket; the method is in Appendix A so it can be re-run.

  • DELIVERY — 09-clients/, 03-sales/, 02-marketing-brand/, 01-strategy/products|financial/
  • PROCESS — 04-operations/, 08-reference/, 06-team-training/, docs/, CLAUDE.md, .claude/, scripts/
  • OTHER — everything else
MonthDELIVERYPROCESSDelivery %Process %
2025-102148.0%56.0%
2025-11253626.3%37.9%
2025-12206520.0%65.0%
2026-01141240.0%34.3%
2026-02405736.0%51.4%
2026-0383116.7%64.6%
2026-04231544.2%28.8%
2026-05337727.5%64.2%
2026-06238120.0%70.4%
2026-07383941.8%42.9%
2026-08172933.3%56.9%
Total24345628.8%54.1%

Confirmed independently two other ways: any-touch counting gives 350 vs 547; raw file-touches give 1,150 vs 2,136 (27.6% vs 51.2%).

Roughly 1.9 process commits for every delivery commit. Three findings follow:

  1. PROCESS exceeded DELIVERY in 9 of 11 months.
  2. The correlation is inverted. The two highest-output months in repo history were the two most process-heavy (2026-06 at 70.4%, 2026-05 at 64.2%). The only two months where delivery led were the two lowest-volume months. Additional energy has historically flowed into process, not delivery.
  3. The heaviest lifting has been self-maintenance. All fifteen of the largest commits by file count are reorganisations, renames, normalisations or migrations. Not one is content created for a client.

Client footprint​

Excluding six bulk cross-client commits that inflate last-activity dates (renames, Drive migration, ClickUp ID population, doc-kit enforcement — hashes in Appendix A).

ClientCommitsFirstTrue last client-specific commitQuiet
banyan-tree112026-07-292026-08-150d
iboost-online112026-05-142026-08-114d
rotary-sports (incl. rotary-ski)642025-11-192026-08-105d
moots-law (incl. mootslaw)262026-02-172026-08-105d
kraneworks272025-12-102026-07-1036d
upscale-legal232025-11-032026-07-1234d
ct-building-broker232025-11-072026-05-1097d
bn-package-store182026-02-102026-05-1196d
home-watch-203162026-02-152026-05-1196d
jp-floors92025-12-162026-04-20117d
southbury-plaza92025-11-222026-04-20117d
open-wize72026-02-172026-04-20117d
ijazi-masonry12026-07-162026-07-1630d

The delivery portfolio is effectively four accounts. Six client folders have had no client-specific commit in 96–117 days, and for four of them the most recent touch was a repo-wide field-population pass rather than work for the client. ijazi-masonry has one commit in its entire life — the day it was onboarded.

Note the overlap with revenue: four of the six quiet accounts (southbury-plaza, ct-building-broker, jp-floors, bn-package-store) carry the largest single lines in the G1 gap.

Outbound sales has no footprint​

03-sales/prospecting/ — 7 file-touches across 4 files, all templates or strategy, last touched 2026-03-02, silent 165 days. 03-sales/service-packages/ last touched 2026-02-12, silent 183 days.

Within 03-sales/lead-folders/, 74 of 93 file-touches (80%) are two names: lead-banyan-tree (47) and lead-iboost-online (27). All lead activity is inbound or referral. No outbound motion has ever run.

Strategy canon is resurrected, not maintained​

DocumentCommitsCreatedLast touchedDays since
sc-goals.md22026-08-142026-08-141
sc-current-status.md52026-05-012026-08-105
sc-execution-roadmap.md32026-05-012026-08-105
sc-strategy.md32026-05-012026-05-3176

Thirteen commits across four documents in 9.8 months, clustered into exactly three episodes: creation (2026-05-01), initiative-system import (2026-05-31), and consolidation (2026-07-16 → 2026-08-14). Between 31 May and 16 July — 46 days — no strategy document was edited at all, while the repo took 230 commits. The 2026-08-10 roadmap commit is titled "Q3 rollover"; its own changelog records the rollover as 41 days late.

Sprints and PRDs are write-once​

Sprint backlogs live 0–3 days. Ten exist, 31 commits between them. Four have exactly one commit — created, never reopened. 2026-05-client-analytics-foundation was written on 15 May and never touched again.

The exception proves the rule: 2026-07-help-center-insourcing has 11 commits over 3 days with real execution telemetry in the trail — "WS1 progress", "WS1-3 autonomous authoring complete (10 articles)", "WS2 complete - intake form live on intake.symphonycore.com". It shipped. It is one of ten.

PRDs: 8 of 20 (40%) have exactly one commit. Median touches per PRD is 2. Only two carry implementation-status updates.

Cadence​

There is none. Day-of-week distribution is flat Monday to Friday (135–162 commits, a 20% band), with 20% of commits on weekends. No Monday planning spike, no Friday review spike.

Every scheduled artifact has one or two commits total: operational-change-log.md (2 commits, both 2026-05-19, self-described as "append-only… to prevent silent drift"); session summaries (2, both 2025-12-21); the monthly KPI refresh (SOP written 2026-07-16, exactly one snapshot ever produced).

Only two rhythms have more than two observations, and both are under 30 days old: the rotary-sports client digest (v2.0 → v2.5 across 19 days, one client) and the ClickUp audit playbook (three runs, all on one client).

The rhythm that does exist is coarser: a repo-wide consolidation sprint roughly every three months — 2025-12, 2026-03, 2026-06-14, 2026-08-10. These are the four largest single-day file-churn events in the repo.

Abandonment signature​

Second-level paths with ≥4 commits and ≥60 days of silence. Genuine abandonments, excluding content relocated to other repos by design:

PathCommitsBurstSilent
03-sales/prospecting42025-10 → 2026-03165d
03-sales/service-packages52025-11 → 2026-02183d
01-strategy/Business-Plans72025-10 → 2025-12227d
06-team-training/knowledge-sharing52025-10-29 → 11-01286d
10-people-operations/onboarding322025-11 → 2026-0669d
02-marketing-brand/campaigns182025-12 → 2026-0671d
10-people-operations/contractor-registry.md152026-02 → 2026-0587d

Relocations are not abandonment. 08-reference/platforms, 08-reference/tech, 08-reference/glossary and parts of 11-engineering/ show 162–165 days silent because they were moved to the reference-docs and sc-documents-archive repos in March 2026. Nine further paths went dark on a single day, 2026-06-14, in a deliberate mass-retirement merge (#74).

Named initiative outcomes visible in the trail: web-agents (15 commits in 2 weeks, Nov 2025, retired 2026-06-14); Extendly (cancelled 2026-07-03, replaced by the in-house help centre); SearchAtlas (drawn down 2026-07-24, $138 refunded); _meta/ and START-HERE.md (both retired). Deprecation is handled well. What is missing is a comparable record of things launched.

What this record implies for planning​

  1. Effort is not the constraint. Direction is.
  2. Extra capacity has historically been absorbed by process work, not delivery. A plan that does not explicitly protect delivery time will lose it.
  3. Planning documents are written once and referenced, not maintained. A plan that requires periodic hand-updating will not get them.
  4. The four accounts with the largest revenue upside are among the six with no delivery activity in over three months.
  5. The only completion pattern with a good record is an external counterparty or a money date. Extendly's renewal, SearchAtlas's monthly bill, a GitHub issue, a coach waiting on pre-work — all completed. Internally-generated deadlines have a near-zero rate.

Appendix A — Regeneration​

All commands read-only. Run from the repository root.

# Headline
git rev-list --count HEAD
git log --format='%b' | grep -ci 'Co-Authored-By: Claude'
git log --format='%ad' --date=short | sort -u | wc -l

# Activity by month / by ISO week
git log --format='%ad' --date=format:'%Y-%m' | sort | uniq -c | sort -k2
git log --format='%ad' --date=format:'%G-W%V' | sort | uniq -c | sort -k2 | tail -25

# Commits per top-level directory (deduplicated per commit)
git log --name-only --format='COMMIT:%h' | awk '
/^COMMIT:/{h=$0; next}
NF{ split($0,a,"/"); key=h"\t"a[1];
if(!(key in seen)){seen[key]=1; cnt[a[1]]++} }
END{ for(k in cnt) printf "%6d %s\n", cnt[k], k }' | sort -rn

# Process vs delivery — dominant category per commit, per month
git log --name-only --format='COMMIT|%h|%ad' --date=short | awk -F'|' '
function cls(l){
if(l ~ /^09-clients\//) return "DELIVERY";
if(l ~ /^03-sales\//) return "DELIVERY";
if(l ~ /^02-marketing-brand\//) return "DELIVERY";
if(l ~ /^01-strategy\/(products|financial)\//) return "DELIVERY";
if(l ~ /^(04-operations|08-reference|06-team-training)\//) return "PROCESS";
if(l ~ /^docs\//) return "PROCESS";
if(l ~ /^(CLAUDE\.md|README\.md|START-HERE\.md|\.claude\/|_meta\/|\.gitignore|scripts\/)/) return "PROCESS";
return "OTHER";
}
/^COMMIT\|/{ if(h!="") flush(); h=$2; d=$3; delete n; next }
{ if($0=="") next; n[cls($0)]++ }
function flush(){ best="EMPTY"; bv=0;
for(c in n){ if(n[c]>bv){bv=n[c]; best=c} }
print substr(d,1,7)"\t"best }
END{ if(h!="") flush() }' | sort | uniq -c

# Client footprint, excluding bulk cross-client commits
BULK='f1b8da6|66d133d|8680e14|2e3a743|cb71b81|cb27b3c|86af59a|fdba331|feaaa2e'
for c in $(git log --name-only --format='' | grep '^09-clients/' | cut -d/ -f2 | sort -u); do
printf "%-22s " "$c"
git log --format='%ad|%h|%s' --date=short -- "09-clients/$c" \
| grep -vE "\|($BULK)\|" | head -1
done

# Strategy-doc churn
for f in 01-strategy/sc-goals.md 01-strategy/sc-current-status.md \
01-strategy/sc-execution-roadmap.md 01-strategy/sc-strategy.md; do
echo "### $f"; git log --follow --format='%ad %h %s' --date=short -- "$f"
done

# Cadence: day-of-week distribution
git log --format='%ad' --date=format:'%u %a' | sort | uniq -c | sort -k2

# Largest commits by file count
git log --format='%h|%ad|%s' --date=short --no-merges | while IFS='|' read h d s; do
echo "$(git show --name-only --format='' "$h" | grep -c .)|$d|$h|$s"
done | sort -rn | head -20

Appendix B — What could not be verified​

ItemIssue
A twelve-month windowHistory begins 2025-10-23. Everything here covers 9.8 months.
Conventional-commit scope counts334 of 893 commits (37.4%) are free-form and carry no scope; scope counts undercount pre-2026-02 work.
--follow across renamesThe 2026-03-06 kebab-case migration breaks rename tracking. Client totals are merged by hand; commits touching both old and new paths may be double-counted (rotary-ski/rotary-sports, May 2026).
49 merge commits--name-only emits no file list for merges, so they are unclassified. 2026-06 has 23 merges — its split is computed on 115 of 138 commits.
The DELIVERY/PROCESS boundaryA judgment call. Reclassifying 05-platform/ (116 commits) as delivery moves the split to roughly 42%/54%. The stated figure is the conservative delivery estimate; the direction of the finding survives either way.
Commits as a unit of workA one-line typo fix and a 77-file migration each count as one. Line-diff volume was not aggregated.
RevenueNo revenue data exists in git. "Touches delivery" is a path-proximity proxy, never a revenue measurement. Client activity here describes documentation, not billing.

Revision History​

DateVersionChange DescriptionAuthor
2026-08-151.0Initial record, mined from 893 commits across 9.8 months. Establishes the process-versus-delivery ratio (1.9:1), the effective four-account delivery portfolio, the absence of any weekly cadence, and the write-once pattern in sprints and PRDs. Regeneration commands and unverifiable-claim register included so the document can be rebuilt rather than hand-maintained.Symphony Core Systems Team