gate: a resolve-only public surface (screen) beside wall #73

Open
opened 2026-07-17 03:57:00 +00:00 by PerishFire · 0 comments
Owner

ensign brings its own ceremonies (invitation-only join, password login per the escape-ladder law) and needs gate's resolution middleware WITHOUT the stock doors — today wall() welds /register /login /logout (token-flow) onto the pass layer.

Proposal: pub fn screen(self, router: Router) -> Router — the pass layer alone (bearer Token + Session cookie resolution, bar hook honored, operator injection). wall() keeps its meaning (doors + screen).

Found by ensign dream-code (ensign docs/model.md, gaps section). Ship as keel-gate in the next train.

ensign brings its own ceremonies (invitation-only join, password login per the escape-ladder law) and needs gate's resolution middleware WITHOUT the stock doors — today `wall()` welds `/register` `/login` `/logout` (token-flow) onto the pass layer. Proposal: `pub fn screen(self, router: Router) -> Router` — the pass layer alone (bearer Token + Session cookie resolution, bar hook honored, operator injection). `wall()` keeps its meaning (doors + screen). Found by ensign dream-code (ensign docs/model.md, gaps section). Ship as keel-gate in the next train.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PerishLab/keel#73
No description provided.