name: the tree keel already derives for authority now names things too #109
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "name-law"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Four codehull units wear a hand-written path — OrgLabel, OrgRunner, OrgSecret, UserKey — because the unit namespace was recorded as FLAT by design. That record was a non-sequitur. `/org/label` is unavailable because the route grammar's second segment is an id, which rules out `/` as a separator; it does not rule out a hierarchical name. The flatness came from ddl::table() being one to_ascii_lowercase(), and the route law was read backwards as its justification. Meanwhile capability.md already says every unit derives its root chain, C-1 already walks it, and transfer already moves a subtree along it. The tree exists and is load-bearing. Identity was the only thing discarding it, so a flat namespace did what flat namespaces always do: the hierarchy got encoded into the leaf names, exactly as pthread_create and NSString encode theirs. This law separates the two spaces. Declaration stays flat — units never nest syntactically, so hierarchy stays data and transfer keeps working. Identity becomes `{root}:{name}`, derived from the root relation the author already wrote, so every declared name is one atom again. Scope is exactly one segment, and that bound is a detector rather than a ceiling: needing a third segment means two same-named units under two same-named units, which is a modeling error, and bind says so. `:` carries containment and `.` keeps possession — pack bag keys already spell student.courses, so one separator for both would recreate at a smaller scale the exact overload this law removes. The full key is the only identity: everything persisted or compiled holds it, and a short name is an explicit fallible resolution rather than an implicit widening. Nothing stored can turn ambiguous as the schema grows, because nothing stored was ever short. Law only. No engine change lands here. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>