Cross-repo review + consolidation pass (2026-07-24) on the CAD/brain-adjacent repo set. ingestion-svc already did exactly this move once — archived 2026-05-14, its README states "All ingestion functionality has been consolidated into hyperguild/ingestion." Two more single-purpose ingestion-trigger repos exist today with no equivalent consolidation.
Candidates
mathias/brain-ingest-ntfy — real, built (ntfy URL-push → brain ingest, issue #1 closed as shipped). Currently CI-red since 2026-05-22 (Build & Import failing, issue #3, unresolved 2 months) — brain-ingest-ntfy#3 itself notes the same failure shape recurs on brain-ui, suggesting a shared scaffold bug rather than something specific to this repo's own logic worth preserving in a standalone pipeline.
mathias/brain-weekly-ingest — appears never actually built. homelab#4 says outright: "brain-weekly-ingest repo is empty, not a dependency." Its own issue #1 (the experiment brief, DIKW Phase 1) carries a falsifiable hypothesis with a 2026-07-01 deadline that has now passed with no resolution recorded anywhere found. Issue #3 in that repo is explicitly self-flagged as filed in the wrong place ("This issue currently lives on brain-weekly-ingest, which is the wrong home now that scope is a personal one-off... may not warrant a repo at all").
Proposal
Confirm whether brain-weekly-ingest's experiment (weekly Claude.ai conversation ingest) is still wanted at all, given the hypothesis deadline lapsed unresolved — if yes, build it as a source adapter inside hyperguild/ingestion (the README already lists "GitHub source adapters (in progress)" as the pattern to follow) rather than a fourth standalone repo.
Port brain-ingest-ntfy's ntfy-URL-push trigger into hyperguild/ingestion as another source adapter, fixing the CI issue as part of the move rather than in the old repo.
Once both are absorbed, mark both origin repos archived with a README pointer, mirroring ingestion-svc's own (README.md: "⚠️ ARCHIVED... superseded and pending deletion... All ingestion functionality has been consolidated into hyperguild/ingestion").
ingestion-svc's README.md — the precedent this mirrors exactly
Risk: LOW — consolidation/planning issue, no code yet.
## Context
Cross-repo review + consolidation pass (2026-07-24) on the CAD/brain-adjacent repo set. `ingestion-svc` already did exactly this move once — archived 2026-05-14, its README states "All ingestion functionality has been consolidated into `hyperguild/ingestion`." Two more single-purpose ingestion-trigger repos exist today with no equivalent consolidation.
## Candidates
- **`mathias/brain-ingest-ntfy`** — real, built (ntfy URL-push → brain ingest, issue #1 closed as shipped). Currently **CI-red since 2026-05-22** (`Build & Import` failing, issue #3, unresolved 2 months) — brain-ingest-ntfy#3 itself notes the same failure shape recurs on `brain-ui`, suggesting a shared scaffold bug rather than something specific to this repo's own logic worth preserving in a standalone pipeline.
- **`mathias/brain-weekly-ingest`** — appears **never actually built**. `homelab#4` says outright: "brain-weekly-ingest repo is empty, not a dependency." Its own issue #1 (the experiment brief, DIKW Phase 1) carries a falsifiable hypothesis with a **2026-07-01 deadline that has now passed** with no resolution recorded anywhere found. Issue #3 in that repo is explicitly self-flagged as filed in the wrong place ("This issue currently lives on brain-weekly-ingest, which is the wrong home now that scope is a personal one-off... may not warrant a repo at all").
## Proposal
- [ ] Confirm whether `brain-weekly-ingest`'s experiment (weekly Claude.ai conversation ingest) is still wanted at all, given the hypothesis deadline lapsed unresolved — if yes, build it as a source adapter inside `hyperguild/ingestion` (the README already lists "GitHub source adapters (in progress)" as the pattern to follow) rather than a fourth standalone repo.
- [ ] Port `brain-ingest-ntfy`'s ntfy-URL-push trigger into `hyperguild/ingestion` as another source adapter, fixing the CI issue as part of the move rather than in the old repo.
- [ ] Once both are absorbed, mark both origin repos archived with a README pointer, mirroring `ingestion-svc`'s own (`README.md`: "⚠️ ARCHIVED... superseded and pending deletion... All ingestion functionality has been consolidated into hyperguild/ingestion").
## Related
- `mathias/brain-ingest-ntfy#3` (CI red, unresolved)
- `mathias/brain-weekly-ingest#1` (stale hypothesis, deadline lapsed), `#3` (self-flagged wrong repo)
- `ingestion-svc`'s `README.md` — the precedent this mirrors exactly
Risk: LOW — consolidation/planning issue, no code yet.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Context
Cross-repo review + consolidation pass (2026-07-24) on the CAD/brain-adjacent repo set.
ingestion-svcalready did exactly this move once — archived 2026-05-14, its README states "All ingestion functionality has been consolidated intohyperguild/ingestion." Two more single-purpose ingestion-trigger repos exist today with no equivalent consolidation.Candidates
mathias/brain-ingest-ntfy— real, built (ntfy URL-push → brain ingest, issue #1 closed as shipped). Currently CI-red since 2026-05-22 (Build & Importfailing, issue #3, unresolved 2 months) — brain-ingest-ntfy#3 itself notes the same failure shape recurs onbrain-ui, suggesting a shared scaffold bug rather than something specific to this repo's own logic worth preserving in a standalone pipeline.mathias/brain-weekly-ingest— appears never actually built.homelab#4says outright: "brain-weekly-ingest repo is empty, not a dependency." Its own issue #1 (the experiment brief, DIKW Phase 1) carries a falsifiable hypothesis with a 2026-07-01 deadline that has now passed with no resolution recorded anywhere found. Issue #3 in that repo is explicitly self-flagged as filed in the wrong place ("This issue currently lives on brain-weekly-ingest, which is the wrong home now that scope is a personal one-off... may not warrant a repo at all").Proposal
brain-weekly-ingest's experiment (weekly Claude.ai conversation ingest) is still wanted at all, given the hypothesis deadline lapsed unresolved — if yes, build it as a source adapter insidehyperguild/ingestion(the README already lists "GitHub source adapters (in progress)" as the pattern to follow) rather than a fourth standalone repo.brain-ingest-ntfy's ntfy-URL-push trigger intohyperguild/ingestionas another source adapter, fixing the CI issue as part of the move rather than in the old repo.ingestion-svc's own (README.md: "⚠️ ARCHIVED... superseded and pending deletion... All ingestion functionality has been consolidated into hyperguild/ingestion").Related
mathias/brain-ingest-ntfy#3(CI red, unresolved)mathias/brain-weekly-ingest#1(stale hypothesis, deadline lapsed),#3(self-flagged wrong repo)ingestion-svc'sREADME.md— the precedent this mirrors exactlyRisk: LOW — consolidation/planning issue, no code yet.