Agent-native software should not create a separate shadow system for AI. Agents and applications need to operate over the same workspace records, permissions, validation rules, and audit trail.
That is why Slab5 treats REST, MCP access, and AgentGrid as product surfaces over the same backend contract. REST is for applications and integrations. MCP is for agents where enabled. AgentGrid is for repeatable workflows that need runs, approvals, retries, schedules, and inspection.
Each surface should resolve workspace context, check scopes, respect module boundaries, and write request-correlated activity or run history that humans can inspect.
The design constraint is simple: if an app, agent, or workflow changes business state, the change should be visible, attributable, and reversible through normal operational processes.