Skip to content

docs: add procedural-memory investor FAQ#277

Open
Gradata wants to merge 2 commits into
mainfrom
gra-2535-investor-faq
Open

docs: add procedural-memory investor FAQ#277
Gradata wants to merge 2 commits into
mainfrom
gra-2535-investor-faq

Conversation

@Gradata

@Gradata Gradata commented Jun 9, 2026

Copy link
Copy Markdown
Owner

Summary

Adds a diligence-safe investor FAQ artifact for GRA-2535 covering procedural-memory objections:

  • why now
  • context windows
  • MCP
  • Mem0/Letta/incumbents
  • data moat
  • retention
  • wedge
  • distribution
  • security
  • pricing
  • proof quality
  • company-vs-feature risk

Issue UUID: 4e1a1fb6-8099-4b75-9004-609cc45aa69b

Verification

  • python3 artifact check: 12 objection pairs, 12 proof-needed-next lines, explicit verified/hypothesis separation
  • git diff --cached --check

Artifact

docs/investor-faq/GRA-2535-procedural-memory-diligence.md

@greptile-apps greptile-apps 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.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: a60772f7-d22b-476f-8a40-87b68b829e13

📥 Commits

Reviewing files that changed from the base of the PR and between c596f05 and da6b736.

📒 Files selected for processing (1)
  • docs/investor-faq/GRA-2535-procedural-memory-diligence.md
📜 Recent review details
🔇 Additional comments (2)
docs/investor-faq/GRA-2535-procedural-memory-diligence.md (2)

17-17: LGTM!


111-111: LGTM!


📝 Walkthrough
  • Adds investor FAQ: docs/investor-faq/GRA-2535-procedural-memory-diligence.md (188-line doc) addressing procedural-memory diligence objections
  • Explicitly separates verified facts from assumptions/hypotheses and reiterates no claims of external customers, revenue, or paid pilots
  • Contains 12 objection/answer pairs covering timing, context windows, MCP, incumbents (Mem0/Letta), data moat, retention, wedge, distribution, security, pricing, proof quality, and company-vs-feature risk
  • Each objection includes a "Proof needed next" item (12 proof-needed lines) specifying concrete validation steps (before/after datasets, eval comparisons, retention metrics, security model publication, pricing validation, external alpha case studies)
  • Verified artifact checks recorded: Python artifact check confirming 12 objection pairs, 12 proof-needed-next lines, and explicit verified/hypothesis separation; and git diff --cached --check performed
  • Documentation-only change; no exported/public API changes, no breaking changes, and no security fixes

Walkthrough

This PR adds a new investor FAQ document addressing diligence objections to Gradata's procedural-memory category framing, structuring verified facts vs assumptions, 12 objection/answer sections with explicit "Proof needed next" items, and scope constraints on claims.

Changes

Procedural-Memory Investor Diligence FAQ

Layer / File(s) Summary
Investor FAQ document with verified facts, diligence objections, and proof requirements
docs/investor-faq/GRA-2535-procedural-memory-diligence.md
New FAQ document separating verified facts from assumptions, addressing 12 investor diligence objections with answers and explicit proof requirements including before/after datasets, baseline comparisons, retention tracking, security model publication, pricing validation, and external case studies. Establishes scope limits (no claims of external customers, revenue, or paid pilots).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

docs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'docs: add procedural-memory investor FAQ' directly and clearly describes the main change: adding a new investor FAQ document for procedural-memory diligence.
Description check ✅ Passed The description is directly related to the changeset, listing specific topics covered in the FAQ, verification steps, and the artifact file path.
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 gra-2535-investor-faq

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

@coderabbitai coderabbitai Bot added the docs label Jun 9, 2026

@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: 2

🤖 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/investor-faq/GRA-2535-procedural-memory-diligence.md`:
- Line 111: Replace the sentence "Verified: The founder's own environment
heavily dogfoods agentic coding and operations workflows." with a more polished
phrasing; for example, change "heavily dogfoods" to "extensively uses" or
"practices extensive internal use" so the line reads along the lines of
"Verified: The founder's own environment extensively uses agentic coding and
operations workflows." This keeps the meaning but removes informal jargon for
investor-facing material.
- Line 17: Update the founder background sentence ("The founder is Oliver, solo,
with AE experience at Sprites AI and previously PayPal.") to spell out the
abbreviation "AE" (e.g., "Account Executive" or "Application Engineer") —
confirm which meaning is correct, replace "AE" with the full title, and
optionally include the abbreviation in parentheses (e.g., "Account Executive
(AE)") for clarity in investor-facing materials.
🪄 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 3015f583-180e-41e9-b28f-1f553f5e2924

📥 Commits

Reviewing files that changed from the base of the PR and between 8bf23a5 and c596f05.

📒 Files selected for processing (1)
  • docs/investor-faq/GRA-2535-procedural-memory-diligence.md
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: pytest macos-latest / py3.11
  • GitHub Check: pytest ubuntu-latest / py3.12
  • GitHub Check: pytest macos-latest / py3.12
  • GitHub Check: pytest ubuntu-latest / py3.11
  • GitHub Check: pytest windows-latest / py3.12
  • GitHub Check: pytest windows-latest / py3.11
🧰 Additional context used
🪛 LanguageTool
docs/investor-faq/GRA-2535-procedural-memory-diligence.md

[style] ~119-~119: To elevate your writing, try using a synonym here.
Context: ...or objection: "Memory infrastructure is hard to distribute. What's the go-to-market ...

(HARD_TO)


[grammar] ~128-~128: Ensure spelling is correct
Context: ...horts; publish a simple case study from dogfood or external alpha users. ## 9. Is this...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~158-~158: Ensure spelling is correct
Context: ...tion: "Is this real evidence or founder dogfood theater?" Answer: - Verified: Current...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (1)
docs/investor-faq/GRA-2535-procedural-memory-diligence.md (1)

1-189: Fix potential leakage: ensure docs/investor-faq/ isn’t published publicly

Current file is under docs/investor-faq/, but the prior check couldn’t verify anything because mkdocs.yml is not present in the repo root (so we don’t know whether MkDocs publishes it). Run/confirm the docs build configuration: locate the actual MkDocs config file(s), then ensure docs/investor-faq/ is either excluded from the public build or only included in a private/internal artifact path; otherwise this “diligence-safe” investor material (proof gaps/hypotheses + founder background + lack of customers) may leak to gradata.ai/docs.

Comment thread docs/investor-faq/GRA-2535-procedural-memory-diligence.md Outdated
Comment thread docs/investor-faq/GRA-2535-procedural-memory-diligence.md Outdated

@greptile-apps greptile-apps 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.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant