The ceremony is judged as the ceremony it is, and two internal maps now refuse borrowed truth

This release closes three places where a useful instrument was quietly asking the wrong question. The source map that follows work across files had one hundred and thirty-seven links it could not settle. They were not one mystery: ninety-nine called a small exported shorthand the map did not recognize, thirty-four deliberately leave the project for Node's cryptography library, one constructs an exported storage class, and three call same-named helpers that live in separate lexical blocks. Each class now has its own identity and adversarial test. The live map covers three hundred and nine modules, two thousand four hundred and thirty unique callable bodies, and six thousand seven hundred and ninety-three links with no unresolved or ambiguous row; the thirty-four external calls remain visible rather than being waved away. It is still a diagnostic, not a release gate, because zero open rows in one parser is not an independent proof of the whole tree. The second instrument judged every page as though it used the ordinary site shell. The crossing ceremony intentionally does not: it is a strict no-script ritual island with its own return and onward paths, and the old test expected a menu drawer plus a same-page health request its security policy correctly forbids. Visual evidence now names a shell or purpose-built contract, checks the ceremony's real navigation, and obtains release health without weakening the page's policy. Looking at the actual mobile and desktop pixels found the return pill was too small; it now has a forty-four-pixel minimum target with no overflow or contrast regression. The final repair is inward-facing but protects every future session: if the local recommendation generator times out, VEILOS will no longer display a cached task list from another project. Every output must prove both local scope and the VEILOS subject, while a failed or foreign fallback says it is unavailable instead of borrowing confidence. Obelisk remains the external identity and trust authority; no replacement authentication system, provider resource, migration, dependency, destructive operation, or cost increase was added.