Remember — Project Page
Vision
A private space for the thoughts I choose to always carry. The most personal diary of the mind I choose to be. Not documentation — remembrance. Things that matter enough to write down, organized enough to find again.
User Stories
| Role | Story | Success Metric |
|---|---|---|
| Lucas | Capture a thought I want to always remember, and find it again when I need it | Notes exist, are private, and are retrievable by topic |
Plan
No active plan. This project doesn't follow a development lifecycle. Notes arrive when they arrive.
Board
Board:
board-remember. Kanban for note maturity. Standard columns for now — see how the flow feels before customizing:Backlog (raw capture) → Todo (worth developing) → Next Up (actively thinking about) → In Progress (writing/expanding) → Done (finished piece)
Status
New project. First note: 2026-03-14. Auth enforcement pending —
is_public: false is a flag, not a lock. Tailscale network perimeter is the current access control.Milestones
None yet. Milestones may not apply to a personal journal — this section exists to satisfy the project template.
Architecture
No architecture diagrams. This is a personal project with no services, no data flow, no deployment. Notes live in pal-e-docs as
journal type, tagged private,remember, with is_public: false.Repos
| Repo | Platform | Role | Status |
|---|---|---|---|
| N/A | — | No code repository. Content lives in pal-e-docs. | — |
Open Questions
- Does the project template fit personal expression, or does a personal template need to emerge from use?
- Should the kanban columns be renamed for thought maturity (Raw → Reflecting → Developing → Polished → Published)?
- When pal-e-docs gets auth, how should per-user private notes work? Keycloak user ID on notes? Separate namespace?
- Should the template hook exempt personal projects from sections like Architecture and Repos?
Inbox
Query:
list_notes(project="remember", note_type="todo", status="open")