feat: scoping is the first Phase, completed in conversation (iteration 9 step 2)
Some checks failed
validation / verify (push) Failing after 10s
Some checks failed
validation / verify (push) Failing after 10s
Every Execution now begins by agreeing the scope, before requirements. - A new Phase and Deliverable, produced by a scope analyst with two tools: scope_read shows what is settled and what is not; scope_set records fields with where each value came from (the request, the customer's answer, or an assumption with its reason). Code checks each value against the catalogue. - With someone present the analyst asks for what is missing; with nobody present it assumes it, visibly. With no spec it drafts one from the request. A value the customer stated in the file is changed only by their own answer. - A submission cannot leave an essential field unknown. Code writes the completed spec, the data every later Specialist reads, and the information register, from what was recorded. - The spec's status follows the Execution: under review, approved, then locked as a Baseline. A Change request starts from the delivered scope. - The requirements analyst derives from the agreed scope and no longer asks for what it settles. About 80 tests assumed requirements came first; tests/scoped.py runs scoping ahead of a test's own script, and tests about order and counts are updated. Not run with real models. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -5,6 +5,7 @@ from app.adk.roles import PILLAR_ADVISOR
|
||||
from app.adk.runtime import RoleSpec, ToolResult, ToolSpec
|
||||
from app.tools.pillars import CONSULT_TOOL, pillar_consultation_tool
|
||||
from app.tools.toolkit import make_tool_factory
|
||||
from tests.scoped import ScopedRuntime as FakeAgentRuntime # noqa: F811
|
||||
|
||||
PILLARS = {
|
||||
"security": "waf-security",
|
||||
|
||||
Reference in New Issue
Block a user