Open to Backend, GenAI & Full-Stack roles · remote or Hyderabad

Projects

Tooling & Lab

Inkforge

Notes, topics, or code → published technical articles.

3 min read · 564 words

View repo 124 commits updated 2 weeks ago
TypeScript Node.js Next.js Turborepo Bedrock BM25 Commander Vitest

Inkforge is personal publishing infrastructure — a CLI + web UI that turns scattered notes, topics, or code directories into polished technical articles and publishes them to Dev.to through its API, with Medium and Hashnode publishers that drive your logged-in Chrome via browser-harness (not live-verified); Substack and LinkedIn stay manual.

The core is a STORM two-stage pipeline: first an explicit outline artifact is generated (section tree + word budgets per section), then each section is drafted independently with context chaining, then a single humanization pass adds voice and transitions. For notes-dump inputs, an in-process BM25 RAG layer (no external vector DB — k1=1.5, b=0.75, hierarchical Markdown chunker) surfaces the top-5 relevant chunks into the outline prompt.

  • STORM pipeline with explicit outlines — sections drafted independently, no context explosion; 4096-token budget with JSON truncation repair
  • BM25 in-memory RAG — no embedding service or vector database to run; BM25 over in-process chunks of your own notes
  • Dual output sinks — primary .md files for portability; optional Anvilry mirror, also .md since Velite's notes glob takes both
  • No asset rendering — nothing in the CLI touches pixels; cover, carousel and GIF specs are committed markdown under content/published/, rendered by a human or agent
  • Platform publishers — Dev.to REST API v1 (canonical_url); Medium and Hashnode via browser-harness in your logged-in Chrome, canonical URL checked by hand
  • Streaming web UI — SSE event stream from CLI pipeline into browser; section-by-section live preview at /generate
  • Content-as-committed-data — generated articles gitignored; published tracking committed as source of truth

44 tests in 9 files pass in CI on develop (a08e9e9, 2026-10-21). Built the Tombstone launch article (3,531 words) from incident notes in one command. @inkforge/cli is not on npm.

Architecture

Inkforge is a pnpm monorepo: packages/core holds the pipeline, RAG layer, LLM abstraction, and publishers; packages/cli is the Commander entry point. Both are versioned at 0.1.1; the root is 0.1.6 (v0.1.6, 2026-10-20), private, with no publishConfig — it runs from a git clone, not npm.

The LLM layer defaults to AWS Bedrock with a two-model fallback chain — Sonnet 4.6, then Haiku 4.5 — plus an LLM_PROVIDER=anthropic toggle. Opus 4.6 is deliberately excluded.

The publisher layer registers three publishers (publish --platform devto|hashnode|medium): a Dev.to REST client, and Medium and Hashnode publishers that script the browser through browser-harness, replacing the old Hashnode GraphQL client. Substack is a stub that only explains why it cannot publish (--platform substack is rejected) and LinkedIn has no publisher, so both ship by hand. All tests live in @inkforge/core and the publisher tests mock browser-harness; the Dev.to client, the LLM layer, the BM25 index and the outline, draft and polish stages have none.

How It Works

  1. Input — notes dump, topic, or code directory.
  2. RAG surfacing (notes-dump only) — BM25 surfaces the top-5 chunks into the outline prompt.
  3. Outline generation — one LLM call builds the section tree and word budgets via the Bedrock fallback chain.
  4. Section drafting — each section drafted independently with context chaining, streamed over SSE into /generate.
  5. Humanization pass — one pass adds voice and transitions.
  6. Assets, outside the pipeline — Inkforge renders nothing; cover, carousel and GIF specs are committed markdown, and a human or agent produces the images by hand.
  7. Publish — Dev.to pushes through its API; Medium and Hashnode are driven through browser-harness; Substack is pasted and LinkedIn's PDF uploaded by hand.
  8. Tracking — the generated article stays local and gitignored; the content/published/<platform>/<slug>.md record is committed. The same pipeline has since generated Trelix and Tombstone launches too.