Skip to content

docs: update GTM plan status, CHANGELOG, and launch content#175

Merged
ajianaz merged 1 commit into
developfrom
docs/update-gtm-plan-and-launch
Jun 4, 2026
Merged

docs: update GTM plan status, CHANGELOG, and launch content#175
ajianaz merged 1 commit into
developfrom
docs/update-gtm-plan-and-launch

Conversation

@ajianaz

@ajianaz ajianaz commented Jun 4, 2026

Copy link
Copy Markdown
Collaborator

Summary

Post PR #174 cleanup β€” bring docs up to date with actual state.

Changes

GTM Plan (docs/plans/2026-06-04-readme-landing-page-gtm.md)

CHANGELOG.md

  • Add missing [0.0.8] link (was absent from bottom links)
  • Add [Unreleased] entry for GTM Phase 1+2 work

Launch docs

  • docs/launch/hn-post.md: update install command to curl | sh, fix model size (188MB), update features list (namespaces, aging, consolidation, shell hooks, server mode)
  • docs/launch/twitter-thread.md: update competitors (Mem0/Letta/Zep instead of ChromaDB/MemGPT), add performance tweet, update install command

Summary by CodeRabbit

  • Documentation
    • Updated marketing and launch materials (Show HN and social media messaging) to reflect refreshed product positioning as "offline-first semantic memory engine."
    • Added new product highlights including simplified installation method, 30ms recall performance, and expanded feature list (shell hooks, HTTP server mode, memory aging, etc.).
    • Updated GTM plan documentation with completed phases and distribution strategy for Phase 3.

- GTM plan: mark Phase 1+2 as completed (PR #174 merged)
- CHANGELOG: add [0.0.8] link, add Unreleased entry for GTM work
- HN post: update install command, model size, features list
- Twitter thread: update competitors, add performance tweet
@coderabbitai

coderabbitai Bot commented Jun 4, 2026

Copy link
Copy Markdown

Review Change Stack

πŸ“ Walkthrough

Walkthrough

This pull request updates launch documentation and the GTM execution plan to reflect the completion of Phase 1–2 work from PR #174 (README and landing-page refresh) and aligns external messaging with new offline-first positioning, curl-based installation, 256-dimension embeddings, and Phase 3 distribution readiness.

Changes

Launch Documentation and GTM Messaging

Layer / File(s) Summary
Release metadata and GTM phase status
CHANGELOG.md, docs/plans/2026-06-04-readme-landing-page-gtm.md
CHANGELOG records GTM Phase 1+2 completion with README overhaul and website refresh references plus new [0.0.8] release link; GTM plan document opens with Phase status (1–2 completed, 3 ready) and merged PR #174 metadata.
Show HN and Twitter launch positioning
docs/launch/hn-post.md, docs/launch/twitter-thread.md
Show HN post and Twitter thread reposition Uteke as offline-first semantic memory engine with single-binary curl | sh install, 256d embeddings, ~30ms recall; expanded features (namespaces, memory aging, shell hooks, HTTP server); tweets compare against Mem0/Letta/Zep and emphasize zero API keys, Docker, or cloud.
GTM phase execution details and next steps
docs/plans/2026-06-04-readme-landing-page-gtm.md
Phase 1–2 task headers and descriptions updated to reflect completed work (README hero/tagline, quick-start installer, comparison table, performance refresh, landing page badge/social proof/OG tags); Phase 3 marked distribution-prep ready with Reddit post and terminal demo recording tasks; Summary section replaced with phase/task/status/results table and updated next steps for launching.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • ajianaz/uteke#174: Merged PR introducing the README and landing-page refresh that PR #175 documents as completed work in the changelog and GTM plan.
  • ajianaz/uteke#91: Related update to embedding dimensionality claims (768d β†’ 256d) and offline/semantic-memory positioning that align with the launch messaging in this PR.

Poem

🐰 The docs are dressed in new attire,
Offline-first and quick to fire,
256 dimensions deep and clean,
The launch copy now serene.
Phase three awaits with eager feetβ€”
Distribution's about to tweet! ✨

πŸš₯ Pre-merge checks | βœ… 5
βœ… Passed checks (5 passed)
Check name Status Explanation
Description Check βœ… Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check βœ… Passed The title accurately summarizes the main changes: documentation updates to GTM plan status, CHANGELOG, and launch content, which aligns with all four modified files.
Docstring Coverage βœ… Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check βœ… Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check βœ… Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
πŸ§ͺ Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/update-gtm-plan-and-launch

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❀️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

πŸ” Cora AI Code Review

βœ… No issues found. Code looks good!


Review powered by cora-cli Β· BYOK Β· MIT

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

πŸ€– Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/launch/hn-post.md`:
- Line 23: The docs claim EmbeddingGemma Q4 is 256d but the code uses 768
dimensions; update the docs text in hn-post.md to state 768d so it matches the
implementation (change the line mentioning "EmbeddingGemma Q4 (256d)" to
"EmbeddingGemma Q4 (768d)"). Verify this aligns with the constants and functions
in the codebase such as MODEL_DIMS (768) in
crates/uteke-core/src/embed/engine.rs, EmbeddingEngine::embed() which returns a
768-d vector, and DEFAULT_DIMS (768) in crates/uteke-core/src/memory/vector.rs.
πŸͺ„ Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
βš™οΈ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b40ebf42-0160-4cc4-886d-17f1366b0c78

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 37b8188 and 9b2b30f.

πŸ“’ Files selected for processing (4)
  • CHANGELOG.md
  • docs/launch/hn-post.md
  • docs/launch/twitter-thread.md
  • docs/plans/2026-06-04-readme-landing-page-gtm.md

Comment thread docs/launch/hn-post.md
- **Zero config** β€” First run downloads the embedding model (~188MB ONNX). That's it.
- **Fully offline** β€” No API keys. No cloud. Data lives in `~/.uteke/`. SQLite + HNSW.
- **Semantic search** β€” Uses EmbeddingGemma Q4 (768d) for vector similarity. ONNX runtime runs locally.
- **Semantic search** β€” Uses EmbeddingGemma Q4 (256d) for vector similarity. ONNX runtime runs locally.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Search for embedding dimension references in the code

# Search for dimension configurations
rg -nP '(dimension|dim|embedding.*(?:256|768)|(?:256|768).*embedding)' --type rust -C2

# Search for model dimension in config or constants
rg -nP 'const.*(?:DIM|DIMENSION|EMBED)' --type rust -C2

Repository: ajianaz/uteke

Length of output: 10475


Fix EmbeddingGemma embedding dimension claim in hn-post docs.

docs/launch/hn-post.md says EmbeddingGemma Q4 produces 256d embeddings, but the implementation hardcodes/uses 768 dimensions (e.g., crates/uteke-core/src/embed/engine.rs MODEL_DIMS: 768, EmbeddingEngine::embed() returning a 768-dimensional vector, and crates/uteke-core/src/memory/vector.rs DEFAULT_DIMS: 768). Update the doc to 768d.

πŸ€– Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/launch/hn-post.md` at line 23, The docs claim EmbeddingGemma Q4 is 256d
but the code uses 768 dimensions; update the docs text in hn-post.md to state
768d so it matches the implementation (change the line mentioning
"EmbeddingGemma Q4 (256d)" to "EmbeddingGemma Q4 (768d)"). Verify this aligns
with the constants and functions in the codebase such as MODEL_DIMS (768) in
crates/uteke-core/src/embed/engine.rs, EmbeddingEngine::embed() which returns a
768-d vector, and DEFAULT_DIMS (768) in crates/uteke-core/src/memory/vector.rs.

@ajianaz
ajianaz merged commit 7944f68 into develop Jun 4, 2026
8 checks passed
@ajianaz
ajianaz deleted the docs/update-gtm-plan-and-launch branch June 4, 2026 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant