Repair

Operator Inputs

• Name the exact damaged surface, broken state, or degraded panel that needs restoration.
• Define what usable again means in observable terms.
• State what must stay unchanged while the repair is made.
• Flag any evidence that the damage may be symptomatic of something larger.

Procedure

1. Restate the target, success condition, and no-touch boundaries before you spend the chip.
2. Collect the operator inputs below so the chip lands on the right panel.
3. Identify the damaged surface that needs restoration.
4. Repair it directly with the least ceremony possible.
5. Confirm the panel is truly usable again.
6. Stop for explicit confirmation before taking a live action that changes real state outside the current conversation.
7. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

• A restoration patch or environment fix.
• A verification note proving the surface is stable.

Output Contract

• A direct restoration move focused on returning the damaged surface to working order.
• A patch narrow enough to avoid unrelated upgrades or cleanup sprawl.
• A verification step proving the surface is stable again.
• A plain note if the damage appears symptomatic rather than isolated.

Do Not Use For

• Feature work disguised as maintenance.
• Speculative redesigns when a plain fix would restore service.
• Cases where the real need is temporary shielding or recovery, not infrastructure restoration.

Pair With

• Repair + Sanctuary: create a safer zone first, then restore the broken ground inside it.
• Repair + Barrier: patch the damaged surface while a small buffer absorbs the next hit.
• Repair + Recovery: restore the field, then stabilize the operator or dependent workflow.

Pitfalls / Guardrails

• Treat the live action surface as real operational work, not just battle-chip flavor text.
• Repair should restore service, not smuggle in unrelated upgrades.
• If the damage is symptomatic of a larger structural issue, say so.
• Keep the chip metaphor anchored to a real operating move; do not let flavor substitute for procedure.

Verification

• Check that the response includes every promised deliverable and leaves an inspectable audit trail.
• Check that confirmed facts, assumptions, and proposed follow-up are visibly separated.
• Confirm the response names the damaged surface precisely instead of hand-waving at the system.
• Confirm the repair restores intended function without broadening scope into enhancement work.
• Confirm there is an observable test proving the panel is usable again.
• Check that the exact live target, confirmation gate, and rollback or recovery path are explicit.

Example Invocation

Use Repair to restore this broken workflow step directly and prove it is usable again before suggesting improvements.
Use Repair on the damaged environment surface here; keep it narrow and honest about root cause.