owner
Record the reason
Every change connects to a problem, metric, complaint, task, or roadmap note.
Do not change copy, pricing, routes, or email only because it sounds prettier today.
day one
Day-one handbook
What a new helper should read, check, and not touch on the first day working with OmenHall.
A new person enters the house not with a hammer, but with a map, a lamp, and respect for locked rooms.
owner
Keep receipts
After important changes leave a short changelog: what changed, where, how to verify, how to rollback.
Do not leave the future team facing a riddle without a map and lamp.
everyone
Protect the user
If the user is vulnerable, anxious, or asks for risky advice, move the response back into safe boundaries.
Do not promise healing, guaranteed futures, legal wins, money, or influence over another person.
Read first
Before work, a new helper reads internal sections to avoid mixing public promises and operator notes.
- /trust, /how, /ai-transparency, /refund-policy
- /content-governance, /support-ops, /launch, /ops-calendar
- Current pass reports in project root.
Touch only safe areas
Day one is for reading, QA, and small copy fixes, not blindfolded surgery.
- Allowed: typo, broken internal link, documentation note.
- Not allowed: prices, Stripe, auth, privacy copy, legal disclaimers.
- All changes go through owner review.
checklist
- I understand which sections are public and which are internal/noindex.
- I understand forbidden claims and support boundaries.
- I know where route registry, Next redirects, and reports live.
handoff
- At end of day the helper writes what they understood, what they did not, and what risks they noticed.
- Owner assigns first safe task after reading.
red flags
- New helper asks for production keys.
- New helper proposes immediate pricing or payment changes.
- New helper cannot distinguish advice boundary from oracle reflection.
related doors