# Episode - Profile.md and Aura.md: What belongs in public and what stays private?

Status: seed
Generated: 2026-05-17
Generated by Two Dogs interactive feedback form.

## Core Boundaries

- Luke is Red Dog / Red Heeler.
- Angel is Blue Dog / Blue Heeler.
- Blue Dog material is Angel-directed only.
- Guests choose their own spirit animal character and nickname.

## Hook

Red Dog uses the idea of public profile files and deeper private AI context files to ask a bigger question: what should the world know, and what should only the trusted system know?

## Why This Episode

The Community Ledger page separates a plain public profile from deeper private context for useful AI help. That is a clean way to discuss public/private boundaries in a podcast without getting abstract too quickly.

## Red Dog Angle

Red Dog can talk about why AI systems work better with context, but why not all context belongs in public, on-chain, on a website or in a casual prompt.

## Blue Dog Boundary

[Blue Dog space - Angel to direct]

## Main Beats

- What a public profile should be able to say plainly.
- Why deeper context can help agents without becoming public theatre.
- The risk of over-sharing because a system feels friendly.
- How consent, usefulness and audience decide where information belongs.

## Scene Seeds

- Red Dog sorts cards into public beach noticeboard, private notebook and "do not feed this to anything".
- A guest chooses a spirit animal nickname but keeps their private life private.
- A friendly AI asks for too much and gets gently redirected.

## Segment Seeds

- Public, private or nope
- Context helps, oversharing hurts
- The useful boundary

## Source References

- Strange But True: Community Ledger public profile and deeper private file sections
- Public page: https://auraofintelligence.github.io/strange-but-true/community-ledger.html

## Next Useful Action

Make a reusable privacy prompt for future guest notes: "What is public, what is private, and what is not for the repo?"