Semantic Config Define logic breakpoints like "Region Entry", not file paths.
Native Debugging GlobQL pauses the actual process (Node/JVM), allowing full variable inspection.
Run and Debug
VARIABLES
this: PaymentService
req: Object
amount: 100
currency: "USD"
GLOBQL BREAKPOINTS
Entry: :payments
Exit: :web
Data: PII Leak
CALL STACK
14
15
16
17
18
19
20
// PaymentService.ts
class PaymentService {
async process(req) {
Paused on Region Entry
Context switched from :web to :payments.
Matched rule: Entry: :payments
    const valid = await this.validate(req);
if (!valid) throw "Invalid";
return stripe.charge(req);
}
}
CALL STACK (Thread 1) Running: node --inspect
Payments process PaymentService.ts:17
Web checkoutHandler CheckoutController.ts:42
Web handleRequest Server.ts:105
main Auto Save: On
Spaces: 2 UTF-8 TypeScript

Platform-Native Semantic Debugging

Don't just instrument; intervene. GlobQL hooks directly into your platform's debugger (Node.js Inspector, JVM JDWP, etc.). This lets you pause execution when high-level conditions are met—like crossing a Region boundary—giving you full access to inspect variables and memory in real-time.