---
phase: 165-real-topic-l0-to-l2-e2e-validation
plan: 01
type: execute
wave: 1
depends_on:
  - v1.90-closure
files_modified:
  - .planning/phases/165-real-topic-l0-to-l2-e2e-validation/165-E2E-RUNBOOK.md
  - .planning/phases/165-real-topic-l0-to-l2-e2e-validation/165-ISSUE-CAPTURE-PROTOCOL.md
  - .planning/phases/165-real-topic-l0-to-l2-e2e-validation/165-ISSUE-LEDGER.md
  - .planning/phases/165-real-topic-l0-to-l2-e2e-validation/evidence/<topic-slug>/POSTMORTEM.md
  - .planning/phases/165-real-topic-l0-to-l2-e2e-validation/evidence/<topic-slug>/COMMANDS.md
autonomous: false
requirements:
  - REQ-E2E-01
  - REQ-E2E-02
  - REQ-E2E-03
  - REQ-E2E-04
must_haves:
  truths:
    - use the current public AITP entry surfaces first instead of seeding hidden artifacts
    - treat the run as research-utility validation, not just another narrow acceptance script
    - do not assume GSD will auto-discover issues from runtime artifacts alone
---

<objective>
Run one real topic from an initial idea through the current AITP user-facing
flow, collect durable evidence about where the protocol helped or hurt, and
turn every discovered issue into explicit GSD-tracked work.
</objective>

<tasks>

<task type="auto">
  <name>Task 1: Execute one primary real-topic E2E route from an initial idea</name>
  <files>.planning/phases/165-real-topic-l0-to-l2-e2e-validation/165-E2E-RUNBOOK.md, .planning/phases/165-real-topic-l0-to-l2-e2e-validation/evidence/&lt;topic-slug&gt;/COMMANDS.md</files>
  <read_first>research/knowledge-hub/README.md</read_first>
  <action>Choose one real topic, run it through `explore` and/or `bootstrap`, then continue with `loop`, `status`, `replay-topic`, and the relevant audit surfaces until the topic reaches one honest bounded outcome.</action>
  <verify>Record the exact command sequence and the key produced artifact paths.</verify>
  <acceptance_criteria>
    - the run starts from a real idea rather than a synthetic seeded fixture
    - the run uses current public AITP entry surfaces
    - the run reaches one explicit bounded outcome (`L2`, `promotion-ready`, blocked, or deferred)
  </acceptance_criteria>
  <done>One primary real-topic command/evidence trail exists.</done>
</task>

<task type="auto">
  <name>Task 2: Write the postmortem and issue ledger</name>
  <files>.planning/phases/165-real-topic-l0-to-l2-e2e-validation/evidence/&lt;topic-slug&gt;/POSTMORTEM.md, .planning/phases/165-real-topic-l0-to-l2-e2e-validation/165-ISSUE-CAPTURE-PROTOCOL.md, .planning/phases/165-real-topic-l0-to-l2-e2e-validation/165-ISSUE-LEDGER.md</files>
  <read_first>.planning/phases/165-real-topic-l0-to-l2-e2e-validation/165-ISSUE-CAPTURE-PROTOCOL.md</read_first>
  <action>Write one durable postmortem naming what helped, what created friction, what route the topic actually took, and what concrete issues were discovered.</action>
  <verify>Every issue in the postmortem appears in the issue ledger with a severity, artifact reference, and proposed GSD routing.</verify>
  <acceptance_criteria>
    - the postmortem names exact artifact refs and outcome state
    - the issue ledger distinguishes urgent follow-up from backlog-worthy follow-up
    - no discovered issue is left only in chat memory
  </acceptance_criteria>
  <done>The real-topic run is now actionable for follow-up engineering work.</done>
</task>

<task type="auto">
  <name>Task 3: Promote discovered problems into explicit GSD work</name>
  <files>.planning/BACKLOG.md, .planning/ROADMAP.md</files>
  <read_first>.planning/phases/165-real-topic-l0-to-l2-e2e-validation/165-ISSUE-LEDGER.md</read_first>
  <action>For each issue in the ledger, either create an urgent decimal follow-up phase or add/promote a backlog item. Do not assume GSD will discover the problem from runtime artifacts automatically.</action>
  <verify>Every issue ledger row records one concrete GSD destination: current milestone decimal phase, next milestone candidate, or backlog item.</verify>
  <acceptance_criteria>
    - urgent blockers become explicit GSD execution work
    - non-urgent issues become backlog or next-milestone candidates
    - the phase ends with a visible follow-up map instead of an informal conclusion
  </acceptance_criteria>
  <done>The E2E run has been turned into schedulable GSD follow-up work.</done>
</task>

</tasks>
