change, continuity, and responsibility boundaries
Why change requests are separate from initial delivery, what continuity covers, and how desks own disruption without amnesia.
- managed network
- no fabricated news
delivery boundary
Initial delivery closes with evidence and QA acceptance. Scope expansion or behavior change uses a separate change path with reason and impact.
This separation prevents contractual ambiguity and preserves an auditable history — silent edits via task fields are not a product path.
desks that own the messy middle
change desk
Formal request, reason, impact, approval — then new evidence versions
escalation
Raise issues with record — no automatic punishment or reputation penalties
continuity desk
Replacement and handoff when disruption hits — logged, not improvised
what continuity means
Continuity covers confirmed defect fixes, handoff documentation, and agreed limited maintenance — not unlimited post-acceptance development disguised as “support.”
When a member leaves, knowledge rides on evidence history and scoped access, not private side channels that vanish with a contractor.
boundaries worth defending
you get
- Logged replacement with evidence handoff
- Scoped maintenance with explicit agreement
- Change with impact assessment
you do not get
- Abandoning projects when a single contractor disappears
- Open-ended rewrites under a maintenance label
- Silent scope creep through informal chat
Continue with quality, developers, organizations.