u/Hungry-Treat8953

Guys I have my permanent DL test this Thursday for both car and bike, so I wanted to practice the figure "8" which is required for a bike test. So I wanted to know places where I can practice this 8 and it's a proper rto sized 8 with proper marking preferable location panvel but you can suggest any place within kharghar (can suggest others too). I went to the karnala side but couldn't find anything like that also it would be great if you could share the exact pinpoint location link. Also do the rto people check the details of the bike you bring there for the test?

I’ve been looking at OpenAI’s Auto-review, and I feel like it brings a problem: if an agent has to stop and wait for human approval every time it encounters a boundary action, the workflow becomes extremely fragmented; but if everything is automatically allowed through, it can easily drift toward the other extreme of full access.

So what I’m more concerned with now is no longer whether we need a reviewer, but rather: should the reviewer layer itself be stratified?

My intuition is that the first layer can actually be quite simple. Most escalation actions are rule-based by nature: whether they cross writable roots, whether they touch the network policy, whether they clearly have destructive side effects. This category may not need the heaviest model to review it at all.

What really makes me hesitate is the other layer: the harder review cases. These are cases where the action looks reasonable on the surface, but actually involves several candidate paths, different side effects, or a conflict between the user’s intent and system boundaries. At that point, the question is what kind of model is suitable for sitting in this hard-case reviewer slot?

This is where I start thinking about a thinking model like Ring 2.6 1T, with high / xhigh modes. If the reviewer layer really does need to be stratified, I’d be more inclined to put it in the role that requires complex logical analysis, path comparison, and final calls on hard cases, rather than having it review every single action by default.

I wouldn’t make it the always-on reviewer, but would instead reserve it specifically for cases where a lightweight reviewer should not be making the final call. If you were building your own auto-review / approval gate, would you stratify it this way? Or did you eventually find that, as long as the rules are clear, heavy reasoning is actually unnecessary for the reviewer layer?