Agentic SDLC via MCP
How to use the SbD-ToE MCP server to support the end-to-end agentic development process — the agent consults the manual via MCP at each stop of the flow, from mandate to kill-switch.
How to use the SbD-ToE MCP server to support the end-to-end agentic development process — the agent consults the manual via MCP at each stop of the flow, from mandate to kill-switch.
Organisational policy that defines the lifecycle of the mandate of each AI agent in operational use — registration, ownership, autonomy levels A0-A4, tool scope, periodic review and revocation, in alignment with REQ-AGN-001..004 of Ch. 02 and ARC-015 of Ch. 04, proportionate to the criticality level (L1, L2, L3).
Organisational policy that defines the requirements for the controlled use of development support tools, including generative AI assistants (GenAI/Copilot) and autonomous agents with tool-use (A0–A4), with a focus on mandatory review of output, traceability, licence validation, autonomy mandates and the maintenance of human responsibility, proportional to the criticality level (L1, L2, L3).
Cross-cutting map of the secure development process for systems with AI agents — from mandate to kill-switch, with stops in each SbD-ToE chapter and a cross-reference to the AI Act, NIS2, DORA and the CRA
Prescription for the controlled use of automated generation tools (including AI) in development, without changing the application requirements