Back to Signal Feed
CodeTracked since May 19, 2026

Fix resume instructions to load Per-Unit Design artifacts from the correct unit directory

The PR corrects `session-continuity.md` so Per-Unit Design resume guidance matches actual Construction output, specifying `aidlc-docs/construction/{unit-name}/{functional-design,nfr-requirements,nfr-design,infrastructure-design}/`, requiring in-progress unit selection from `aidlc-state.md`, and removing outdated hardcoded filenames.

awslabs/aidlc-workflowssession-continuity.mdaidlc-docs/construction/{unit-name}/...aidlc-state.md

What Happened

  • The PR corrects `session-continuity.md` so Per-Unit Design resume guidance matches actual Construction output, specifying `aidlc-docs/construction/{unit-name}/{functional-design,nfr-requirements,nfr-design,infrastructure-design}/`, requiring in-progress unit selection from `aidlc-state.md`, and removing outdated hardcoded filenames.
  • The PR corrects `session-continuity.md` so Per-Unit Design resume guidance matches actual Construction output, specifying `aidlc-docs/construction/{unit-name}/{functional-design,nfr-requirements,nfr-design,infrastructure-design}/`, requiring in-progress unit selection from `aidlc-state.md`, and removing outdated hardcoded filenames.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Aligned the Per-Unit Design session-continuity guidance with actual artifact layout and dependency rules, changing resume behavior from an inaccurate fixed file list to unit-aware paths and explicit unit selection.

Why Track This

Why It Matters

Operators resuming multi-unit Construction sessions can now follow the correct artifact path for the active unit, so they are less likely to hit broken resume steps from missing files and can continue context restoration with fewer manual corrections. The change addresses a direct correctness issue in continuity guidance that was shown in a 6-unit resume run; next, teams should watch for future Construction output-path or naming changes that could reintroduce mismatch between docs and stage artifacts.

Impact

Operators resuming multi-unit Construction sessions can now follow the correct artifact path for the active unit, so they are less likely to hit broken resume steps from missing files and can continue context restoration with fewer manual corrections. The change addresses a direct correctness issue in continuity guidance that was shown in a 6-unit resume run; next, teams should watch for future Construction output-path or naming changes that could reintroduce mismatch between docs and stage artifacts.

What To Watch Next

  • Watch whether awslabs/aidlc-workflows becomes a repeated pattern.
  • Track follow-up changes around Code Repository Intelligence.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: artifact_path_schema_drift_after_pipeline_updates, missing_unit_selection_in_other_resume_guides.
Open Topic TimelineOpen Technical EventOpen Original Sourceartifact_path_schema_drift_after_pipeline_updates / missing_unit_selection_in_other_resume_guides / manual_dependency_overrides_masking_documentation_mismatch

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

awslabs/aidlc-workflows PR #276: fix: scope per-unit artifact loading to unit directories in session-continuity

A resumed, zero-context multi-unit session previously had no clear way to know which unit’s artifacts to load, and the documented filenames did not exist at the listed paths.