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:
@@ -14,6 +14,7 @@ tools, so the Ledger refuses anything that is not allowed, whatever was decided.
|
||||
|
||||
from __future__ import annotations
|
||||
|
||||
import json
|
||||
import logging
|
||||
import re
|
||||
from collections.abc import Awaitable, Callable, Mapping, Sequence
|
||||
@@ -37,6 +38,7 @@ from app.workflows.chain import (
|
||||
IMPLEMENTATION_FILE,
|
||||
RECOMMENDATIONS_FILE,
|
||||
REQUIREMENTS_FILE,
|
||||
SCOPE_DATA_FILE,
|
||||
VERDICTS_FILE,
|
||||
read_graph,
|
||||
read_list,
|
||||
@@ -741,6 +743,24 @@ def approval_facts(phase: PhaseId, view: TurnView, r: Readings) -> dict[str, Any
|
||||
),
|
||||
}
|
||||
facts["counts"] = {name: count for name, count in counts.items() if count}
|
||||
scope = (view.deliverables.get(DeliverableKind.SCOPE.value) or {}).get(
|
||||
"attachments", {}
|
||||
)
|
||||
if phase is PhaseId.SCOPING and scope.get(SCOPE_DATA_FILE):
|
||||
# What approving the scope commits to: how much the customer stated, how
|
||||
# much was assumed for them, and what is still unknown.
|
||||
try:
|
||||
agreed = json.loads(scope[SCOPE_DATA_FILE])
|
||||
except ValueError:
|
||||
agreed = {}
|
||||
facts["scope"] = {
|
||||
"kind": agreed.get("kind"),
|
||||
"assumed": [item.get("field") for item in agreed.get("assumed", [])],
|
||||
"left_to_decide": [
|
||||
item.get("field") for item in agreed.get("to_decide", [])
|
||||
],
|
||||
"unknown": [item.get("field") for item in agreed.get("to_ask", [])],
|
||||
}
|
||||
graph = read_graph(view.deliverables)
|
||||
if graph is not None:
|
||||
facts["target_architecture"] = graph.summary()
|
||||
@@ -776,6 +796,14 @@ def assembled_summary(phase: PhaseId, facts: Mapping[str, Any]) -> str:
|
||||
lines.append(
|
||||
", ".join(f"{count} {name}" for name, count in counts.items()) + "."
|
||||
)
|
||||
scope = facts.get("scope")
|
||||
if scope:
|
||||
lines.append(
|
||||
f"Scope of a {scope.get('kind') or 'workload'}: "
|
||||
f"{len(scope['assumed'])} fields assumed, "
|
||||
f"{len(scope['unknown'])} still unknown. Requirements are derived "
|
||||
"from it once you approve."
|
||||
)
|
||||
graph = facts.get("target_architecture")
|
||||
if graph:
|
||||
lines.append(
|
||||
|
||||
Reference in New Issue
Block a user