Capture
A meeting, note, or status update becomes sourced project memory.
Leku accepts rough context first. The source stays attached before anything becomes a brief, decision, answer, or follow-up.
Living project memory
Leku
Project memory that stays current.
A meeting, note, or status update becomes sourced project memory. Leku keeps the current state, decisions, open questions, and answers tied to the source so teams can see what changed before they act.
Captured from planning notes
Launch readiness changed after the design review.
The current plan depends on owner review, source inspection, and one unresolved launch question before the team acts.
- Source
- Planning notes
- Freshness
- Context may be stale
Source-backed answer
What changed?
This answer is based on 4 sources. Two prior decisions are related, and one source should be reviewed before treating the plan as final.
Related to two prior decisions
Decision record
Review source before acting
Source library
Context may be stale
Freshness signal
Current state, not another folder.
Organize
Current state becomes visible without filing work.
The product names what changed, what was decided, what is unresolved, and which source supports the memory.
Verify
Answers keep their evidence in view.
Ask from the project memory, then inspect source, freshness, confidence, and related decisions before acting.
This answer is based on 4 sources
Context may be stale
Related to two prior decisions
Review source
Before the workspace
Understand the product before signing in.
The prototype shows the working surface. The public pages explain signup, privacy, AI processing, and how project memory stays tied to evidence.