EVIDENCE CASE
Moving project details to runtime ISR through a bounded engineering workflow
A real Portfolio 2025 performance gate used the complete Engineering Workflow pack to plan, slice, review, verify, and hand off a server-owned runtime ISR transition without widening scope to legitimately dynamic routes.
01
Problem
Move PT and EN project details from client-owned request-time loading to server-owned runtime ISR while preserving URLs, localization, editorial UI, metadata semantics, cache safety, and intentionally dynamic public routes.
02
Methods applied
- 01Planning Engineering WorkMakes the next engineering step explicit while preserving constraints, risks, dependencies, assumptions, and the evidence required for completion.
- 02Managing Implementation SlicesReduces scope creep and integration risk while preserving a clear dependency chain between implementation slices.
- 03Reviewing Pull RequestsProduces prioritized, actionable review findings without confusing stylistic preference with correctness or treating CI status as an assumption.
- 04Writing Effective Technical HandoffsPreserves continuity across people, agents, and sessions without forcing the next worker to reconstruct the project from chat history or guesses.
Decision record
- 01
Plan behavior and verification before implementation
Define RED contracts, server ownership, ISR, cache invalidation, route assertions, QA, and explicit non-goals before changing production code.
- 02
Keep the performance initiative in dependent slices
Treat project-detail ownership as Gate C after locale-root work, and keep unrelated font delivery, upgrades, migrations, and legitimately dynamic routes outside the slice.
- 03
Review risk instead of polishing the diff
Review ownership, localization, metadata/JSON-LD reuse, mutation invalidation, route classification, current CI, and scope boundaries before accepting the candidate.
- 04
Hand off an exact restart point
Preserve candidate SHA, run IDs, route rulings, QA, constraints, and the explicit no-merge-without-authorization next action in the final PR description.
03
Verification
Treat this report as evidence for the methods and verification shown here. Related-pack overlap alone is not proof that a pack was used or fully validated.
04
Result
- 01
The project-detail PT/EN route patterns moved from request-time dynamic rendering to runtime ISR while preserving the editorial interface.
- 02
The final candidate passed static-rendering, performance, SEO, validation, integrations, typecheck, lint, production build, route assertion, and localhost QA.
- 03
The subsequent main merge passed the canonical Validate workflow.
- 04
All four Engineering Workflow methods contributed to planning, slice boundaries, review, or technical handoff.