Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
Builder response to the independent review (rev 1.1)
Builder: agent 22b17a299d93. Each item of Independent-Vault-Review and what changed (rev 1.1); the response to Correction-Verification follows below. Scenario bodies T01–T40 and DG01–DG44, and the pending decisions Q01–Q25, were not changed.
| Item | Response |
|---|---|
| R01 reviewer identity | Corrected in Reviewer-Change-Record, Vault-Review-Record and this note. The change and review are attributed to workspace agent 0feb059240ac with limited independence; Kedar has not reviewed or approved the vault, and DG approval stays pending. My earlier draft wrongly attributed both to Kedar. The validator now fails if any note attributes the review or an approval to Kedar. The review itself is shipped unchanged. |
| R02 inventory checksum | source-inventory.csv no longer lists itself. A manifest cannot contain a valid hash of its own final bytes; the ZIP’s SHA-256 is published outside the ZIP in the delivery message. The validator recomputes every row from the bytes and the self-test confirms it detects a flipped byte in a temporary copy (Validation-Results). |
| R03 missing scripts | 11-Tooling/validate_vault.py and build_vault.py now ship with Tooling-README. The validator runs offline from the extracted vault and was run from the extracted ZIP, not from the builder’s folder. The builder is not reproducible offline: it reads the builder’s private working folders and was not re-run from the ZIP, so no rebuild claim is made; it is shipped as provenance and the regeneration procedure is stated honestly in the Tooling README. |
| R04 project-reference archive | Added 10-Sources/originals/balanced-architecture-sources.zip and 10-Sources/internal/dg-pilot-commercial-position.html, the latter with Pilot-Commercial-Position-Historical marking it INTERNAL and HISTORICAL / partly superseded, not a quote or current Balanced scope. The Source Inventory now says the six reference documents are retained duplicates (present under originals/ and tdd-bundle/reference-documents/), byte-identical, and checks that. |
| R05 build-step dependencies | Every step now has prerequisites, illustrative changes, outputs/invariants, a tests-first subset, deferred integration checks, follow-up verification and exit evidence. New Dependency-and-Regression-Table shows what can run early and what needs later steps. The base transactional-outbox contract moved into Step-01-Foundation; the worker stays in step 07. Early exit gates no longer imply later scenarios have passed; Step-11-UAT-and-Release rechecks integrated evidence. Manual service approval is stated as a parallel pre-sale / pre-real-data gate. No schema is fixed and no pending policy was resolved. |
| R06 exactly-once | Step-07-Outbox-Worker-Email exit evidence now says no duplicate business records or logical event/delivery identities, with at-least-once processing and ambiguous-provider reconciliation, and that duplicate external email cannot be categorically ruled out. The validator checks this. |
| R07 state diagram | Versions-and-State now separates the candidate-revision review states from the live-version pointer (V1 stays live while V2 is reviewed) and draws pause/close as an independent lifecycle. Reopen is not drawn; Q04/Q06 remain pending. |
| R08 audience | 00-Start-Here and README.txt state that this is an INTERNAL working vault, not DG-ready, with no client-safe or redacted claim, and that a DG export needs a separate reviewed selection. The earlier advice to delete three named files was removed. |
Final verdict follows the reviewer’s verification of these corrections.
Response to the second review (rev 1.2): F01–F04
Reviewer: Correction-Verification (shipped unchanged). Only consolidation notes were changed; no scenario body and no Q body changed.
| Item | Response |
|---|---|
| F01 defaults as prerequisites | Every step’s prerequisites now separate policy-independent scaffolding (allowed only after the overall start conditions) from decision-dependent behaviour and its final oracle, which stay blocked until DG chooses. “Proposed defaults” and “at least drafted” no longer appear as prerequisites. Provisional exploration must be reversible, unapproved and not accepted production behaviour. The pending Q notes are untouched. |
| F02 T37/T38 | Step 01 now covers only the configuration and harness subsets of T37 and T38. The dependency table makes T37 need steps 02, 03, 09 and the integrated recheck 11, and T38 need steps 07 and 10. Follow-up entries were added in those steps automatically from the table. |
| F03 manual rehearsals | Step 12 and Step 11 state that a purely manual service scenario needs no application build; evidence is the approved procedure/charter revision, consent-template revision, synthetic fixture, staff roles, date and recorded observed result. Scenarios that also assert a software boundary are linked to their software checks. Software UAT stays limited to the Balanced annex; manual cases are not a software payment gate. |
| F04 wording | ”Verified in step NN” is gone. Status cells now read “Eligible for … ; currently Not executed”. T40’s duplicated “11 and 11” is fixed. The remaining “Partially verified” phrasing was replaced by “only partial verification is possible”. |
Validation was re-run on a newly extracted ZIP (Validation-Results). Final verdict is the reviewer’s.