# PROFILES — user, coach, markdown projection

The living record should *read* as markdown. The database (when it exists) is sized for long comments, not VARCHAR(255).

v1 is a prototype: a directory of markdown files is an acceptable stand-in for Postgres. Do not over-build.

## Hybrid (later)

- Postgres (or files, in the mockup) is source of truth
- Long fields: coach observations, letters, recipe method, “what was missing”
- Project to markdown:

```text
users/<id>/profile.md
users/<id>/coach.md
users/<id>/meals/2026-08-19.md
users/<id>/letters/2026-W33.md
users/<id>/inventory.md
recipes/<recipe-id>.md
stances/*.md
constitution.md          # hidden — not served as part of the user profile
```

## User profile (visible)

A nicer page (and a `.md`) the user can visit:

- Who they are in Iðunn terms (goals, trusted farm, dislikes)
- Recent plate in plain language
- Body metrics they chose to track
- Behaviour analysis: repeats, gaps, inventory habits
- Links to letters and favourite recipes

This is **their** story, not a verdict.

## Coach profile (visible)

How *this* user’s coach is behaving — not the secret constitution:

- What it has noticed (“workday seed-oil lunches,” “loves the stew”)
- What it stopped nagging, what it started offering
- Tone they asked for (blunt / softer)
- A reminder on the page: **the coach advises; you decide**

The user can correct it: “stop talking about liver every day.”

## Prototype honesty

Do not encrypt these files in v1. LAN HTTP is enough to show the idea. Isolation is “separate folders / a user_id column,” not a threat model.