Attach Intent to Every Pull Request.

Memorum records the Why behind every Pull Request, so future engineers never have to guess.

PRs ship. Context evaporates. Memorum keeps the Why attached to the code.

Built for CTOs, Engineering Managers, and architects who value clarity over chaos.

  • Runs directly inside your PRs
  • Adds structured architectural context
  • Search decisions years later
Install GitHub AppView Demo PR

Works with GitHub. No CI config required.

Minimal permissions:Read PRs + diffs路Comment on PRs路Read repo metadata
馃
Memorum Analysis路 just now
Why This Change

Rotate refresh tokens on session bind to prevent token replay attacks. This strengthens OAuth security by ensuring tokens are bound to validated session nonces.

Testing: Unit tests for token rotation + integration test for session binding
Why Source: AI Generated
Consider: What happens to existing sessions after deploy?
鈿狅笍Auth layer change detected. Verify session rollback behavior and token expiry handling.
Architectural Questions
What happens to in-flight requests during token rotation?
Answer: ________________
How are existing sessions migrated?
Answer: ________________
鉁忥笍 Edits are preserved
Change Size:4/10
Files:5
Delta:+127-34
Layers:auth 路 api
Category:AUTH_FLOW_CHANGE
Risk:Elevated
Review Focus
backwards compatpermissionstoken handlingsession state

Code changes. Context disappears.

After 6 months

"Why was this file changed?"

After 2 years

"Who approved this architectural shift?"

During onboarding

"Why does auth work like this?"

Memorum answers these questions automatically, inside your Pull Requests.

How it works

1

Install GitHub App

One-click install. No config required.

2

Memorum analyzes every PR

AI extracts intent, layers, risk, and review focus.

3

Intent is preserved

Searchable by file, commit, author, time.

For Teams That Take Architecture Seriously

  • Stop re-explaining decisions in Slack
  • Know who approved risky changes
  • Review faster with risk + focus hints
  • Search decisions by file or commit
  • Onboard new devs using real PR history
  • No dashboards or behavior changes

No-friction PR Why capture

Memorum inserts a structured Why block into every PR. Developers can edit it. Edits are preserved.

馃
Memorum Analysis
Why This Change

Migrate session storage from cookies to Redis to enable horizontal scaling. Previous cookie-based approach limited us to sticky sessions.

鉁忥笍 Edits to "Why This Change" are preserved
Architectural Questions
What happens to existing sessions during migration?
Answer:
________________
How is session data invalidated on logout?
Answer:
________________
鉁忥笍 Your answers are saved
Without Memorum
路 Slack thread archaeology
路 git blame guessing
路 "Ask the author" (who left)
With Memorum
路 Why captured at PR time
路 Approved by reviewers
路 Searchable forever

Edits persist. No extra process.

Retrieval intelligence

Find the 'Why' in 2 seconds. Search architectural decisions across time.

src/auth/session.ts
repo: myorg/apiauthor: anycategory: AUTH_*2023-2024
AUTH_FLOW_CHANGEPR #142路 Mar 2024

Bind refresh tokens to validated session nonces to prevent replay attacks.

auth/session.ts@aliceabc123f
AUTH_FLOW_CHANGEPR #98路 Jan 2024

Migrate session storage from cookies to Redis for horizontal scaling.

auth/session.ts@chendef456a
DATA_MODEL_CHANGEPR #67路 Nov 2023

Add session metadata table for audit logging requirements.

auth/session.ts@kumar789abc0
3 decisions found 路 0.8s 路 Indexed by file, commit, author, time

Search by file, commit, author, time.

Architectural risk detection

Memorum highlights risky layers and tells reviewers what to check.

Risk Analysis
PR #203
Category:DATA_MODEL_CHANGE
Risk:High
Affected Layers
dbpaymentsapi
鈿狅笍Database schema change detected. Verify migration rollback and data integrity before merge.
Review Focus
migrationsdata integritybackwards compaterror handling
Blast Radius:Medium路 touches db + payments + api

Catch risky architectural changes before merge.

Small Tool. Real Problem.

Memorum attaches intent to your codebase.

No dashboards.

No new process.

No behavior change.

Just structured engineering memory.

Get Started