[STRANGER-TEST] Session 1: Junior Developer

[4444J99]

Session Metadata

• Date: 2026-03-15
• Session type: live
• Participant profile: Junior Frontend Developer

Tasks Attempted

1. Task: Find out what ORGAN-V does.
   Result: ❌
2. Task: Find a way to contribute.
   Result: ✅

Friction Points

• The profile README is heavily philosophical. Participant couldn't understand what concrete software the org builds.
• Greek naming convention (theoria, poiesis) was extremely confusing.

Trust Signals

• High quality formatting and consistent branding increased trust.

Recommended Changes

• Add a TL;DR "What we do in plain English" at the top of the README.

Evidence

None.

[4444J99]

Engagement disposition: distilled: README.md. Current main now opens with a concrete explanation that Public Process is a Jekyll blog/publication site, includes a What ORGAN-V Does section, and has a Greek Names in Plain English table mapping each organ name to its role. That directly addresses the junior-developer confusion about what ORGAN-V does and what the Greek names mean.