Channel Map
Where to actually show up, and what each channel's job is — the point is picking a small set deliberately, not being everywhere. Per the Superpowers case study, the highest-leverage move is usually converting organic reach into one owned channel, not spreading thin across many rented ones.
| Channel | Job | Status |
|---|---|---|
| fullstackfusions.com | Owned portfolio site — the anchor destination everything else points back to | Already live. |
| fullstackfusions.com/blogs | Long-form technical writing — exactly the "publish the reasoning" channel the Superpowers case study pointed at, already operational, not a gap | Already live and active — 30 posts as of 2026-08-24, spanning RAG architecture (per-industry: travel, hospital, wealth management, banking), LLM observability, harness engineering, agent memory, voice cloning, AWS agent-native infra, MCP. Published to github.com/fullstackfusions/fullstackfusions (_posts/), mirrored read-only into this vault's BlogPosts/ nightly via Hermes. This is the single biggest already-existing proof artifact for proof_artifacts — 30 real, dated, substantial technical posts is most people's multi-year blogging output. |
| fullstackfusions.com/projects | Curated, public-facing project showcase — the polished cross-source view a recruiter/interviewer would actually browse | Already live — but NOT simply a filtered view of one repo. Aggregates from at least three sources: the public_projects repo, past job-role work (different employers, not personal experiments), and other standalone personal GitHub repos. See proof_artifacts for the full breakdown — none of the three source→site mappings are tracked anywhere yet. |
github.com/fullstackfusions/public_projects |
One specific source among several feeding the site above — personal hands-on experiments/prototypes, not job/client work | Already live — 51 projects, spanning fintech, healthcare IT, AI/LLM, DevOps/Kubernetes, databases, networking, observability. See Projects/public-projects for the full table. |
| Other standalone personal repos | Additional source feeding the portfolio site, separate from public_projects |
Exists per Mihir, not yet inventoried anywhere in this vault — see proof_artifacts's todo |
| Primary interview/recruiter-facing surface — positioning statement, proof artifacts, job-search visibility | Active per Works/NextPlan/2026-08-contract-job-search; > [!todo] confirm current posting cadence/handle here — natural next move is cross-posting/linking the existing blog posts here, not writing new content twice | |
| GitHub (profile-level) | Proof-of-work surface, umbrella above the specific repos already listed | fullstackfusions org per this vault's remote; > [!todo] confirm which repos beyond public_projects and the blog repo are meant to be public-facing |
| Owned channel (newsletter/community) | Only worth building once there's an audience to convert | Not started — with a live blog already generating content, this is the more natural next channel to consider than starting a new writing surface would have been |
[!todo] Confirm LinkedIn handle/cadence, the actual list of standalone personal repos, and what else lives under the
fullstackfusionsGitHub org beyondpublic_projectsand the blog repo. Everything else in this table is already accurate as of 2026-08-25.