Operator-oriented, architecture-aware documentation connected directly to the working routes technical teams use during evaluation, review, and rollout.
These routes are the shortest path from product understanding to technical review, rollout planning, and browser-surface orientation.
The documentation surface should feel like a review workspace: what to read first, what route to open next, and how the technical narrative connects back to enterprise evaluation.
Start here when platform and security stakeholders need to define deployment boundary, control surfaces, and rollout fit.
Use the Web UI and route-level docs to connect product surfaces to actual operator workflows and runtime behavior.
Move into enterprise intake once the conversation shifts from understanding the system to scoping a real evaluation.
The documentation view keeps the emphasis on what matters to platform teams: memory, orchestration, security, and the control plane around them.
JEBAT uses a five-layer memory stack with heat-based promotion, retention, and retrieval rules that keep long-lived operator context useful instead of noisy.
Specialist skills and role-driven agents turn the platform into a governed execution system rather than a plain prompt interface.
Security is treated as audit, hardening, and execution-boundary control across both browser and backend surfaces.