Orpheus Systems Architecture

7. Fresh orphan branch for the public repository

7. Fresh orphan branch for the public repository

Date: 2026-10-22

Status

Accepted

Problem

The repository carries naming from a previous employer (a utilities package, a path alias and a URL, listed in design §8) in its working tree and in its three existing commits. The anti-goal is that nothing in the public repository identifies a previous employer or a real client; the acceptance criterion is that the case-insensitive hygiene grep defined in design §8 returns nothing. The terms themselves are deliberately not repeated here.

Decision

The public repository orpheussystems/sharepoint will start from a fresh orphan branch. The three existing commits are not carried over, so the grep criterion applies to history as well as to the working tree. New commits use the repo-local author Kiril Iliev <kiril.iliev@orpheussystems.com>. The clean-room pass removes every prior-employer fingerprint before the first public commit; LICENSE was initially MIT © 2026 Orpheus Systems (superseded by ADR-009: Apache-2.0 with NOTICE) and package.json author, repository, homepage are set accordingly.

From the private history to the public repository

flowchart TB
  subgraph PRIV["Private repository"]
    H["Three existing commits<br/>with prior-employer naming"]
    WT["Working tree"]
  end
  WT --> CR["Clean-room pass<br/>removes every<br/>fingerprint"]
  CR --> G{"Hygiene grep<br/>design §8, gate G-2<br/>any hits?"}
  G -->|"yes"| CR
  G -->|"no"| O["Fresh orphan branch<br/>no parent commit<br/>repo-local author"]
  O --> PUB["Public repository<br/>orpheussystems/sharepoint<br/>private until published"]
  H -.-x|"not carried over,<br/>stays private"| PUB
  PUB --> GATE["Hygiene grep also<br/>passes on git log -p<br/>and runs in CI"]

Considered Options

Option Summary Pros Cons
✅ Orphan branch New history from a clean tree History provably clean; simple Loses the (small) existing history
History rewrite (git filter-repo) Scrub identifiers from existing commits Keeps history Error-prone; residual risk in commit messages and blobs; three commits are not worth it
Publish as is No change None Violates the anti-goal

Consequences

Positive:

Negative / Trade-offs:

Risks: | Risk ID | Description | Impact (E/H/M/L) | Mitigation | |---------|-------------|------------------|------------| | R-HYG-1 | A fingerprint survives in the working tree at the time of the orphan commit | H | Gate G-2 grep before the first public commit |

Amendments

2026-10-23 — The decision is unchanged.