Commerce purchasing planning examination
Scope and method
Codex examined the inherited planning layer against the three supplied source revisions. This report uses the requested filename; the examination finished on 2026-10-23. The fleet’s instruction to commit on its supplied task branch governs this job, so no worktree landing or master update was performed. The authoring brief requested by the job is absent from the supplied documentation revision; finding 034 records that limit.
The review reads the conventions, artifact templates and the four broad approved CRM concepts as the writing standard. It checks source files and named anchors at the pinned revisions, compares assertions with the cited test bodies, and examines route authorization, service behavior, persistence constraints and the registered console surfaces. Test-file census and remaining-test title review identify coverage limits; this is a static specification examination, not a new execution of the Commerce or Accounting integration suites. No development resources or shared data were changed.
Every inherited module file and the six module-defined Commerce actor descriptions receive an OpenAI final wording pass. Product approval is not derived from implementation. Existing confirmed intent remains tied to the cited product decisions; observed behavior without such a decision remains proposed. Permanent identifiers and source revisions are retained, with new identifiers reserved before their records are written. Verification corrections and subsequent artifact rewrites are committed in reviewable units; newly identified behavior is authored directly in OpenAI wording.
Counts examined
| Measure | Result |
|---|---|
| Inherited module files | 58, including charter, findings and identifier registry |
| Features / broad concepts / capabilities / journeys / acceptance sets | 7 / 6 / 18 / 6 / 18 |
| Rule rows | 204 inherited; 210 final |
| Must-prove rules | 202 |
| Acceptance scenarios | 167 inherited; 173 final |
| Scenarios with pinned bindings | 168; 432 binding entries |
| Unbound proposed scenarios | 5 |
| Illustrative scenarios and edge cases | 27; 12 have unknown provenance |
| Journey steps / assertions | 33 / 17 |
| Actor descriptions | 6 |
| Findings / product questions | 35 / 5; four findings added |
| Concept body length | 555–617 words, six sections each |
Coverage at the pinned revisions
Coverage counts indicate a mapped scope item, not acceptance of every clause or a successful live deployment. The charter’s frontmatter coverage_catalog names the operation, storage, end-to-end file and permission-group mappings retained by this examination.
| Scope item | Covered / total | Uncovered or limited evidence |
|---|---|---|
| Declared business HTTP operations | 78 / 78 | None by name; health routes excluded from this count |
| Tables in the five registered modules | 32 / 32 | None by name; each maps to a capability |
| Published permission keys in nine scoped groups | 47 / 47 | Twelve have no operation; finding 018 names them |
| API end-to-end files | 37 / 37 | None unmapped; this count is separate from live browser proof |
| Unit, integration and API end-to-end files directly cited by a rule or scenario | 72 / 144 | 72 files lack direct row citation; named below under finding 033 |
| Owned scheduled functions | 1 / 1 | Checkout sweeper: cart expiry, reservation expiry, tender windows, billing/tender recovery, financial refresh, entitlement expiry and idempotency cleanup map to capabilities 001, 006, 007, 008, 010, 011 and 013; fulfilment-register work is delegated |
| Deploy registration functions | 1 / 1 | Participant registration maps to capability 012 |
| Owned state machines / queues | 0 / 0 | Delivery queues are outside this five-module boundary |
| Registered console pages | 4 / 4 | Orders list, direct detail, contact detail and New Order; Operations is outside this module |
| Complete browser acceptance bindings | 0 / 3 inherited proposals | Scenarios 007-14, 007-15 and 010-08 remain proposed; findings 003 and 032 |
| Must-prove rules with an acceptance scenario | 167 / 202 | 35 mandatory rules are explicitly assigned to finding 033 |
Purchasing’s reconciliation helper is covered by capability 018. The purchasing record identifies a caller in the neighboring inventory nightly function; the five-module scheduled-function count does not assert that the helper is an independently deployed schedule or that reconciliation automatically repairs missing cost.
Mandatory rules awaiting a scenario
Finding 033 retains these rule-specific gaps; a finding satisfies conformance bookkeeping without claiming acceptance proof.
BR-CAP-COM-ORD-001-10BR-CAP-COM-ORD-001-11BR-CAP-COM-ORD-001-12BR-CAP-COM-ORD-001-13BR-CAP-COM-ORD-002-03BR-CAP-COM-ORD-002-05BR-CAP-COM-ORD-003-11BR-CAP-COM-ORD-004-09BR-CAP-COM-ORD-004-10BR-CAP-COM-ORD-004-11BR-CAP-COM-ORD-005-13BR-CAP-COM-ORD-006-11BR-CAP-COM-ORD-006-12BR-CAP-COM-ORD-007-12BR-CAP-COM-ORD-008-09BR-CAP-COM-ORD-008-10BR-CAP-COM-ORD-009-07BR-CAP-COM-ORD-010-05BR-CAP-COM-ORD-011-04BR-CAP-COM-ORD-012-04BR-CAP-COM-ORD-012-09BR-CAP-COM-ORD-012-10BR-CAP-COM-ORD-012-11BR-CAP-COM-ORD-012-13BR-CAP-COM-ORD-013-12BR-CAP-COM-ORD-014-11BR-CAP-COM-ORD-014-12BR-CAP-COM-ORD-014-13BR-CAP-COM-ORD-014-14BR-CAP-COM-ORD-015-10BR-CAP-COM-ORD-015-11BR-CAP-COM-ORD-015-12BR-CAP-COM-ORD-016-10BR-CAP-COM-ORD-016-11BR-CAP-COM-ORD-018-13
Scenarios without pinned proof
Schedule-read acceptance is proposed because no bound test proves its complete side effects. Complete transfer acceptance is proposed because the unit test proves weighted rounding, while the source also promises handling of uncovered quantities and absence of a posting fact. Component tests and API fixtures support the other scenarios only at their stated level; they do not replace live browser or Accounting-contract validation.
Illustrative rows whose original source is unavailable
Finding 032 preserves the source limitation for the following rows. Their examples remain readable as unverified illustrations, and their provenance is unknown.
SC-CAP-COM-ORD-001-01SC-CAP-COM-ORD-002-01SC-CAP-COM-ORD-005-01SC-CAP-COM-ORD-006-02SC-CAP-COM-ORD-007-02SC-CAP-COM-ORD-008-01SC-CAP-COM-ORD-011-01SC-CAP-COM-ORD-014-01SC-CAP-COM-ORD-015-01SC-CAP-COM-ORD-016-01SC-CAP-COM-ORD-017-01SC-CAP-COM-ORD-018-01
Files not directly cited by a rule or bound scenario
These file names are census evidence, not newly approved behavioral claims. Existing capability mappings cover their containing operations; finding 033 retains the lack of a direct row-to-test citation.
services-commerce:modules/checkout/tests/e2e/engine-pricing.e2e.spec.jsservices-commerce:modules/checkout/tests/integration/db/checkouts.table.integration.spec.jsservices-commerce:modules/checkout/tests/integration/services/checkout/transaction-errors.integration.spec.jsservices-commerce:modules/checkout/tests/integration/services/persistence/accounting-products.queries.integration.spec.jsservices-commerce:modules/checkout/tests/integration/services/persistence/checkouts.queries.integration.spec.jsservices-commerce:modules/checkout/tests/integration/services/persistence/crm-affiliations.queries.integration.spec.jsservices-commerce:modules/checkout/tests/integration/services/persistence/party-addresses.queries.integration.spec.jsservices-commerce:modules/checkout/tests/integration/services/persistence/platform-users.queries.integration.spec.jsservices-commerce:modules/checkout/tests/unit/checkout/checkout-installments.spec.jsservices-commerce:modules/checkout/tests/unit/checkout/checkout-part-checks.spec.jsservices-commerce:modules/checkout/tests/unit/checkout/checkout-promotions.spec.jsservices-commerce:modules/checkout/tests/unit/checkout/checkout-shipping-offers.spec.jsservices-commerce:modules/checkout/tests/unit/checkout/order-discount-shares.spec.jsservices-commerce:modules/checkout/tests/unit/checkout/participant-calls.spec.jsservices-commerce:modules/checkout/tests/unit/checkout/process-ref-bound.spec.jsservices-commerce:modules/checkout/tests/unit/checkout/record-ids.spec.jsservices-commerce:modules/entitlements/tests/e2e/health.e2e.spec.jsservices-commerce:modules/entitlements/tests/integration/db/entitlements-tables.table.integration.spec.jsservices-commerce:modules/entitlements/tests/integration/services/persistence/entitlement-uses.queries.integration.spec.jsservices-commerce:modules/entitlements/tests/integration/services/persistence/entitlements.integration.spec.jsservices-commerce:modules/entitlements/tests/integration/services/persistence/entitlements.queries.integration.spec.jsservices-commerce:modules/entitlements/tests/unit/register/download-grant.spec.jsservices-commerce:modules/orders/tests/e2e/health.e2e.spec.jsservices-commerce:modules/orders/tests/e2e/order-extension-discount.e2e.spec.jsservices-commerce:modules/orders/tests/e2e/tenant-availability.e2e.spec.jsservices-commerce:modules/orders/tests/integration/db/orders.table.integration.spec.jsservices-commerce:modules/orders/tests/integration/db/post-purchase-tables.table.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/amendments/promotion-amendment-parts.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/amendments/promotion-amendment.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/billing/billing-request.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/billing/issue-before-tender.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/cancellations/cancellation-shipping-fence.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/installments/installments.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/persistence/amendments.queries.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/persistence/cancellations.queries.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/persistence/claims.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/persistence/financial-positions.queries.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/persistence/financial-reads.queries.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/persistence/orders.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/persistence/reservations.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/persistence/reservations.queries.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/persistence/return-policies.queries.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/persistence/returns.queries.integration.spec.jsservices-commerce:modules/orders/tests/integration/services/placement/promotion-parts-placement.integration.spec.jsservices-commerce:modules/orders/tests/unit/accounting/accounting-api.spec.jsservices-commerce:modules/orders/tests/unit/accounting/accounting-money.spec.jsservices-commerce:modules/orders/tests/unit/accounting/commerce-accounting-client.spec.jsservices-commerce:modules/orders/tests/unit/accounting/fixture-accounting-client.spec.jsservices-commerce:modules/orders/tests/unit/accounting/fixture-accounting-tax.spec.jsservices-commerce:modules/orders/tests/unit/accounting/fixture-installments.spec.jsservices-commerce:modules/orders/tests/unit/accounting/http-accounting-client.spec.jsservices-commerce:modules/orders/tests/unit/accounting/merchant-account-eligibility.spec.jsservices-commerce:modules/orders/tests/unit/accounting/service-accounting-client.spec.jsservices-commerce:modules/orders/tests/unit/amendments/amendment-plan.spec.jsservices-commerce:modules/orders/tests/unit/amendments/change-order-tax.spec.jsservices-commerce:modules/orders/tests/unit/amendments/promotion-amendment-plan.spec.jsservices-commerce:modules/orders/tests/unit/billing/deposit-invoice-request.spec.jsservices-commerce:modules/orders/tests/unit/billing/invoice-request-shipping.spec.jsservices-commerce:modules/orders/tests/unit/billing/invoice-tax.spec.jsservices-commerce:modules/orders/tests/unit/billing/line-credits.spec.jsservices-commerce:modules/orders/tests/unit/billing/purity.spec.jsservices-commerce:modules/orders/tests/unit/installments/installment-rules.spec.jsservices-commerce:modules/orders/tests/unit/orders/order-card-rule.spec.jsservices-commerce:modules/orders/tests/unit/promotions/frozen-answers.spec.jsservices-commerce:modules/orders/tests/unit/tender/tender-refusal-wording.spec.jsservices-commerce:modules/participants/tests/integration/services/persistence/participants.queries.integration.spec.jsservices-commerce:modules/participants/tests/unit/plain/plain-product-registration.spec.jsservices-commerce:modules/participants/tests/unit/registry/in-process-registry.spec.jsservices-commerce:modules/purchasing/tests/integration/db/purchasing-tables.table.integration.spec.jsservices-commerce:modules/purchasing/tests/integration/services/cost/lifo-costing.integration.spec.jsservices-commerce:modules/purchasing/tests/integration/services/persistence/business-unit-settings.queries.integration.spec.jsservices-commerce:modules/purchasing/tests/integration/services/persistence/purchasing-reads.integration.spec.js
Verification changes by artifact
The changes below correct the draft’s factual statements, evidence level or source anchors. Rewording is separately accounted for in the final-text table.
| Artifact or row | Examination change |
|---|---|
FINDINGS | Resolved descriptive anchors to literal record headings/decisions; added findings 032–035. |
JNY-COM-ORD-003 | Rendered sample data does not independently prove agreement with live Accounting. Applied source/provenance corrections where required; preserved stable IDs and approval status. |
JNY-COM-ORD-002 | Separated billing and gate opening from completed delivery, and narrowed hand-off/mirror assertions to actual fixtures. Applied source/provenance corrections where required; preserved stable IDs and approval status. |
JNY-COM-ORD-001 | Placement-step expectation now matches the pinned placement test’s pending billing state. Applied source/provenance corrections where required; preserved stable IDs and approval status. Narrowed step 8 to its tender-panel component assertions and assertion 1 to retry acceptance; cart uniqueness remains in the placement capability rather than the tender test. |
ATS-COM-ORD-002 | Matched the currency pair and policy snapshot assertions to the bound tests. Applied source/provenance corrections where required; preserved stable IDs and approval status. |
ATS-COM-ORD-017-04 | Classified the set by its integration and API execution bindings. |
ATS-COM-ORD-017 | Applied source/provenance corrections where required; preserved stable IDs and approval status. |
ATS-COM-ORD-010 | Applied source/provenance corrections where required; preserved stable IDs and approval status. |
ATS-COM-ORD-012-07 | Classified its placement/billing/delivery binding as API evidence rather than unit evidence. |
ATS-COM-ORD-012 | Applied source/provenance corrections where required; preserved stable IDs and approval status. |
ATS-COM-ORD-014 | Aligned refund arithmetic and override expectations with the planner. Applied source/provenance corrections where required; preserved stable IDs and approval status. |
ATS-COM-ORD-007-04 | Matched the expectation to the masked token assertion. |
ATS-COM-ORD-007 | Applied source/provenance corrections where required; preserved stable IDs and approval status. |
ATS-COM-ORD-003 | Corrected tax fixtures and described ship-to bindings as helper tests, not executed preview/placement routes. Applied source/provenance corrections where required; preserved stable IDs and approval status. |
ATS-COM-ORD-004-06 | Removed an inconsistent fixed discount amount from the registration fixture. |
ATS-COM-ORD-004 | Applied source/provenance corrections where required; preserved stable IDs and approval status. |
CON-COM-ORD-002 | Corrected the universal checkout origin and the claim that voided orders were never paid. Applied source/provenance corrections where required; preserved stable IDs and approval status. |
CAP-COM-ORD-006 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-006-11, BR-CAP-COM-ORD-006-12. Unbound rules are enumerated in FND-COM-ORD-033. |
CAP-COM-ORD-002 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-002-03, BR-CAP-COM-ORD-002-05. Unbound rules are enumerated in FND-COM-ORD-033. |
CAP-COM-ORD-005 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-005-13. Unbound rules are enumerated in FND-COM-ORD-033. |
CAP-COM-ORD-003 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-003-11. Unbound rules are enumerated in FND-COM-ORD-033. |
BR-CAP-COM-ORD-018-13 | Included transfer-out movements; separated reconciliation behavior from its nightly caller outside this module. |
CAP-COM-ORD-018 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Added BR-CAP-COM-ORD-018-14 with acceptance scenario ATS-COM-ORD-018-14; bound calculation/flow evidence. Added BR-CAP-COM-ORD-018-15 with acceptance scenario ATS-COM-ORD-018-15; bound calculation/flow evidence. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-018-13. Unbound rules are enumerated in FND-COM-ORD-033. |
BR-CAP-COM-ORD-014-05 | Separated invoice credit from funded refund, including fraction and fee deductions. |
BR-CAP-COM-ORD-014-08 | Removed unconditional immediate execution under override; the approval threshold still applies. |
CAP-COM-ORD-014 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Added BR-CAP-COM-ORD-014-15 with acceptance scenario ATS-COM-ORD-014-12; proposed route proof. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-014-11, BR-CAP-COM-ORD-014-12, BR-CAP-COM-ORD-014-13, BR-CAP-COM-ORD-014-14. Unbound rules are enumerated in FND-COM-ORD-033. |
BR-CAP-COM-ORD-004-01 | Recorded boundary trimming rather than preserving surrounding whitespace. |
CAP-COM-ORD-004 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-004-09, BR-CAP-COM-ORD-004-10, BR-CAP-COM-ORD-004-11. Unbound rules are enumerated in FND-COM-ORD-033. |
CAP-COM-ORD-011 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-011-04. Unbound rules are enumerated in FND-COM-ORD-033. |
BR-CAP-COM-ORD-013-08 | The code revokes active grants even when their uses are fully consumed. |
CAP-COM-ORD-013 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-013-12. Unbound rules are enumerated in FND-COM-ORD-033. |
BR-CAP-COM-ORD-012-12 | Removed the unproved guarantee that no placement can ever deadlock. |
CAP-COM-ORD-012 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-012-04, BR-CAP-COM-ORD-012-09, BR-CAP-COM-ORD-012-10, BR-CAP-COM-ORD-012-11, BR-CAP-COM-ORD-012-13. Unbound rules are enumerated in FND-COM-ORD-033. |
CAP-COM-ORD-001 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-001-10, BR-CAP-COM-ORD-001-11, BR-CAP-COM-ORD-001-12, BR-CAP-COM-ORD-001-13. Unbound rules are enumerated in FND-COM-ORD-033. |
CAP-COM-ORD-016 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-016-10, BR-CAP-COM-ORD-016-11. Unbound rules are enumerated in FND-COM-ORD-033. |
CAP-COM-ORD-015 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Added BR-CAP-COM-ORD-015-13 with acceptance scenario ATS-COM-ORD-015-10; bound calculation/flow evidence. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-015-10, BR-CAP-COM-ORD-015-11, BR-CAP-COM-ORD-015-12. Unbound rules are enumerated in FND-COM-ORD-033. |
CAP-COM-ORD-017 | Applied source/provenance corrections where required; preserved stable IDs and approval status. |
CAP-COM-ORD-008 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-008-09, BR-CAP-COM-ORD-008-10. Unbound rules are enumerated in FND-COM-ORD-033. |
BR-CAP-COM-ORD-007-04 | Corrected token suffix versus card last-four; the backend test does not establish the separate card form. |
CAP-COM-ORD-007 | Applied source/provenance corrections where required; preserved stable IDs and approval status. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-007-12. Unbound rules are enumerated in FND-COM-ORD-033. |
CAP-COM-ORD-009 | Added BR-CAP-COM-ORD-009-08 with acceptance scenario ATS-COM-ORD-009-07; proposed route proof. Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-009-07. Unbound rules are enumerated in FND-COM-ORD-033. |
CAP-COM-ORD-010 | Marked refusal, calculation and side-effect rules must_prove: BR-CAP-COM-ORD-010-05. Unbound rules are enumerated in FND-COM-ORD-033. |
CAP-COM-ORD-001 / ATS-COM-ORD-001 / CON-COM-ORD-001 | Added rule 14, acceptance scenario 10 and the cancelled cart state, sourced to persistence and its integration tests. |
ATS-COM-ORD-018-14 | Removed a unit binding that establishes rounding alone, not the complete rule; complete transfer acceptance is proposed at API level. |
JNY-COM-ORD-004 | Narrowed the failure branch to repeated voiding, which its cited test actually rejects. |
JNY-COM-ORD-006 | Separated layer valuation from unconditional quantity agreement; reconciliation is not a guarantee that mismatches cannot exist. |
ATS-COM-ORD-014-12 | Bound waiting line-grain refusal to the exact pinned cancellation-plan test; provenance is test. |
The identifier registry advances the rule and acceptance sequences for cart lifecycle, schedule reads, whole-line cancellation, proration, transfers and stock adjustments. Capability grain remains eighteen outcomes and concept grain remains six broad nouns; no merge, split, reuse or renumbering is needed. Actor descriptions now distinguish responsibilities from predefined security roles, retain the portal’s deferred status and avoid treating a support fixture as integrated identity proof.
Exact metadata corrections
This table lists every changed inherited source, provenance, enforcement, intent-origin anchor, proof flag or binding. Array positions identify the existing structural location; the row identifier identifies the permanent record. New rows are described above and do not have inherited metadata to compare. No source_sha, supersedes, product_intent, implementation_evidence or approval status value is changed.
| Record | Field | Previous value | Examined value |
|---|---|---|---|
FINDINGS.md | finding_evidence.0.source | ["services-commerce:docs/milestones/plans/COMM-M2-plan.md#header and closing line","services-commerce:docs/milestones/README.md#Records (COMM-M2 plan approved 2026-10-21)","services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#header","services-commerce:docs/forge-handoff/commerce.md#C. Decisions"] | ["services-commerce:docs/milestones/plans/COMM-M2-plan.md#Status: Proposed","services-commerce:docs/milestones/README.md#COMM-M2 plan (approved 2026-10-21","services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#Andrew asked (2026-10-21)","services-commerce:docs/forge-handoff/commerce.md#C. Decisions"] |
FINDINGS.md | finding_evidence.2.source | ["react-console:acceptance (no commerce directory at baf6dae3)","react-console branch comm-m2-run-4-base at 7307008c: acceptance/commerce/inventory, journeys, playwright","services-commerce:docs/forge-handoff/commerce.md#D. Current state"] | ["react-console:components/order-composer/__tests__/live-composer.test.tsx","services-commerce:docs/forge-handoff/commerce.md#D. Current state"] |
FINDINGS.md | finding_evidence.6.source | ["services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#Product purchase eligibility enforced (Functions)","services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#Decisions of 2026-10-22 (M2-E)","services-commerce:aws/commerce.service-calls.ts:PLATFORM_SERVICE_FUNCTIONS_PUBLISHED"] | ["services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#Product purchase eligibility enforced (Platform PLAT-M11 D6; Andrew approved 2026-10-21)","services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#Decisions of 2026-10-22 (Andrew, question tool, ~10:18 ET)","services-commerce:aws/commerce.service-calls.ts:PLATFORM_SERVICE_FUNCTIONS_PUBLISHED"] |
FINDINGS.md | finding_evidence.7.source | ["services-commerce:docs/forge-handoff/commerce.md#C. Decisions (My own assumptions)","services-commerce:docs/milestones/plans/COMM-M2-shipto-and-support.md#Reading taken (please confirm)","services-commerce:modules/checkout/tests/unit/checkout/ship-to-no-address.spec.js#is a blocking problem with the code and the message Andrew decided"] | ["services-commerce:docs/forge-handoff/commerce.md#C. Decisions","services-commerce:docs/milestones/plans/COMM-M2-shipto-and-support.md#Reading taken (please confirm)","services-commerce:modules/checkout/tests/unit/checkout/ship-to-no-address.spec.js#is a blocking problem with the code and the message Andrew decided"] |
FINDINGS.md | finding_evidence.10.source | ["services-commerce:docs/milestones/plans/COMM-M2-repairs-1.md#1. COM-ACC-0319 (Left alone)"] | ["services-commerce:docs/milestones/plans/COMM-M2-repairs-1.md#1. COM-ACC-0319"] |
FINDINGS.md | finding_evidence.11.source | ["services-commerce:docs/milestones/plans/COMM-M2-repairs-2.md#R2-1 (P0): a part-paid void ends completed (Not proved here)"] | ["services-commerce:docs/milestones/plans/COMM-M2-repairs-2.md#R2-1 (P0): a part-paid void ends completed"] |
FINDINGS.md | finding_evidence.12.source | ["services-commerce:docs/milestones/plans/COMM-M2-W1-report.md#Things to know / for Andrew (5)"] | ["services-commerce:docs/milestones/plans/COMM-M2-W1-report.md#Things to know / for Andrew"] |
FINDINGS.md | finding_evidence.14.source | ["services-commerce:docs/milestones/plans/COMM-M2-plan.md#8. Dependencies (Accounting: receivable events delivered to Commerce)","services-commerce:docs/milestones/plans/COMM-M2-plan.md#3. How it works for the user (step 13)"] | ["services-commerce:docs/milestones/plans/COMM-M2-plan.md#8. Dependencies","services-commerce:docs/milestones/plans/COMM-M2-plan.md#3. How it works for the user"] |
FINDINGS.md | finding_evidence.16.source | ["services-commerce:docs/milestones/plans/COMM-M2-W1-report.md#Things to know / for Andrew (2)","react-console:app/(console)/console/[tenantId]/orders/[orderId]/page.tsx"] | ["services-commerce:docs/milestones/plans/COMM-M2-W1-report.md#Things to know / for Andrew","react-console:app/(console)/console/[tenantId]/orders/[orderId]/page.tsx"] |
FINDINGS.md | finding_evidence.17.source | ["services-commerce:aws/commerce.service.ts (CheckoutsPermissions, OrdersPermissions, ReturnPoliciesPermissions, PurchasingPermissions, InventoryCostingPermissions)","services-commerce:modules/orders/aws/api/post-purchase.routes.ts"] | ["services-commerce:aws/commerce.service.ts:OrdersPermissions","services-commerce:modules/orders/aws/api/post-purchase.routes.ts"] |
FINDINGS.md | finding_evidence.18.source | ["react-console:app/(console)/console/[tenantId]/crm/contacts/[id]/orders/**","react-console:components/commerce/orders/**","react-console:components/console/order/**","react-console:app/(console)/console/[tenantId]/orders/operations/page.tsx"] | ["react-console:app/(console)/console/[tenantId]/crm/contacts/[id]/orders/new/page.tsx","react-console:components/commerce/orders/orders-list-screen.tsx","react-console:components/console/order/order-360-live.tsx"] |
FINDINGS.md | finding_evidence.19.source | ["services-commerce:docs/milestones/plans/COMM-M2-D10-report.md#Decisions for Andrew / follow-ups (5)"] | ["services-commerce:docs/milestones/plans/COMM-M2-D10-report.md#Decisions for Andrew / follow-ups"] |
FINDINGS.md | finding_evidence.20.source | ["services-commerce:docs/milestones/plans/COMM-M2-D10-report.md#Decisions for Andrew / follow-ups (7)","services-commerce:docs/milestones/plans/COMM-M2-plan.md#D10"] | ["services-commerce:docs/milestones/plans/COMM-M2-D10-report.md#Decisions for Andrew / follow-ups","services-commerce:docs/milestones/plans/COMM-M2-plan.md#D10"] |
FINDINGS.md | finding_evidence.22.source | ["services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#Product purchase eligibility enforced (Not in this part)","services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#Open points for Andrew"] | ["services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#Product purchase eligibility enforced (Platform PLAT-M11 D6; Andrew approved 2026-10-21)","services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#Open points for Andrew"] |
FINDINGS.md | finding_evidence.23.source | ["services-commerce:docs/milestones/plans/COMM-M2-plan.md#D7 (Today: Built)"] | ["services-commerce:docs/milestones/plans/COMM-M2-plan.md#D7"] |
FINDINGS.md | finding_evidence.25.source | ["services-commerce:docs/milestones/plans/COMM-M2-plan.md#2. Scope (Excluded)"] | ["services-commerce:docs/milestones/plans/COMM-M2-plan.md#2. Scope"] |
FINDINGS.md | finding_evidence.26.source | ["services-commerce:docs/migrations/post-purchase/README.md#What waits (as first built; see \"What waits, after this extension\" above for what still stands)","services-commerce:docs/milestones/README.md#COMM-M4 row"] | ["services-commerce:docs/migrations/post-purchase/README.md#What waits (as first built; see \"What waits, after this extension\" above for what still stands)","services-commerce:docs/milestones/README.md#COMM-M4"] |
FINDINGS.md | finding_evidence.27.source | ["services-commerce:docs/milestones/plans/COMM-M2-W1-report.md#Things to know / for Andrew (3)"] | ["services-commerce:docs/milestones/plans/COMM-M2-W1-report.md#Things to know / for Andrew"] |
FINDINGS.md | finding_evidence.29.source | ["services-commerce:docs/milestones/README.md#milestones table","services-commerce:docs/milestones/plans/COMM-realignment-2026-10-22.md#5. The milestones, revised"] | ["services-commerce:docs/milestones/README.md#COMM-M4","services-commerce:docs/milestones/plans/COMM-realignment-2026-10-22.md#5. The milestones, revised"] |
FINDINGS.md | finding_evidence.30.source | ["services-commerce:docs/milestones/README.md#COMM-M5 row","services-commerce:docs/migrations/purchasing/README.md#What waits"] | ["services-commerce:docs/milestones/README.md#COMM-M5","services-commerce:docs/migrations/purchasing/README.md#What waits"] |
ATS-COM-ORD-017-04 | scenarios.3.level | "unit" | "api" |
ATS-COM-ORD-010-08 | scenarios.7.source | "react-console:acceptance/commerce/journeys/console/COM-ACC-0867.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
ATS-COM-ORD-012-07 | scenarios.6.level | "unit" | "api" |
ATS-COM-ORD-007-14 | scenarios.13.source | "react-console:acceptance/commerce/journeys/console/COM-ACC-0857.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
ATS-COM-ORD-007-15 | scenarios.14.source | "react-console:acceptance/commerce/journeys/console/COM-ACC-0864.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
CON-COM-ORD-002 | relationships.0.provenance | "test" | "observed" |
CON-COM-ORD-002 | relationships.0.source | "services-commerce:modules/checkout/tests/e2e/placement.e2e.spec.js#leaves the checkout placed, naming the order, its items frozen with what prepare attested, and its trail telling the story" | "services-commerce:modules/orders/db/orders.table.ts:orders" |
BR-CAP-COM-ORD-006-11 | rules.10.must_prove | false | true |
BR-CAP-COM-ORD-006-12 | rules.11.must_prove | false | true |
SC-CAP-COM-ORD-006-02 | edge_cases.0.provenance | "documented" | "unknown" |
SC-CAP-COM-ORD-006-02 | edge_cases.0.source | "react-console:acceptance/commerce/journeys/billing/COM-ACC-0288.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
CAP-COM-ORD-002 | intent_sources | ["services-commerce:docs/milestones/COMM-M1-set-up-what-you-sell.md#D9","services-commerce:docs/milestones/plans/COMM-M2-plan.md#A6","services-commerce:docs/milestones/plans/COMM-M2-plan.md#9. Acceptance scenarios (COMM-M2-X02)"] | ["services-commerce:docs/milestones/COMM-M1-set-up-what-you-sell.md#D9","services-commerce:docs/milestones/plans/COMM-M2-plan.md#A6","services-commerce:docs/milestones/plans/COMM-M2-plan.md#COMM-M2-X02"] |
BR-CAP-COM-ORD-002-03 | rules.2.must_prove | false | true |
BR-CAP-COM-ORD-002-05 | rules.4.must_prove | false | true |
BR-CAP-COM-ORD-002-08 | rules.7.origin | "services-commerce:docs/milestones/plans/COMM-M2-plan.md#9. Acceptance scenarios (COMM-M2-X02)" | "services-commerce:docs/milestones/plans/COMM-M2-plan.md#COMM-M2-X02" |
SC-CAP-COM-ORD-002-01 | scenarios.0.provenance | "documented" | "unknown" |
SC-CAP-COM-ORD-002-01 | scenarios.0.source | "react-console:acceptance/commerce/journeys/checkout/COM-ACC-0032.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
BR-CAP-COM-ORD-005-13 | rules.12.must_prove | false | true |
SC-CAP-COM-ORD-005-01 | scenarios.0.provenance | "documented" | "unknown" |
SC-CAP-COM-ORD-005-01 | scenarios.0.source | "react-console:acceptance/commerce/journeys/checkout/COM-ACC-0004.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
CAP-COM-ORD-003 | intent_sources | ["services-commerce:docs/milestones/plans/COMM-M2-plan.md#2. Scope","services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#Product purchase eligibility enforced (Platform PLAT-M11 D6; Andrew approved 2026-10-21)","services-commerce:docs/milestones/plans/COMM-realignment-2026-10-22.md#4. Decisions for Andrew (D-T4)","services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#M2-S1","services-commerce:docs/milestones/plans/COMM-M2-plan.md#D9","services-commerce:docs/milestones/COMM-M1-set-up-what-you-sell.md#D14"] | ["services-commerce:docs/milestones/plans/COMM-M2-plan.md#2. Scope","services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#Product purchase eligibility enforced (Platform PLAT-M11 D6; Andrew approved 2026-10-21)","services-commerce:docs/milestones/plans/COMM-realignment-2026-10-22.md#D-T4","services-commerce:docs/milestones/COMM-M2-take-a-staff-order.md#M2-S1","services-commerce:docs/milestones/plans/COMM-M2-plan.md#D9","services-commerce:docs/milestones/COMM-M1-set-up-what-you-sell.md#D14"] |
BR-CAP-COM-ORD-003-05 | rules.4.origin | "services-commerce:docs/milestones/plans/COMM-realignment-2026-10-22.md#4. Decisions for Andrew (D-T4)" | "services-commerce:docs/milestones/plans/COMM-realignment-2026-10-22.md#D-T4" |
BR-CAP-COM-ORD-003-11 | rules.10.must_prove | false | true |
BR-CAP-COM-ORD-018-13 | rules.12.must_prove | false | true |
BR-CAP-COM-ORD-018-13 | rules.12.provenance | "test" | "observed" |
BR-CAP-COM-ORD-018-13 | rules.12.source | "services-commerce:modules/purchasing/tests/integration/services/receiving/purchasing-flow.integration.spec.js#raises valuation_mismatch on stock no layer costs, relief_missing on a shipment movement no relief followed, and nothing on the reconciled items" | "services-commerce:modules/purchasing/services/valuation/inventory-valuation.ts:raiseCostFindings" |
SC-CAP-COM-ORD-018-01 | scenarios.0.provenance | "documented" | "unknown" |
SC-CAP-COM-ORD-018-01 | scenarios.0.source | "react-console:acceptance/commerce/journeys/inventory/COM-ACC-0460.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
BR-CAP-COM-ORD-014-11 | rules.10.must_prove | false | true |
BR-CAP-COM-ORD-014-12 | rules.11.must_prove | false | true |
BR-CAP-COM-ORD-014-13 | rules.12.must_prove | false | true |
BR-CAP-COM-ORD-014-14 | rules.13.must_prove | false | true |
SC-CAP-COM-ORD-014-01 | scenarios.0.provenance | "documented" | "unknown" |
SC-CAP-COM-ORD-014-01 | scenarios.0.source | "react-console:acceptance/commerce/journeys/post-purchase/COM-ACC-0600.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
BR-CAP-COM-ORD-004-09 | rules.8.must_prove | false | true |
BR-CAP-COM-ORD-004-10 | rules.9.must_prove | false | true |
BR-CAP-COM-ORD-004-11 | rules.10.must_prove | false | true |
BR-CAP-COM-ORD-009-07 | rules.6.must_prove | false | true |
BR-CAP-COM-ORD-010-05 | rules.4.must_prove | false | true |
BR-CAP-COM-ORD-011-04 | rules.3.must_prove | false | true |
SC-CAP-COM-ORD-011-01 | scenarios.0.provenance | "documented" | "unknown" |
SC-CAP-COM-ORD-011-01 | scenarios.0.source | "react-console:acceptance/commerce/journeys/billing/COM-ACC-0311.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
BR-CAP-COM-ORD-013-12 | rules.11.must_prove | false | true |
BR-CAP-COM-ORD-012-04 | rules.3.must_prove | false | true |
BR-CAP-COM-ORD-012-09 | rules.8.must_prove | false | true |
BR-CAP-COM-ORD-012-10 | rules.9.must_prove | false | true |
BR-CAP-COM-ORD-012-11 | rules.10.must_prove | false | true |
BR-CAP-COM-ORD-012-13 | rules.12.must_prove | false | true |
BR-CAP-COM-ORD-001-10 | rules.9.must_prove | false | true |
BR-CAP-COM-ORD-001-11 | rules.10.must_prove | false | true |
BR-CAP-COM-ORD-001-12 | rules.11.must_prove | false | true |
BR-CAP-COM-ORD-001-13 | rules.12.must_prove | false | true |
SC-CAP-COM-ORD-001-01 | scenarios.0.provenance | "documented" | "unknown" |
SC-CAP-COM-ORD-001-01 | scenarios.0.source | "react-console:acceptance/commerce/journeys/checkout/COM-ACC-0018.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
CAP-COM-ORD-016 | intent_sources | ["services-commerce:docs/migrations/post-purchase/README.md#The return label's fee and the change order's tax (decisions P and Q, 2026-10-18) (D-P7-32)"] | ["services-commerce:docs/migrations/post-purchase/README.md#D-P7-32"] |
BR-CAP-COM-ORD-016-08 | rules.7.origin | "services-commerce:docs/migrations/post-purchase/README.md#The return label's fee and the change order's tax (decisions P and Q, 2026-10-18) (D-P7-32)" | "services-commerce:docs/migrations/post-purchase/README.md#D-P7-32" |
BR-CAP-COM-ORD-016-10 | rules.9.must_prove | false | true |
BR-CAP-COM-ORD-016-11 | rules.10.must_prove | false | true |
SC-CAP-COM-ORD-016-01 | scenarios.0.provenance | "documented" | "unknown" |
SC-CAP-COM-ORD-016-01 | scenarios.0.source | "react-console:acceptance/commerce/journeys/post-purchase/COM-ACC-0608.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
CAP-COM-ORD-015 | intent_sources | ["services-commerce:docs/migrations/post-purchase/README.md#The return label's fee and the change order's tax (decisions P and Q, 2026-10-18) (D-P7-33)","services-commerce:docs/milestones/COMM-M1-set-up-what-you-sell.md#D12-F1"] | ["services-commerce:docs/migrations/post-purchase/README.md#D-P7-33","services-commerce:docs/milestones/COMM-M1-set-up-what-you-sell.md#D12-F1"] |
BR-CAP-COM-ORD-015-04 | rules.3.origin | "services-commerce:docs/migrations/post-purchase/README.md#The return label's fee and the change order's tax (decisions P and Q, 2026-10-18) (D-P7-33)" | "services-commerce:docs/migrations/post-purchase/README.md#D-P7-33" |
BR-CAP-COM-ORD-015-10 | rules.9.must_prove | false | true |
BR-CAP-COM-ORD-015-11 | rules.10.must_prove | false | true |
BR-CAP-COM-ORD-015-12 | rules.11.must_prove | false | true |
SC-CAP-COM-ORD-015-01 | scenarios.0.provenance | "documented" | "unknown" |
SC-CAP-COM-ORD-015-01 | scenarios.0.source | "react-console:acceptance/commerce/journeys/post-purchase/COM-ACC-0616.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
SC-CAP-COM-ORD-017-01 | scenarios.0.provenance | "documented" | "unknown" |
SC-CAP-COM-ORD-017-01 | scenarios.0.source | "react-console:acceptance/commerce/journeys/inventory/COM-ACC-0473.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
BR-CAP-COM-ORD-008-09 | rules.8.must_prove | false | true |
BR-CAP-COM-ORD-008-10 | rules.9.must_prove | false | true |
SC-CAP-COM-ORD-008-01 | scenarios.0.provenance | "documented" | "unknown" |
SC-CAP-COM-ORD-008-01 | scenarios.0.source | "react-console:acceptance/commerce/journeys/billing/COM-ACC-0297.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
BR-CAP-COM-ORD-007-04 | rules.3.enforced_at | ["service","console"] | ["service"] |
BR-CAP-COM-ORD-007-12 | rules.11.must_prove | false | true |
SC-CAP-COM-ORD-007-02 | edge_cases.0.provenance | "documented" | "unknown" |
SC-CAP-COM-ORD-007-02 | edge_cases.0.source | "react-console:acceptance/commerce/journeys/billing/COM-ACC-0301.json (branch comm-m2-run-4-base)" | "FND-COM-ORD-032" |
Open disagreements
All inherited findings remain visible rather than being silently closed by wording changes. Several document historical reports and require follow-up against the current implementation or deployment; this examination does not assert their live reproduction. The four added findings separate unavailable sources, incomplete proof, the missing brief and write-performing schedule reads.
| Finding | Severity | Kind | Remaining concern |
|---|---|---|---|
FND-COM-ORD-001 | medium | inconsistency | The staff-order plan retains a pending approval label, but the milestone index, milestone record and handoff record Andrew’s approval and instruction to build on the recommended choices. Confirmed intent here follows those approval records. The product should reconcile the plan’s stale approval text. |
FND-COM-ORD-002 | low | inconsistency | The milestone index and individual milestone record disagree about progress: the index retains an in-progress catalog entry and omits the staff-order record, while the individual record reports catalog acceptance. The product should update the index to match the authoritative records. |
FND-COM-ORD-003 | medium | inconsistency | The pinned console revision contains component tests but lacks the draft’s referenced acceptance inventory and browser journey specifications. Earlier identifiers remain in supersedes as historical seeds. Browser acceptance remains proposed because the named browser proof cannot be bound at this revision. |
FND-COM-ORD-004 | medium | debt | The installment engine currently coordinates with Accounting, while the realignment record assigns future installment ownership to Billing. Approval of the full revised milestone sequence is still pending. The product should define the handover before promising a customer-facing plan workflow. |
FND-COM-ORD-005 | medium | inconsistency | Tax ownership differs across the staff-order plan and the later realignment. The records describe an interim Commerce zone provider and an Accounting provider that is not enabled. The settled no-tax-address refusal does not confirm every provider, zone or address-selection choice; those choices remain proposed. |
FND-COM-ORD-006 | medium | inconsistency | The Accounting tax refusal test expects a bad-request response at placement, unlike the conflict response used by other placement refusals. The recorded review leaves that difference in place. The product should decide whether callers should handle one consistent refusal shape. |
FND-COM-ORD-007 | low | inconsistency | The staff-order narrative retains an earlier statement that eligibility service publication is unavailable. The pinned service-call declaration and later milestone entry show publication and switch-on. The product should remove the stale dependency statement. |
FND-COM-ORD-008 | medium | inconsistency | The no-address ship-to refusal extends the recorded deleted-contact decision, but its test describes the message as Andrew’s decision. Shipping’s refusal also differs from the tax path’s buyer-address fallback. The product should resolve the intended shared address behavior. |
FND-COM-ORD-009 | medium | debt | Pure helper tests exercise the two ship-to checks. They do not establish preview and placement behavior through the complete API paths, and the draft declares no compliance control for the checks. The product should add route-level proof before relying on their complete purchase coverage. |
FND-COM-ORD-010 | low | inconsistency | The documented prepayment delivery exception applies to console terms purchases; the portal terms path still waits for payment. The milestone record identifies that distinction as unresolved product behavior. |
FND-COM-ORD-011 | medium | debt | The repair record reports that a failed promotion-sum invariant reaches the caller as an unexplained server outcome. The product should specify a usable refusal and retain a scenario for the invariant failure. |
FND-COM-ORD-012 | medium | debt | The partial-payment void evidence uses an Accounting stand-in that does not model real Accounting’s over-application rejection. It therefore does not establish that the production contract accepts credit after refund. The product should validate the settlement ordering against the actual Accounting contract. |
FND-COM-ORD-013 | low | debt | The order-list report describes full order reads for each row, including lines, tenders and invoices. It identifies a smaller list response as future work. The product should assess that work using realistic list volume rather than infer scalability from the current page size. |
FND-COM-ORD-014 | medium | debt | The repair record identifies different process-reference length limits in checkout and the shared participant contract. Long references can be omitted when passed to an application. The product should align the limits and prove the full reference survives the call. |
FND-COM-ORD-015 | medium | inconsistency | The staff-order plan expects prompt financial updates after Accounting payments, while its dependency record reports missing receivable events in development. Sweep-based refresh remains the documented fallback; this examination does not establish that live event delivery has since recovered. |
FND-COM-ORD-016 | low | defect | The shipping repair record describes placement rejecting a shipping charge whose policy has no shipping product, although preview does not surface the configuration problem. The product should expose that blocker before staff attempt placement. |
FND-COM-ORD-017 | low | inconsistency | The list report describes organization order detail as contact-route-only. The pinned console also provides the workspace Orders detail route. The product should reconcile the report with the available route. |
FND-COM-ORD-018 | low | debt | Twelve published permission keys have no corresponding operation in this scope: checkout delete and bulk; order update, delete and bulk; return-policy update and bulk; purchasing bulk; and inventory-costing create, delete and bulk. Return-policy replacement uses deletion and creation because no edit operation exists. |
FND-COM-ORD-019 | medium | inconsistency | The inherited scope description overlooks contact-based order pages, the list and detail components, and their supporting composer and list layers. Operations shares the Orders area but belongs to fulfilment. The module’s source and coverage declarations distinguish these boundaries; this examination changes only the authorized registry status. |
FND-COM-ORD-020 | medium | defect | The post-sale promotion report describes audience-restricted promotions being refused without an eligibility verdict, even for a qualifying buyer. The product should establish and prove the intended eligibility evaluation for this amendment path. |
FND-COM-ORD-021 | low | inconsistency | The promotion report records a generic eligibility refusal where the plan proposes a more specific message for a nonmember-only offer. The product should choose the customer explanation and align the scenario with that choice. |
FND-COM-ORD-022 | low | inconsistency | The earlier staff-order walkthrough includes Membership purchases, but a later recorded decision hides Membership in the live composer until its commerce milestone. The product should align the walkthrough with that restriction; same-purchase member pricing is not a complete live staff journey at this stage. |
FND-COM-ORD-023 | medium | debt | The milestone record distinguishes purchase-eligibility checks in cart preview and placement from quotes and staff promotion preview that do not apply them. A quoted amount consequently does not establish permission to buy. The product should resolve that catalog boundary with its owning module. |
FND-COM-ORD-024 | low | debt | The same-purchase member-price evidence uses a stand-in participant. Membership’s actual declaration of package-granted audiences remains a dependency. The product should obtain proof from that application before treating the integration as complete. |
FND-COM-ORD-025 | low | debt | The plain-product participant declares the Accounting product type, while the recorded donation decision is conditional on donations using orders. No donation type is declared here. The product should decide that route before adding the type. |
FND-COM-ORD-026 | medium | debt | The draft identifies no console configuration screen for product grants and records removal of the Accounting product entitlement section. Grant declaration is available through the API, while the later entitlement milestone remains proposed. The product should define the configuration experience before claiming a staff workflow. |
FND-COM-ORD-027 | medium | debt | The after-sale record leaves live console integration, execution of future-dated amendments, automatic return-authorization expiry and fee waiver work outstanding. Existing sample-data dialogs do not prove those operational outcomes. The product should resolve the remaining scope before designing self-service changes. |
FND-COM-ORD-028 | low | inconsistency | The order-list report notes that a cancelled purchase refunded to zero meets the money-based Paid filter. It asks whether that grouping serves managers. The product should confirm whether financial position alone determines the filter. |
FND-COM-ORD-029 | low | undocumented | The support-attribution report relies on a stand-in identity and does not verify Platform’s actual support actor identifier. The product should verify that identity before treating the attribution as an integrated support workflow. |
FND-COM-ORD-030 | low | inconsistency | The milestone index and proposed realignment assign different numbers to after-sale and merchandise work after inserting tax work. Earlier journey seeds retain their historical numbering. The product should select a single approved sequence for future planning. |
FND-COM-ORD-031 | low | debt | The purchasing record leaves vendor, purchase-order and costing screens for later work, and the merchandise milestone remains proposed. This layer describes the API implementation without establishing a completed console purchasing experience. |
FND-COM-ORD-032 | medium | inconsistency | Some illustrative examples and three browser proposals refer to a console run branch unavailable at the pinned revision. Historical seed identifiers are retained, while unsupported example details point to this finding and carry unknown provenance. The browser scenarios remain unbound proposed work. |
FND-COM-ORD-033 | high | debt | Existing bindings leave specific clauses unproven: fixture settlement does not validate the live Accounting contract, rendered components do not establish browser handoffs, and helper checks do not prove their complete API callers. Mandatory rules with no scenario are named in affects. The complete transfer proposal also needs proof of uncovered quantities and absence of posting facts; its arithmetic test establishes rounding only. The product should close those rule-specific proof gaps before treating the layer as acceptance-ready. |
FND-COM-ORD-034 | low | undocumented | The supplied documentation revision lacks the requested authoring brief. Its intended exclusions cannot be independently examined. The module registry and this job’s instructions establish the scope used here. |
FND-COM-ORD-035 | medium | undocumented | Reading an accepted installment purchase can create a missing Accounting schedule, link its invoices and refresh the money mirror while authorized only for order reading. The product should review the permission boundary and retry behavior of this write-performing read before design approval. |
The five product questions remain open: installment handover, shipping and tax address selection, donation participation, purchasing ownership and cancellation of the original order fee. Their recommendations are product proposals and require Andrew’s decision.
OpenAI final-text pass
Each listed file has final prose and applicable readable row fields authored by Codex. Technical identifiers, exact source anchors, decision references and preserved historical seeds are intentionally retained. The concepts have six ordered sections and meet the requested length; capability explanations describe actors, progress and failure or recovery. Features group their children without introducing another rule home.
| Artifact | Final title or record | Inherited metadata corrections |
|---|---|---|
ATS-COM-ORD-001 | ATS-COM-ORD-001 | 0 |
ATS-COM-ORD-002 | ATS-COM-ORD-002 | 0 |
ATS-COM-ORD-003 | ATS-COM-ORD-003 | 0 |
ATS-COM-ORD-004 | ATS-COM-ORD-004 | 0 |
ATS-COM-ORD-005 | ATS-COM-ORD-005 | 0 |
ATS-COM-ORD-006 | ATS-COM-ORD-006 | 0 |
ATS-COM-ORD-007 | ATS-COM-ORD-007 | 2 |
ATS-COM-ORD-008 | ATS-COM-ORD-008 | 0 |
ATS-COM-ORD-009 | ATS-COM-ORD-009 | 0 |
ATS-COM-ORD-010 | ATS-COM-ORD-010 | 1 |
ATS-COM-ORD-011 | ATS-COM-ORD-011 | 0 |
ATS-COM-ORD-012 | ATS-COM-ORD-012 | 1 |
ATS-COM-ORD-013 | ATS-COM-ORD-013 | 0 |
ATS-COM-ORD-014 | ATS-COM-ORD-014 | 0 |
ATS-COM-ORD-015 | ATS-COM-ORD-015 | 0 |
ATS-COM-ORD-016 | ATS-COM-ORD-016 | 0 |
ATS-COM-ORD-017 | ATS-COM-ORD-017 | 1 |
ATS-COM-ORD-018 | ATS-COM-ORD-018 | 0 |
CAP-COM-ORD-001 | Build a buyer’s cart | 6 |
CAP-COM-ORD-002 | Select and preserve the sale’s checkout policy | 6 |
CAP-COM-ORD-003 | Review the price and resolve purchase blockers | 3 |
CAP-COM-ORD-004 | Use promotion codes before the sale | 3 |
CAP-COM-ORD-005 | Create one order at the reviewed price | 3 |
CAP-COM-ORD-006 | Invoice a sale through Accounting | 4 |
CAP-COM-ORD-007 | Collect payment without duplicate charges | 4 |
CAP-COM-ORD-008 | Clear an unaccepted order and return its resources | 4 |
CAP-COM-ORD-009 | Purchase with a deposit and scheduled payments | 1 |
CAP-COM-ORD-010 | Locate orders and understand their progress | 1 |
CAP-COM-ORD-011 | Protect orders and carts by workspace and authority | 3 |
CAP-COM-ORD-012 | Sell through the application that owns the purchase | 5 |
CAP-COM-ORD-013 | Provide purchased rights and account for their use | 1 |
CAP-COM-ORD-014 | Cancel accepted purchases and settle the result | 6 |
CAP-COM-ORD-015 | Amend purchases and settle their price difference | 7 |
CAP-COM-ORD-016 | Authorize returns and settle received goods | 6 |
CAP-COM-ORD-017 | Arrange vendor stock purchases | 2 |
CAP-COM-ORD-018 | Receive inventory and retain its cost | 5 |
CON-COM-ORD-001 | Checkout | 0 |
CON-COM-ORD-002 | Order | 2 |
CON-COM-ORD-003 | Selling Application | 0 |
CON-COM-ORD-004 | Entitlement | 0 |
CON-COM-ORD-005 | After-Sale Change | 0 |
CON-COM-ORD-006 | Purchase Order | 0 |
FEAT-COM-ORD-01 | Purchase preparation | 0 |
FEAT-COM-ORD-02 | Sale completion and payment | 0 |
FEAT-COM-ORD-03 | Order access and review | 0 |
FEAT-COM-ORD-04 | Application participation in sales | 0 |
FEAT-COM-ORD-05 | Purchased benefits | 0 |
FEAT-COM-ORD-06 | Purchase changes and returns | 0 |
FEAT-COM-ORD-07 | Vendor purchasing and stock value | 0 |
FINDINGS.md | FINDINGS.md | 20 |
ID_REGISTRY.md | ID_REGISTRY.md | 0 |
JNY-COM-ORD-001 | A phone purchase succeeds after a declined card | 0 |
JNY-COM-ORD-002 | An organization purchase is accepted on terms | 0 |
JNY-COM-ORD-003 | A manager locates a purchase and reviews its balance | 0 |
JNY-COM-ORD-004 | A void releases an unfinished purchase | 0 |
JNY-COM-ORD-005 | A partial cancellation refunds the affected purchase | 0 |
JNY-COM-ORD-006 | Vendor stock arrives through partial receipts | 0 |
MOD-COM-ORD | Customer purchases, purchased benefits and vendor stock | 0 |
ACTORS-COM | People and applications using Commerce; all six module-defined actor rows | Wording and role framing only |
MOD-COM-ORD registry entry | PRODUCT-AREAS module status | planning drafted → planning examined |
The final-wording audit finds no unchanged inherited sentence-length statement, scenario action, expectation, definition, purpose, note or actor description in the rewritten fields. Familiar nouns and exact technical values are retained where changing them would change their meaning. The examination report itself is authored by Codex.
Validation
The final acceptance commands are npm ci followed by npm run check, and npm test. Corpus conformance reports zero errors, and all four corpus-tool tests pass. The source-anchor audit resolves every source and bound-test reference at the pinned revisions with zero unresolved references; this anchor check supplements, rather than replaces, semantic inspection of the claims. No service test execution, new browser run or live Accounting settlement is claimed.
Verdict for Andrew
The layer is a faithful, sourced description of the registered module at the pinned commits when its explicit unknown examples, proposed scenarios and open findings are read with the implemented behavior. Its weakest evidence is the complete browser and real Accounting handoff, together with mandatory rule clauses still covered only by a finding. Before design begins, Andrew should resolve the five product questions and the schedule-read permission decision, and the team should bind the missing route and settlement proofs at the required level.