Derive context

Orient

Why this stage matters

The issue describes a balance symptom. Before proposing a change, engineers must establish where the request travels, where data changes and what the current tests observe.

Inputs

Use repository sources and accepted artifacts

Worked example

Trace the amount field from the form to persistence

1. Find where the React form collects the amount and creates the request object.
2. Follow the request into OperationDTO and the mapper.
3. Read createOperation and identify the only repository write.

The worked example stops after this one field. You trace the remaining behavior.

Decide

Separate repository facts from product decisions

• Which files determine operation creation and balance behavior?
• Which files provide useful background but do not affect this change?
• Which statements are observed facts, and which are assumptions?
• What product rules cannot be derived from the repository?

Use the agent

Use the agent on this repository

These are task patterns for the pinned JHipster source, not answer scripts. Replace every bracketed field with accepted repository work. Open every cited path at the pinned revision and review each response before continuing. If you cannot supply a field, return to the earlier artifact.

Decide before prompting

• Paste the issue exactly as written. Do not add a solution.
• Choose one request entry point to trace first.
• Create context-brief.md for accepted findings.

Read this issue:
[paste the issue]

Trace operation creation from the React form through the API to persistence. Use repository sources only. Cite each file and symbol. Separate observed facts from inferences. Do not propose changes.

Using the verified request trace, find where BankAccount balance is read or changed. Identify transaction boundaries and ownership checks on the create path. Cite each file and symbol. Report missing behavior as a finding, not as a requirement.

Search for every path that can create, update or delete an Operation or directly change BankAccount balance. For each path, cite the entry point and persistence call. State whether existing tests observe the balance effect. Do not infer product policy.

Draft context-brief.md from the findings I accepted. Include the current request path, related state, transaction boundary, ownership checks, mutation paths, relevant tests and repository constraints. Preserve file and symbol citations. End with exclusions, inferences and questions the repository cannot answer.

Audit context-brief.md against the repository. List unsupported statements, missing sources, irrelevant sources and facts stated as inferences or inferences stated as facts. Do not rewrite the brief. Return findings with exact citations.

Create

Produce the context brief for this repository

1. Trace the selected account from the form to the stored relationship.
2. Locate the transaction boundary and both repositories.
3. Inspect update, partial-update and delete paths for operations and bank accounts.
4. Read the existing Java, React and Cypress tests. Record what each test observes.
5. Write the context brief and link every material fact to a source.

Challenge

Try to disprove the repository-backed work

Revise

Use repository evidence before continuing

Transfer

Apply the practice to your work

• Name the equivalent request entry point, persistence boundary and tests in one service you maintain.
• Identify one generated or framework area you would exclude from the first context pass.

Record your answer. The lab is complete only when you can name the equivalent practice, artifact and evidence in your work.