Each policy is a plain promise you can inspect — what’s allowed, what isn’t, and who decides.
KNOWN BOUNDARIES · 4 IN FORCE
Only the boundaries actually established right now. Anything not stated reads not recorded — never legalistic wallpaper.
{{ p.name }}
{{ p.summary }}
{{ p.tag }}
CAN
{{ p.can }}
CANNOT
{{ p.cannot }}
WHO DECIDES{{ p.who }}
IF REVISED{{ p.ifRevised }}
source · {{ p.source }}applies · {{ p.applies }}enforced · {{ p.enforcedBy }}exceptions · none recordedchange receipt · not recorded
ALTERNATE — NOT CURRENT · A REQUESTED ACTION HITS A POLICY. THE SOURCE / WHY, THE CONSEQUENCE, A SAFE ALTERNATIVE, AND THE EXACT DECISION ROUTE — NO INVENTED LEDGER OR EXCEPTION HISTORY.
REQUESTED ACTION
“Publish the Otaru day to my public site.”
HITS A HARD BOUNDARY
PolicyNo outward authorization
Source / whyyour default — the day is private, on device
Consequenceit would send data outward — Veda will not
SAFE ALTERNATIVE
Keep the day private and prepare a reversible draft. Correct the low-confidence place first, then decide — nothing leaves until you authorize the exact artifact.
This conflict is reversible — the request simply waits at the boundary for your call. Nothing is denied forever; nothing crosses on its own.
VEDA HEARD
“can the Otaru day go public?”
confirm first
Trust — policies
Only boundaries actually in force are shown. Everything else reads “not recorded” — no legalistic wallpaper.
A hard boundary (magenta) can’t be crossed. A reversible conflict (amber) waits at the decision.
Every policy names who decides and what would change if it were revised — you, always.