editor
Promise
Use reflection, entertainment, symbolism, self-observation, next safe step.
Do not promise exact future, legal outcome, health, money, or another person's love.
editorial lock
Content change rules
How to change public and internal content without breaking tone, trust, SEO, legal boundaries, and user safety.
OmenHall content should be warm, clear, and careful. It invites reflection, but does not sell fate in a bottle.
editor
SEO
Write useful title/description that matches page content.
Do not stuff repeated keywords for search engines.
owner
Internal notes
Keep internal operational content noindexed and practical.
Do not turn internal instructions into public trust copy.
Before change
A change begins not with code, but with reason and limits.
- Name the owner and impacted routes.
- Understand whether this is a public page or internal noindex section.
- Define rollback path before merge.
During change
Make changes in small batches so errors do not spread through the house like quiet smoke.
- Do not mix payment, content, UX, and security in one shapeless commit.
- Check routes, internal links, SEO, and noindex near the change.
- Do not add tracking without a privacy-safe note.
After change
A change ends not when code is saved, but when it can be verified and rolled back.
- Run typecheck, lint, tests, route audit, links, structure, and security checks.
- Record result in the relevant pass report or decision log.
- Name what remains unchecked and where to verify it in Vercel.
checklist
- There is a next step, but no pressure.
- There is a safety boundary for high-stakes topics.
- No conflict with refund policy, disclaimer, trust, or AI transparency.
handoff
- Editor hands off summary: what changed, why, routes, SEO notes, risk notes.
red flags
- Page promises an 'exact answer'.
- Copy scares the user into buying a reading.
- Internal operator text leaked into a public page.
related doors