--- id: FAS-COM-ORD-04 title: Application participation in sales feature: FEAT-COM-ORD-04 product_area: commerce module: orders revision: 1 status: proposed product_intent: proposed source_sha: services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-COM-ORD-012 scenarios: - id: FAS-COM-ORD-04-01 title: A registered application supplies the purchased details kind: behaviour exercises: - CAP-COM-ORD-012 - CAP-COM-ORD-003 - CAP-COM-ORD-005 relies_on: - ATS-COM-ORD-012-01 - ATS-COM-ORD-003-01 - ATS-COM-ORD-005-10 preconditions: A registered application owns the fixture item type. steps: - do: Preview and place its item after valid registration. provenance: proposed source: - ATS-COM-ORD-012-01 - ATS-COM-ORD-003-01 - ATS-COM-ORD-005-10 expected: The sale freezes the owner’s prepared details and delivery plan. negative: false data_needs: 'An isolated workspace with the records, permissions and controlled outcomes named above.' bound_to: [] provenance: proposed source: - ATS-COM-ORD-012-01 - ATS-COM-ORD-003-01 - ATS-COM-ORD-005-10 expected_provenance: proposed expected_source: - ATS-COM-ORD-012-01 - ATS-COM-ORD-003-01 - ATS-COM-ORD-005-10 - id: FAS-COM-ORD-04-02 title: Prepared details define the later grant kind: interaction exercises: - CAP-COM-ORD-012 - CAP-COM-ORD-013 relies_on: - ATS-COM-ORD-012-07 - ATS-COM-ORD-013-01 preconditions: An application-owned item prepares a finite entitlement specification. steps: - do: 'Place, change the live configuration and dispatch the frozen grant.' provenance: proposed source: - ATS-COM-ORD-012-07 - ATS-COM-ORD-013-01 expected: The right uses the prepared allowance rather than the new configuration. negative: false data_needs: 'An isolated workspace with the records, permissions and controlled outcomes named above.' bound_to: [] provenance: proposed source: - ATS-COM-ORD-012-07 - ATS-COM-ORD-013-01 expected_provenance: proposed expected_source: - ATS-COM-ORD-012-07 - ATS-COM-ORD-013-01 - id: FAS-COM-ORD-04-03 title: Retiring a type stops new sales while preserving history kind: lifecycle exercises: - CAP-COM-ORD-012 - CAP-COM-ORD-005 relies_on: - ATS-COM-ORD-012-01 - ATS-COM-ORD-005-10 preconditions: A sold type is omitted on the owner’s next registration. steps: - do: 'Read the earlier purchase, attempt another cart item and redeclare the type.' provenance: proposed source: - ATS-COM-ORD-012-01 - ATS-COM-ORD-005-10 expected: The earlier purchase stays intact and new availability follows the registry state. negative: false data_needs: 'An isolated workspace with the records, permissions and controlled outcomes named above.' bound_to: [] provenance: proposed source: - ATS-COM-ORD-012-01 - ATS-COM-ORD-005-10 expected_provenance: proposed expected_source: - ATS-COM-ORD-012-01 - ATS-COM-ORD-005-10 - id: FAS-COM-ORD-04-04 title: Registration is the registry write boundary kind: permission exercises: - CAP-COM-ORD-012 - CAP-COM-ORD-011 relies_on: - ATS-COM-ORD-011-02 - ATS-COM-ORD-012-09 preconditions: The ordinary application role can read the registry. steps: - do: Try direct registry writes and then use authorized registration. provenance: proposed source: - ATS-COM-ORD-012-09 - ATS-COM-ORD-011-02 expected: Direct writes fail and the authorized declaration is reconciled. negative: true data_needs: 'An isolated workspace with the records, permissions and controlled outcomes named above.' bound_to: [] provenance: proposed source: - ATS-COM-ORD-012-09 - ATS-COM-ORD-011-02 expected_provenance: proposed expected_source: - ATS-COM-ORD-012-09 - ATS-COM-ORD-011-02 - id: FAS-COM-ORD-04-05 title: Unavailable application advice leaves no partial sale kind: regression exercises: - CAP-COM-ORD-012 - CAP-COM-ORD-003 - CAP-COM-ORD-005 relies_on: - ATS-COM-ORD-012-04 - ATS-COM-ORD-003-03 - ATS-COM-ORD-005-05 preconditions: The owning application stops answering. steps: - do: 'Preview and place, restore its response and preview the same cart.' provenance: proposed source: - >- services-commerce:modules/checkout/tests/e2e/participant-unavailable.e2e.spec.js#previews the same checkout once the participant answers again expected: No failed sale remains and review resumes on the original cart. negative: true data_needs: 'An isolated workspace with the records, permissions and controlled outcomes named above.' bound_to: [] provenance: proposed source: - >- services-commerce:modules/checkout/tests/e2e/participant-unavailable.e2e.spec.js#previews the same checkout once the participant answers again expected_provenance: proposed expected_source: - >- services-commerce:modules/checkout/tests/e2e/participant-unavailable.e2e.spec.js#previews the same checkout once the participant answers again candidate_bindings: - TST-COM-ORD-034 binding_gap: FND-COM-ORD-079 evidence: - provenance: documented source: 'rhythm-v2-docs:specs/commerce/orders/planning/features/FEAT-COM-ORD-04-selling-applications.md' - provenance: observed source: - >- rhythm-v2-docs:specs/commerce/orders/planning/capabilities/CAP-COM-ORD-012-let-selling-applications-declare-prepare-and-deliver-what-an.md --- # Application participation in sales: Feature Acceptance Suite ## What the Feature Must Do as a Whole Selling applications provide the declarations and prepared details that Commerce uses to place and deliver a purchase. The suite follows those handoffs and asks whether registration, retirement or unavailability leaves the purchase in an understandable state. ## Interactions Between Capabilities Registry declarations govern preparation, and prepared details supply later delivery inputs. The outage case separately asserts refusal and resumed preview, but its test does not count order rows. Full absence of a partial sale remains proposed. ## Regression Record | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish the feature’s combined outcomes from the pinned specification and executable evidence. |