Skip to content

fix: clarify COMPLETED vs approved status on session resumption#255

Open
Abhishek8108 wants to merge 1 commit into
awslabs:mainfrom
Abhishek8108:fix/distinguish-generated-from-approved-status
Open

fix: clarify COMPLETED vs approved status on session resumption#255
Abhishek8108 wants to merge 1 commit into
awslabs:mainfrom
Abhishek8108:fix/distinguish-generated-from-approved-status

Conversation

@Abhishek8108
Copy link
Copy Markdown

@Abhishek8108 Abhishek8108 commented May 9, 2026

Fixes #249

Problem

When a session clears mid-workflow and a new instance resumes by reading aidlc-state.md, it has no way to distinguish between:

  • A stage that was generated (artifact exists, user has not yet approved)
  • A stage that was fully approved (artifact reviewed and signed off)

Both appear as COMPLETED in the state file, so the resumed session proceeds past approval gates without user confirmation — potentially generating later-stage artifacts before earlier ones have been reviewed.

Fix

Adds an Approval Gate Status Interpretation section to session-continuity.md with an explicit lookup table:

State entry Interpretation Action
[x] Stage Name (Approved) Generated AND approved Proceed
[x] Stage Name (no annotation) Generated, approval unknown Halt — present artifact, request confirmation
[ ] Stage Name Not started Begin

The rule is simple: (Approved) annotation = safe to proceed; absent annotation = halt and re-present to the user before continuing. An audit trail cross-check via audit.md is also specified as a tiebreaker when the state file is ambiguous.

Scope

Single file change in session-continuity.md — the file already referenced in core-workflow.md as the mandatory guide for resumption. No other files touched.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

A fresh session reading aidlc-state.md could not distinguish between
'artifact generated' and 'user approved' when a stage shows COMPLETED,
causing it to skip approval gates on resumption (issue awslabs#249).

Add an explicit approval gate status table to session-continuity.md:
- [x] Stage (Approved)  → generated AND approved → proceed
- [x] Stage (no tag)    → generated only → halt and re-present artifact

The new rules require the resuming session to halt at any stage marked
COMPLETED without an (Approved) annotation, load the artifact, and
request explicit user confirmation before continuing. An audit trail
cross-check against audit.md is also specified as a tiebreaker.

Fixes awslabs#249
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Session resumption after context clear can skip approval gates by misreading COMPLETED status

1 participant