# Decide what can be shared

Compare two actual requests only with permission from their owners. Keep private records and local rules in their approved systems. This worksheet records a reuse decision; it does not authorize moving data, code, policy, or customer-funded work.

## Completed hypothetical comparison

No component has been implemented or tested. No delivery or support saving has been measured.

| Question                                   | Paper-case answer                                                                                                                                                                                                     |
| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Who needs the component?                   | Two purchasing teams in one company: North and South                                                                                                                                                                  |
| North's job                                | Prepare routine requests using approved supplier and cost-center records; buyer accepts the request; closed cost center stays held                                                                                    |
| South's job                                | Prepare supplier exceptions using contract and exception-policy sources; legal decides nonstandard clauses; restricted details stay limited                                                                           |
| Proposed common behavior                   | Display permitted evidence and revisions; retain proposed edits and correction history; identify who handles blocked work                                                                                             |
| What stays local?                          | Sources, access enforcement, policy decisions, acceptance rules, business actions, support assignments, and private case records                                                                                      |
| Candidate version                          | review-card@0.1-candidate; proposed only                                                                                                                                                                              |
| Differences to preserve                    | North's buyer and cost-center path; South's legal and contract path; neither component may place orders or change contracts                                                                                           |
| Why investigate reuse?                     | Two hypothetical requests suggest a question to investigate. They do not establish demand or an advantage from a reusable product.                                                                                    |
| Rights and confidentiality                 | Reuse permission unresolved; do not copy real records or policy text into a shared repository                                                                                                                         |
| Ownership                                  | Shared maintainer and reserved support time unassigned; local workflow ownership stays with each team                                                                                                                 |
| Cost comparison                            | Local versus shared setup, testing, migration, maintenance, and support costs unknown                                                                                                                                 |
| Inputs, outputs, versions, and stopping it | Agree which facts each team supplies and how edits or blocked cases return to its application. Review exact versions; plan to disable or replace the component while preserving cases and an approved review process. |
| Required local tests                       | North closed cost center; South legal clause; restricted source; correction; interruption and resume with current evidence/history                                                                                    |
| Current decision                           | Investigate. Keep existing review paths; no shared release approved                                                                                                                                                   |

If the work came from a customer engagement, also inspect ownership, license, contract, confidentiality, and publication terms with the appropriate reviewer. Removing customer names is not sufficient reuse clearance.

## Your two requests

| Question                                                                                                      | Your record                                                                                 |
| ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| Which teams, decisions, and accepted results are being compared?                                              | —                                                                                           |
| What evidence shows the same job recurs? Include counterexamples and the period.                              | —                                                                                           |
| What is the smallest proposed common behavior?                                                                | —                                                                                           |
| Which differences are required by policy, user roles, source systems, or operating conditions?                | —                                                                                           |
| Which differences may be accidental workarounds worth repairing instead?                                      | —                                                                                           |
| What data, rules, source connectors, permissions, and decisions must stay local?                              | —                                                                                           |
| What code or evidence may be moved, and who can authorize that?                                               | —                                                                                           |
| What ownership, contract, license, confidentiality, or publication questions remain?                          | —                                                                                           |
| Who maintains the shared version, with what reserved time and support route?                                  | —                                                                                           |
| Who owns each local workflow and its users?                                                                   | —                                                                                           |
| Over the same period, what do separate local versions cost?                                                   | —                                                                                           |
| What would extraction, adaptation, testing, migration, support, maintenance, and retirement cost?             | —                                                                                           |
| Which exact version would each team use? What information must it supply, and what does the component return? | —                                                                                           |
| What tests can reject the candidate in each team's workflow?                                                  | —                                                                                           |
| How will restricted data stay out of the component, model, errors, and exports?                               | —                                                                                           |
| How will you disable, replace, or revert the component while preserving pending work?                         | —                                                                                           |
| What future evidence would establish less effort or lower full cost without worse outcomes?                   | —                                                                                           |
| Next action, owner, review date, and evidence location                                                        | —                                                                                           |
| Decision                                                                                                      | Investigate / keep local / use existing feature / propose shared component / defer / reject |

Sharing code does not let North approve South's work or choose which contract South must follow. Each team still needs its own data, security, testing, release, adoption, support, and ownership checks. Record the exact version actually used and the local work it still required before claiming a benefit from reuse.