Principles Library / Original Intent

Original Intent

Understand the Original Intent Before Removing or Replacing Existing Capabilities

Principle intent

Before removing or replacing existing capabilities, understand why they were introduced and what risks they were designed to manage.

Read the full intent

Many systems encode historical learning that is no longer obvious but still relevant.

When it holds: what it does for you

Solved problems stay solved

Safeguards nobody remembered keep doing their job after the change.

Simpler, not more fragile

You can modernize a system without trading away the protections that matter.

Agent changes stay traceable

When an agent rewrites logic, you still know what went and why.

When it is ignored: from early signs to a lasting condition

Early warning signs · Visible now, cheap to fix

What happens over time · Accumulates, costly to reverse

The condition it becomes

Quality Fragility · Primary

Customers find defects before the team does.

How this principle feeds it

recurring solved failures are defects found late, after they are expensive to fix.

Governance Drag · Secondary

Work is done. Approvals are not.

How this principle feeds it

fear of regressions adds change-control layers that slow work more than they cut risk.

Attribution Failure · Primary

We know what happened. Nobody can explain why.

How this principle feeds it

outcomes are recorded but the decision that caused them is not.

Implementation Drift · Primary

The agents are building. Nobody is sure it still matches the plan.

How this principle feeds it

each unacknowledged substitution becomes the new baseline while outputs look locally correct.

Where is your system on this path?

Diagnose

Diagnose

AI signs are on by default. Use the AI switch to exclude them.

1. Which of these early warning signs are you seeing?

  • Capabilities get removed because they look outdated, unused or hard to understand.
  • A simplification or refactor causes a regression nobody expected.
  • Teams are surprised by failures that had already been mitigated.
  • Changes to existing capabilities are judged on elegance or speed, with no risk analysis.
  • Experienced people leave, and the reasons behind key capabilities leave with them.
  • AI refactoring strips out logic that guarded against a failure nobody remembers. (AI)
  • Old problems come back after an agent-driven modernization. (AI)
  • Agents can change or replace capabilities with no step to capture intent first. (AI)
  • Agents change things faster than anyone can record what was removed and why. (AI)

2. Over the last few months, have you noticed…

For each consequence: Not seen / Sometimes / Persistently / Not sure.

  • Problems you'd already solved come back under new names.
  • Operational, compliance or safety risk rises where nobody expected it.
  • Systems look simpler but break more easily.
  • Confidence in change drops, so teams avoid removing anything or add approval gates.
  • After agent-driven replacement, nobody can trace regressions back to their cause. (AI)
  • Agent rewrites become the baseline, and later work builds on lost safeguards. (AI)

3. The condition it becomes

Based on your answers, recognize at most two conditions: No / Partly / Yes, that is us.

Quality Fragility: Customers find defects before the team does.

Governance Drag: Work is done. Approvals are not.

Attribution Failure: We know what happened. Nobody can explain why.

Implementation Drift: The agents are building. Nobody is sure it still matches the plan.

Take your Diagnosis to the next level by invoking AI Diagnostic Coaching tool.

What else have you observed? Optional. Shared only if you choose to start coaching.

Start a Diagnosis session: review and edit a draft containing your note, conditions you recognized in Step 3 (including whether they match partly), warning signs and consequence ratings before sending it. No scores or principle files are sent.

See what practices will help you

Act

Act

Showing all 5 practices. Answer the Diagnose questions and the most relevant come first.

Find out and record why it exists

Before anything is removed, find out why the capability was introduced and what risk it manages. Write that down.

Start by asking your team: What problem was this capability originally solving?

Avoid · You’ll know it’s working when

Avoid

  • Assuming old automatically means bad
  • Treating existing capabilities as accidental rather than intentional

You’ll know it’s working when

Capabilities are removed for known reasons, and the history stays on record when experienced people leave.

Check the incident history first

Review past incidents, outages and failures tied to the capability before deciding to remove or replace it.

Start by asking your team: What failure or risk did it protect against?

Avoid · You’ll know it’s working when

Avoid

  • Removing controls without reviewing incident history

You’ll know it’s working when

Teams know which failures a capability prevents before they touch it, so old failures don't catch them out.

Remove it in small, guarded steps

Remove or replace capabilities a piece at a time, with safeguards in place at each step.

Start by asking your team: What evidence tells us it is now safe to remove or replace?

Avoid · You’ll know it’s working when

Avoid

    You’ll know it’s working when

    Simplifications land without surprise regressions, and any regression traces back to one small change.

    Keep critical protections when you modernize

    When you modernize an implementation, carry its critical protections into the new version.

    Start by asking your team: What assumptions have changed since it was introduced?

    Avoid · You’ll know it’s working when

    Avoid

    • Prioritizing elegance over durability

    You’ll know it’s working when

    New implementations keep the protections that matter, and nobody trades them away for elegance or speed.

    Capture intent before agents remove anything

    Before an agent removes or rewrites a capability, require someone to capture its original intent explicitly.

    Start by asking your team: As automation speeds up change, how are historical safeguards preserved?

    Avoid · You’ll know it’s working when

    Avoid

    • Allowing AI-driven refactoring or replacement without intent analysis

    You’ll know it’s working when

    No agent removes or rewrites a capability until its intent is on record, and that record keeps pace with the change.