← Case Studies/Case #011/C11-015
C11-015DecidedPrivacyFoundational2026-06-06

Child Journey as Private Key, YY Method as Public Key

The child's actual AI learning journey is the private key: journals, prompts, attempts, artifacts, corrections, AI guardrail reviews, and parent decisions. YY Method is the public key: it may derive safe-distance projections, quests, badges, lessons, and proof metadata. The public key may change surface by audience and intent, but it may not mutate, overwrite, disclose, or define the private key.

Freshness
Permanent

Permanent for minor-child source material. Revisit only when the child is legally able to control disclosure, or if the private repository/access model changes materially.

#private-key#public-key#child-owned-repo#private-git#public-projection#source-truth#portfolio-proof#disclosure-consent#one-way-flow

Capture

The child's journey is the private key. YY Method is the public key.

The private key is the child's actual AI learning record:

The public key is the rederived surface:

The public key can change surface depending on audience and intent. It may produce a family-facing note, an adult-learning lesson, a school-compatible pattern, a trusted-family template, or a founder reflection. But it cannot mutate the private key.

The private key is never committed publicly. It rests in a private Git repository in the child's own account, controlled for the child while they are a minor and eventually by the child. The private key can only be shared by the child under their own conditions, and it cannot be safely shared until they are legally able to make that decision.


Why

This architecture gives both sides what they need.

The child gets:

YY Method gets:

The one-way rule is the core:

private key -> public projection: allowed through parent gate
public projection -> private key: forbidden
AI output -> private key mutation: forbidden
parent ambition -> child disclosure: forbidden
child adult consent -> selective disclosure: allowed

The public surface must be easy to rederive from the private source, but it must never require publishing the private source.


Private Repository Shape

The private repository should be organized for future readability:

/journal/YYYY-MM-DD.md
/artifacts/
/prompts/
/ai-reviews/
/parent-decisions/
/portfolio-candidates/
/projection-links/

The public repository may contain only derived records:

/content/case-011/public-learning-notes/
/method/projections/
/badges/
/quests/
/patterns/

Each public projection should carry enough metadata to locate its private source internally without exposing that source publicly.


Why-Not

Why not publish the child's raw journal with identifying details removed? Because raw material can still reveal identity, family context, emotional state, dates, school details, or private thinking patterns. The raw layer exists for the child, not the product.

Why not keep the private source in the parent's account only? The parent may administer access while the child is a minor, but the architecture should point toward the child's own ownership. The long-term archive belongs to the child.

Why not let public feedback improve the private archive? Public feedback may inform future teaching surfaces, but it must not mutate the child's source record. The private key records what happened, not what the public later wanted it to mean.

Why not treat the private archive as a family asset? Because the journey belongs to the child. The family may steward it. The child owns the eventual disclosure decision.


Commit

Decision: A child's AI learning journey is the private key of the system. It lives in a private repository in the child's own account and is never committed publicly. YY Method is the public key: it may derive safe-distance projections, quests, badges, adult-facing lessons, and generalized proof from parent-gated private records. The public key may change surface by audience and intent, but it may not mutate, overwrite, disclose, or define the private key.

Confidence: High.


Timestamp

2026-06-06

C11-014Case #011 RegistryC11-016