Remember

Remember

2026-03-14 — Stream of consciousness while building the Posts project

The CTA link in my posts needs to go somewhere real. Not just a LinkedIn profile — a landing page. A SvelteKit frontend on Tailscale that captures leads. Minimal friction: get an email address, maybe a name, nothing more at first. Keep it professional.

But that means I need:

• A landing page repo (SvelteKit)
• A way to receive and store contact info (backend? form service?)
• A URL on the cluster
• A design — found "impeccable" (open source frontend design tool). Want to fork/mirror to Forgejo and use it as a design agent.

Where does this live? pal-e-agency project? But that project is already about process/agency operating model. Adding a frontend repo bloats it. Maybe there's a separate project for frontend work? Or maybe this is just SOP — "how does an enterprise handle frontends?" — and each frontend lives with its parent project.

The real question: am I even making a post right now, or am I building infrastructure to make posts? Both. The landing page IS the CTA. Can't publish posts without it. But the landing page is also its own project with its own plan.

Frontend SOP for an enterprise — what does that look like? Fork impeccable to Forgejo, use it for design, deploy SvelteKit apps to cluster. This is repeatable. Every project that needs a frontend follows the same pattern. Maybe that's a convention, not a project.

I'm journaling, not posting. And that's fine. Organize thoughts first, build second.

Key threads to resolve:

• Landing page repo: where does it live (project-wise)?
• impeccable: fork to Forgejo, evaluate as design tooling
• Lead capture: minimal funnel (email only), where to store contacts
• Frontend SOP: convention for how frontends are built across projects
• pal-e-agency bloat risk: is pal-e-agency the right home for this?

What most inspires me about my brother Marcus — what I am most proud of — is his unwavering belief in himself.

Confidence.

It's a matter of focusing on the right thing, and doing what must be done, sure. But it's also just getting what you want.

— 2026-03-14

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

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

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")