portfolio: consolidate overlapping repos into canonical recruiter-facing surfaces

[rmems]

Goal

Reduce recruiter-facing repository noise without flattening real architectural boundaries. The active GitHub surface should expose one canonical repository per meaningful accomplishment, while reusable libraries keep independent repositories when they own a genuinely distinct abstraction.

Planning attribution

This portfolio-consolidation plan was drafted with GPT-5.6 Sol (ChatGPT/OpenAI) in collaboration with @rmems on 2026-08-22. Recommendations are revised when direct repository inspection shows a stronger boundary than the initial portfolio-level heuristic.

Portfolio rule

A public repository should earn its own recruiter-facing surface by having at least one of:

• an independently useful reusable library/API;
• a distinct application or experiment with measurable evidence;
• a separate runtime/deployment boundary;
• a separate release lifecycle or consumer base.

Internal abstractions that only exist to support one larger accomplishment should normally become crates/modules/packages inside the canonical repository.

Consolidation wave

Workstream	Canonical issue	Intended result
Issue/Linear migration	#4	Re-home open GitHub work and reconcile auto-created Linear twins before archiving source repos
Temporal Julia stack	rmems/TemporalFocus.jl#53	NeuroPulse.jl + SpikeStream.jl → TemporalFocus.jl
Tensor/fusion architecture	rmems/hybrid-fusion#20	Keep hybrid-fusion separate; finish Corinth/Grok contract extraction. cortex-tensor#35 is closed not-planned.
Reward/plasticity stack	Limen-Neural/plasticity-lab#54	rmems/limbic-critic → plasticity-lab workspace
Runtime/IPC/hardware stack	Limen-Neural/brainstem-daemon#35	thalamic-relay + corpus-ipc → brainstem-daemon workspace; preserve separate core/app crates/binaries
Trading application	rmems/Limen-Capital#9	DendriteTrader.jl → Limen-Capital strategy layer
Spikenaut case study	rmems/Spikenaut-SNN#19	spike-viz + Spikenaut-specific training glue → Spikenaut-SNN
Grok compression reporting	rmems/grok-ozempic#88	combine-for-AI → grok-ozempic evaluation/reporting layer
Corinth thinning	rmems/corinth-canal#161	upstream proven code, then make Corinth consume promoted sibling libraries where parity/performance justify it

hybrid-fusion rule

Do not merge hybrid-fusion into cortex-tensor merely to reduce repo count. Current ownership is defensible:

• hybrid-fusion → backend-agnostic Transformer↔SNN orchestration contracts, pure projection/routing interfaces, architecture composition;
• cortex-tensor → concrete tensor/transformer/MoE numerical implementation;
• engram-parser → checkpoint parsing/layout;
• neuromod → neuron/network dynamics;
• myelin-accelerator → CUDA/GPU kernels.

Continue the Corinth→hybrid-fusion extraction program through rmems/hybrid-fusion#20 instead of collapsing the two repos.

Corinth rule

Do not turn corinth-canal into a consolidation sink. It should become thinner over time: prove behavior in Corinth, upstream reusable surfaces, validate parity/portability/performance, release or pin the sibling library, adopt it as a dependency when justified, then remove the local duplicate.

magere-brug remains external rather than being merged into Corinth.

Migration policy

1. Preserve useful git history where practical.
2. Keep internal package/crate boundaries when they have architectural value.
3. Establish one canonical repository/package identity for each consolidated surface.
4. Move tests, examples, docs, benchmarks, and CI with the implementation.
5. Migrate/triage open GitHub issues using portfolio: migrate open issues and reconcile Linear twins during repository consolidation #4 before archiving a source repo; verify destination GitHub→Linear twins and reconcile old twins instead of manually duplicating them.
6. Update repository URLs, package metadata, badges, docs, GitHub Pages links, and downstream dependency references.
7. Add redirect READMEs to superseded repositories.
8. Archive superseded repositories only after downstream consumers, active issues, and links are migrated.
9. Do not delete source repositories merely for visual cleanup; archive them as provenance.

Recruiter-facing definition of done

• No active repository presents a duplicate or conflicting project identity.
• Pinned repositories each communicate a distinct accomplishment.
• Active READMEs lead with outcome/evidence/reproduction rather than ecosystem archaeology.
• Superseded repositories are archived and clearly redirect to their canonical successor.
• Every open source-repo issue has a documented disposition and active work has a canonical destination issue.
• Destination Linear twins are verified before old twins/source issues are retired.
• Stale former-repository URLs are removed after transfers/consolidations.
• The profile system map reflects canonical repositories only.
• corinth-canal becomes smaller through validated dependency adoption rather than absorbing sibling implementations.

Tracking / Linear sync

This GitHub issue is the canonical umbrella. Let the existing GitHub→Linear integration create its twin automatically; do not manually create a duplicate.

[rmems]

Planning attribution

This consolidation plan and the initial issue drafting were produced with GPT-5.6 Sol (ChatGPT/OpenAI) in collaboration with @rmems on 2026-08-22. Final architectural decisions and implementation remain subject to repository-level validation and maintainer review.