# Canyon Response Logistics proposal sprint — evidence-and-artifact workbook

**Case packet version:** 2026.08.31-practice-3

**Case brief record:** CB01

This is a fictional, sanitized training case. Solicitation identifiers, agencies, companies, people, pricing, and performance records are invented and are not legal, contracting, pricing, or government representations advice.

## How to use this workbook

Complete only what the fictional packet supports. Cite the module input ID beside each material statement. Write **not supplied** for missing operational records, approvals, dates, test results, or identities. Label anything you design as a **learner proposal**. Do not contact people, access systems, run tests, sign records, or present a proposed control as an observed fact. Each module contains a prerequisite gate, six-to-eight task-specific operating steps, field-by-field guidance, schema-exact supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, a completion test, blank artifact tables, and mapped criteria. Row counts are contractual: if an assignment calls for 47 requirements, 20 records, 40 evaluations, or 27 tasks, the corresponding table contains that many stable rows.

## Module 1 — Qualify before bidding

**Task mode:** bounded-case-starter

**Prompt:** Evaluate strategic fit, delivery feasibility, authority, evidence, schedule, and bid cost before committing the team.

**Deliverable:** A bid/no-bid brief with assumptions, disqualifiers, owners, and a decision gate.

### Supplied-input register

| Input ID | Kind | Source record(s) | What the packet supplies | Where I used it |
|---|---|---|---|---|
| M01-I01 | case-fact | F01 | The official submission deadline is September 18 at 2:00 p.m. Eastern. | |
| M01-I02 | case-fact | F03 | Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment. | |
| M01-I03 | case-fact | F06 | A proposed subcontract warehouse supplied only an unsigned availability email. | |
| M01-I04 | case-fact | F07 | Finance totals $486,200 and the required price form totals $468,200. | |
| M01-I05 | case-fact | F10 | The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics. | |
| M01-I06 | case-fact | F11 | The coordinator lacks authority to sign the offer or certify representations. | |
| M01-I07 | case-fact | F12 | The current upload folder is 31 megabytes and includes internal working notes. | |
| M01-B01 | case-brief | CB01 | Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment. | |
| M01-S01 | assignment-scope | F01, F03, F06, F07, F10, F11, F12 | Build a starter version of “A bid/no-bid brief with assumptions, disqualifiers, owners, and a decision gate.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it. | |

### Completion boundary

Complete a bounded starter and gap analysis using only CB01, F01, F03, F06, F07, F10, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

### Prerequisite check

- [ ] Confirm official deadline, amendment, warehouse evidence, price conflict, page overage, signature boundary, and upload-folder condition.
- [ ] Treat the current solicitation and amendment as controlling; internal calendars and drafts are secondary records.
- [ ] Identify bid, price, representation, and submission decision owners by role only.

### Operating procedure

1. State the bid decision and cite the controlling deadline and amendment before considering internal schedule assumptions.
2. List evidence supporting pursuit separately from disqualifiers, unresolved dependencies, and authority limits.
3. Treat the unsigned warehouse email and 14-day delivery as dependencies requiring evidence rather than confirmed capability.
4. Record the price conflict, page overage, signature boundary, and upload-folder exposure as decision risks.
5. Compare proceed, proceed conditionally, pause, and no-bid choices with explicit tradeoffs and closure evidence.
6. Route bid authorization, price approval, representations, and final submission to their authorized owners.
7. Quality-check source priority, deadline expression, amendment status, authority, and absence of invented approvals.

### Field-by-field guidance — M01-A01

| Field | What high-quality completion requires |
|---|---|
| Decision | State the bounded bid/no-bid or conditional-pursuit decision under review. |
| Evidence for | List only supplied facts supporting continued pursuit and cite their inputs. |
| Evidence against | List disqualifiers, conflicts, gaps, and authority limits without resolving them by assumption. |
| Options and tradeoffs | Compare no-bid, pause, conditional proceed, and proceed only after defined closure evidence. |
| Decision owner | Use Authorized proposal lead or contracting reviewer; no named owner is supplied. |
| Required approval | Identify bid, price, representation, signature, and submission approvals still required. |
| Status | Use Draft decision, Blocked, Conditional, or Authorized disposition pending. |

### Completed supported example — M01-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Decision | Evidence for | Evidence against | Options and tradeoffs | Decision owner | Required approval | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Whether to continue the Canyon Response Logistics proposal sprint | Official deadline is September 18 at 2:00 p.m. Eastern. Source M01-I01 (F01, confirmed). | Price totals conflict; technical volume exceeds the limit; coordinator lacks signature authority; upload folder includes working notes. | Pause pending blocker closure; conditional proceed with owner assignments; no-bid if mandatory controls cannot close. | Authorized proposal lead or contracting reviewer | Bid, price, representations, signature, and final-submission approvals: not supplied. | Decision pending — blockers open |

### Completed known-gap example — M01-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Decision | Evidence for | Evidence against | Options and tradeoffs | Decision owner | Required approval | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Whether proposed warehouse evidence supports the amended 14-day delivery requirement | An unsigned availability email exists. Source M01-I03 (F06, provisional). | Signed commitment, capacity evidence, terms, and authorized delivery assessment are not supplied. | Hold dependency open; request approved evidence; no representation of confirmed warehouse availability. | Authorized proposal lead or contracting reviewer | Qualified delivery and subcontract commitment review: not supplied. | Gap open — delivery representation blocked |

### Supporting artifact build sequence

1. **M01-A02 · Disqualifier and owner register** — Produce a bounded, reviewable disqualifier and owner register from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M01-I02, M01-I03 and address M01-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M01-A03 · Opportunity decision-gate record** — Produce a bounded, reviewable opportunity decision-gate record from cited packet evidence while exposing unsupported fields and required approvals. Build 1 row from M01-I03 and address M01-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop pursuit or submission when a mandatory disqualifier, deadline, price, representation, signature, or package control cannot close in time. |
| **Go** | Go conditionally when each blocker has an authorized owner, closure evidence, due point, and fallback. |
| **Escalate** | Escalate bid, pricing, subcontract, representations, and final submission authority to the authorized proposal or contracting owner. |

### Completion test

- [ ] The decision brief uses the official deadline and amendment as controlling evidence.
- [ ] All mandatory blockers and authority limits remain visible with no invented closure.
- [ ] The authorized owner can make a bounded bid/no-bid disposition from the brief.

### Secondary evidence-trace crosswalk

The authored procedure and schema-exact examples above are the main teaching method. This compact crosswalk links the legacy starter and gap controls to the original packet.

#### Legacy worked-starter trace

| Artifact | Criterion | Input | Supported value | How to use it | Boundary |
|---|---|---|---|---|---|
| M01-A01 | M01-EC01 | M01-I01 (F01) | The official submission deadline is September 18 at 2:00 p.m. Eastern. | List the supplied condition as decision evidence and keep the decision, authority, and approval status open. Cite M01-I01 (F01) in the row. | This is one evidence-backed starter entry, not a completed bid/no-bid decision brief or an operational result. |

#### Legacy known-gap trace

| Artifact | Criterion | Missing evidence | Why it matters | Authorized owner or reviewer | Bounded next step | Status |
|---|---|---|---|---|---|---|
| M01-A02 | M01-EC02 | The packet does not supply the complete live records, approvals, or execution results needed to finish the disqualifier and owner register. | Without that evidence, the learner cannot truthfully satisfy M01-EC02 or represent this artifact as complete. | Authorized proposal lead or contracting reviewer | Record the missing evidence in M01-A02, name the authorized reviewer, and leave the outcome pending; do not obtain or simulate the live record in this exercise. | Open — not supplied |

### Decision prompt

**M01-I07:** What bounded decision can the Authorized proposal lead or contracting reviewer make from M01-I07, and what must remain pending until the missing evidence or approval is supplied?

### Artifact-build tables

### M01-A01 · Bid/no-bid decision brief

**Purpose:** Produce a bounded, reviewable bid/no-bid decision brief from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M01-I01, M01-I04, M01-I05, M01-I06, M01-I07

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M01-EC01:** Uses the current official solicitation and amendment as controlling sources
- **M01-EC03:** Names who may authorize bid, price, representations, and final submission
- **M01-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

| Decision | Evidence for | Evidence against | Options and tradeoffs | Decision owner | Required approval | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 01A01R-01 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M01-I01, M01-I04, M01-I05, M01-I06, M01-I07).
- [ ] Every mapped rubric criterion (M01-EC01, M01-EC03, M01-EC04) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M01-A02 · Disqualifier and owner register

**Purpose:** Produce a bounded, reviewable disqualifier and owner register from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M01-I02, M01-I03

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M01-EC02:** Treats warehouse availability and 14-day delivery as unresolved dependencies

| Entry ID | Issue or event | Evidence and source ID | Risk or impact | Owner | Bounded next step | Review point | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 01A02R-01 |  |  |  |  |  |  | Not started |
| 01A02R-02 |  |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M01-I02, M01-I03).
- [ ] Every mapped rubric criterion (M01-EC02) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M01-A03 · Opportunity decision-gate record

**Purpose:** Produce a bounded, reviewable opportunity decision-gate record from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M01-I03

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M01-EC03:** Names who may authorize bid, price, representations, and final submission

| Decision | Evidence for | Evidence against | Options and tradeoffs | Decision owner | Required approval | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 01A03R-01 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M01-I03).
- [ ] Every mapped rubric criterion (M01-EC03) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### Artifact coverage map

| Artifact | Expected rows | Mapped criteria | Scoped case-fact inputs |
|---|---:|---|---|
| M01-A01 · Bid/no-bid decision brief | 1 | M01-EC01, M01-EC03, M01-EC04 | M01-I01, M01-I04, M01-I05, M01-I06, M01-I07 |
| M01-A02 · Disqualifier and owner register | 2 | M01-EC02 | M01-I02, M01-I03 |
| M01-A03 · Opportunity decision-gate record | 1 | M01-EC03 | M01-I03 |

### Decision and revision record

| Decision or question | Supported observations with input IDs | Contradictory evidence | Learner proposal | Alternative | Evidence that would change the recommendation |
|---|---|---|---|---|---|
| | | | | | |

### Evidence-criteria checklist

- [ ] **M01-EC01:** Uses the current official solicitation and amendment as controlling sources
- [ ] **M01-EC02:** Treats warehouse availability and 14-day delivery as unresolved dependencies
- [ ] **M01-EC03:** Names who may authorize bid, price, representations, and final submission
- [ ] **M01-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

### Self-review note

- What did I initially assume?
- Which input contradicted or weakened that assumption?
- What remains outside my role or authority?
- What will I revise before asking for human feedback?

## Module 2 — Rebuild compliance

**Task mode:** bounded-case-starter

**Prompt:** Create a delta-aware requirement matrix covering instructions, evaluation factors, deliverables, and acknowledgments.

**Deliverable:** A versioned starter compliance matrix for the requirement categories explicitly described in F02 through F05, plus a gap register for the unsupplied 47-row solicitation record and amendment text.

### Supplied-input register

| Input ID | Kind | Source record(s) | What the packet supplies | Where I used it |
|---|---|---|---|---|
| M02-I01 | case-fact | F02 | The base package contains 47 requirements, 12 price line items, and two mandatory representations. | |
| M02-I02 | case-fact | F03 | Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment. | |
| M02-I03 | case-fact | F04 | The internal calendar still displays the original deadline in Mountain Time. | |
| M02-I04 | case-fact | F05 | The compliance matrix and current drafts do not reflect the amendment. | |
| M02-I05 | case-fact | F07 | Finance totals $486,200 and the required price form totals $468,200. | |
| M02-I06 | case-fact | F10 | The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics. | |
| M02-I07 | case-fact | F12 | The current upload folder is 31 megabytes and includes internal working notes. | |
| M02-B01 | case-brief | CB01 | Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment. | |
| M02-S01 | assignment-scope | F02, F03, F04, F05, F07, F10, F12 | Build a starter version of “A versioned starter compliance matrix for the requirement categories explicitly described in F02 through F05, plus a gap register for the unsupplied 47-row solicitation record and amendment text.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it. | |

### Completion boundary

Complete a bounded starter and gap analysis using only CB01, F02, F03, F04, F05, F07, F10, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

### Prerequisite check

- [ ] Confirm the aggregate 47 requirements, 12 price lines, and two representations are supplied, but exact requirement text and section/page locations are not.
- [ ] Confirm amendment, calendar, draft, price, page-limit, and upload-folder constraints remain separate.
- [ ] Use all 47 REQ rows; do not invent solicitation wording to make them appear complete.

### Operating procedure

1. Capture each known constraint in the principal matrix and cite the exact module input that establishes it.
2. Initialize REQ-01 through REQ-47 in the requirement register without populating absent section, page, or requirement text.
3. For each retrieved requirement in future work, copy exact text, section/page, amendment effect, owner, response location, evidence source, and review status.
4. Apply amendments by preserving the superseded base text and recording the changed delivery, quantity, or acknowledgment requirement separately.
5. Assign response owners and locations only when authorized records exist; otherwise mark owner and location not supplied.
6. Reconcile page, file-size, price, delivery, deadline, and acknowledgment constraints before declaring the matrix ready.
7. Run a 47-row completeness check and an amendment back-check; no row may be marked compliant from aggregate counts alone.

### Field-by-field guidance — M02-A01

| Field | What high-quality completion requires |
|---|---|
| Item ID | Use a stable constraint identifier distinct from REQ-01 through REQ-47. |
| Supported evidence | State the supplied deadline, amendment, price conflict, page overage, or folder condition exactly. |
| Source input ID | Cite the exact M02-Ixx input and preserve confidence. |
| Criterion or required state | Name the control required for compliance, such as current amendment, price-form agreement, page limit, or clean package. |
| Gap or learner proposal | State missing source text, threshold, response evidence, owner, or disposition; label any workflow proposal. |
| Owner or reviewer | Use Authorized proposal lead or contracting reviewer. |
| Status | Use Constraint confirmed, Gap open, Amendment pending, Conflict open, or Review pending. |

### Completed supported example — M02-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Item ID | Supported evidence | Source input ID | Criterion or required state | Gap or learner proposal | Owner or reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| CONSTRAINT-PRICE-01 | Finance totals $486,200 while the required price form totals $468,200. | M02-I05 (F07, conflicting) | All price artifacts must reconcile to the authorized required form before release. | Line-level reconciliation, correct authorized total, owner, and disposition: not supplied. | Authorized proposal lead and pricing reviewer | Conflict open — release blocker |

### Completed known-gap example — M02-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Item ID | Supported evidence | Source input ID | Criterion or required state | Gap or learner proposal | Owner or reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| CONSTRAINT-REQ-TEXT | The base package contains 47 requirements, but exact source text is not supplied. | M02-I01 (F02, confirmed) | Each requirement must be traced to exact base section/page and amendment effect. | Official base text, section/page, response owner, response location, and review status: not supplied. | Authorized proposal lead or contracting reviewer | Gap open — 47 rows unverified |

### Supporting artifact build sequence

1. **M02-A02 · Forty-seven-requirement gap register** — Produce a bounded, reviewable forty-seven-requirement gap register from cited packet evidence while exposing unsupported fields and required approvals. Build 47 rows from M02-I01 and address M02-EC01. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M02-A03 · Amendment-control register** — Produce a bounded, reviewable amendment-control register from cited packet evidence while exposing unsupported fields and required approvals. Build 3 rows from M02-I02, M02-I03, M02-I04 and address M02-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

#### M02-A02 · Forty-seven-requirement gap register

**Reference-only completed row.** Use it to understand the evidence boundary; do not present it as your own completed work.

**Criterion demonstrated:** M02-EC01

**Why this row is included:** This completed training row demonstrates the declared criterion route for Forty-seven-requirement gap register without claiming live execution or approval.

| Requirement ID | Base section/page | Exact requirement text | Amendment effect | Owner | Response location | Evidence source | Review status | Gap/request |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| REQ-01 | Not supplied | Not supplied; aggregate existence only is confirmed. | Not determined for this requirement; amendment one changes delivery, quantity, and acknowledgment generally. | Not supplied — authorized proposal lead must assign after source retrieval. | Not supplied | M02-I01 (F02, confirmed); M02-I02 (F03, confirmed) for amendment context only | Source retrieval and amendment review pending | Retrieve official base section/page and exact text, then compare amendment one without inventing requirement content. |

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop compliance sign-off when any mandatory row lacks exact source text, amendment treatment, owner, response location, evidence, or review status. |
| **Go** | Go to controlled drafting only for rows whose current requirement and amendment effect are traceable. |
| **Escalate** | Escalate unresolved solicitation interpretation, pricing, representations, page, and submission controls to authorized reviewers. |

### Completion test

- [ ] All 47 REQ identifiers exist and no missing requirement text is fabricated.
- [ ] Known constraints are traceable, and the amendment register preserves superseded versus current requirements.
- [ ] No row is labeled compliant or complete without exact source, owner, response location, and review evidence.

### Secondary evidence-trace crosswalk

The authored procedure and schema-exact examples above are the main teaching method. This compact crosswalk links the legacy starter and gap controls to the original packet.

#### Legacy worked-starter trace

| Artifact | Criterion | Input | Supported value | How to use it | Boundary |
|---|---|---|---|---|---|
| M02-A01 | M02-EC02 | M02-I02 (F03) | Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment. | Place the supplied condition in the appropriate comparison row and leave every unsupplied requirement visibly open. Cite M02-I02 (F03) in the row. | This is one evidence-backed starter entry, not a completed known-constraint compliance matrix or an operational result. |

#### Legacy known-gap trace

| Artifact | Criterion | Missing evidence | Why it matters | Authorized owner or reviewer | Bounded next step | Status |
|---|---|---|---|---|---|---|
| M02-A01 | M02-EC02 | The packet does not supply the complete live records, approvals, or execution results needed to finish the known-constraint compliance matrix. | Without that evidence, the learner cannot truthfully satisfy M02-EC02 or represent this artifact as complete. | Authorized proposal lead or contracting reviewer | Record the missing evidence in M02-A01, name the authorized reviewer, and leave the outcome pending; do not obtain or simulate the live record in this exercise. | Open — not supplied |

### Decision prompt

**M02-I07:** What bounded decision can the Authorized proposal lead or contracting reviewer make from M02-I07, and what must remain pending until the missing evidence or approval is supplied?

### Artifact-build tables

### M02-A01 · Known-constraint compliance matrix

**Purpose:** Produce a bounded, reviewable known-constraint compliance matrix from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M02-I02, M02-I03, M02-I04, M02-I05, M02-I06, M02-I07

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M02-EC02:** Flags the known page, file-size, pricing, delivery, and acknowledgment constraints

| Item ID | Supported evidence | Source input ID | Criterion or required state | Gap or learner proposal | Owner or reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| CONTROL-01 |  |  |  |  |  | Not started |
| CONTROL-02 |  |  |  |  |  | Not started |
| CONTROL-03 |  |  |  |  |  | Not started |
| CONTROL-04 |  |  |  |  |  | Not started |
| CONTROL-05 |  |  |  |  |  | Not started |
| CONTROL-06 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M02-I02, M02-I03, M02-I04, M02-I05, M02-I06, M02-I07).
- [ ] Every mapped rubric criterion (M02-EC02) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M02-A02 · Forty-seven-requirement gap register

**Purpose:** Produce a bounded, reviewable forty-seven-requirement gap register from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M02-I01

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M02-EC01:** Cites supplied fact IDs and creates columns for section, page, exact requirement, owner, artifact, and status without inventing missing solicitation text

| Requirement ID | Base section/page | Exact requirement text | Amendment effect | Owner | Response location | Evidence source | Review status | Gap/request |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| REQ-01 |  |  |  |  |  |  |  | Not started |
| REQ-02 |  |  |  |  |  |  |  | Not started |
| REQ-03 |  |  |  |  |  |  |  | Not started |
| REQ-04 |  |  |  |  |  |  |  | Not started |
| REQ-05 |  |  |  |  |  |  |  | Not started |
| REQ-06 |  |  |  |  |  |  |  | Not started |
| REQ-07 |  |  |  |  |  |  |  | Not started |
| REQ-08 |  |  |  |  |  |  |  | Not started |
| REQ-09 |  |  |  |  |  |  |  | Not started |
| REQ-10 |  |  |  |  |  |  |  | Not started |
| REQ-11 |  |  |  |  |  |  |  | Not started |
| REQ-12 |  |  |  |  |  |  |  | Not started |
| REQ-13 |  |  |  |  |  |  |  | Not started |
| REQ-14 |  |  |  |  |  |  |  | Not started |
| REQ-15 |  |  |  |  |  |  |  | Not started |
| REQ-16 |  |  |  |  |  |  |  | Not started |
| REQ-17 |  |  |  |  |  |  |  | Not started |
| REQ-18 |  |  |  |  |  |  |  | Not started |
| REQ-19 |  |  |  |  |  |  |  | Not started |
| REQ-20 |  |  |  |  |  |  |  | Not started |
| REQ-21 |  |  |  |  |  |  |  | Not started |
| REQ-22 |  |  |  |  |  |  |  | Not started |
| REQ-23 |  |  |  |  |  |  |  | Not started |
| REQ-24 |  |  |  |  |  |  |  | Not started |
| REQ-25 |  |  |  |  |  |  |  | Not started |
| REQ-26 |  |  |  |  |  |  |  | Not started |
| REQ-27 |  |  |  |  |  |  |  | Not started |
| REQ-28 |  |  |  |  |  |  |  | Not started |
| REQ-29 |  |  |  |  |  |  |  | Not started |
| REQ-30 |  |  |  |  |  |  |  | Not started |
| REQ-31 |  |  |  |  |  |  |  | Not started |
| REQ-32 |  |  |  |  |  |  |  | Not started |
| REQ-33 |  |  |  |  |  |  |  | Not started |
| REQ-34 |  |  |  |  |  |  |  | Not started |
| REQ-35 |  |  |  |  |  |  |  | Not started |
| REQ-36 |  |  |  |  |  |  |  | Not started |
| REQ-37 |  |  |  |  |  |  |  | Not started |
| REQ-38 |  |  |  |  |  |  |  | Not started |
| REQ-39 |  |  |  |  |  |  |  | Not started |
| REQ-40 |  |  |  |  |  |  |  | Not started |
| REQ-41 |  |  |  |  |  |  |  | Not started |
| REQ-42 |  |  |  |  |  |  |  | Not started |
| REQ-43 |  |  |  |  |  |  |  | Not started |
| REQ-44 |  |  |  |  |  |  |  | Not started |
| REQ-45 |  |  |  |  |  |  |  | Not started |
| REQ-46 |  |  |  |  |  |  |  | Not started |
| REQ-47 |  |  |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M02-I01).
- [ ] Every mapped rubric criterion (M02-EC01) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M02-A03 · Amendment-control register

**Purpose:** Produce a bounded, reviewable amendment-control register from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M02-I02, M02-I03, M02-I04

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M02-EC03:** Explains how superseded requirements would be preserved once the official base document and amendment are available

| Entry ID | Issue or event | Evidence and source ID | Risk or impact | Owner | Bounded next step | Review point | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| AMEND-01 |  |  |  |  |  |  | Not started |
| AMEND-02 |  |  |  |  |  |  | Not started |
| AMEND-03 |  |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M02-I02, M02-I03, M02-I04).
- [ ] Every mapped rubric criterion (M02-EC03) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### Artifact coverage map

| Artifact | Expected rows | Mapped criteria | Scoped case-fact inputs |
|---|---:|---|---|
| M02-A01 · Known-constraint compliance matrix | 6 | M02-EC02 | M02-I02, M02-I03, M02-I04, M02-I05, M02-I06, M02-I07 |
| M02-A02 · Forty-seven-requirement gap register | 47 | M02-EC01 | M02-I01 |
| M02-A03 · Amendment-control register | 3 | M02-EC03 | M02-I02, M02-I03, M02-I04 |

### Decision and revision record

| Decision or question | Supported observations with input IDs | Contradictory evidence | Learner proposal | Alternative | Evidence that would change the recommendation |
|---|---|---|---|---|---|
| | | | | | |

### Evidence-criteria checklist

- [ ] **M02-EC01:** Cites supplied fact IDs and creates columns for section, page, exact requirement, owner, artifact, and status without inventing missing solicitation text
- [ ] **M02-EC02:** Flags the known page, file-size, pricing, delivery, and acknowledgment constraints
- [ ] **M02-EC03:** Explains how superseded requirements would be preserved once the official base document and amendment are available

### Self-review note

- What did I initially assume?
- Which input contradicted or weakened that assumption?
- What remains outside my role or authority?
- What will I revise before asking for human feedback?

## Module 3 — Recover the calendar

**Task mode:** bounded-case-starter

**Prompt:** Build a backward schedule with review windows, dependencies, and a documented time-zone conversion.

**Deliverable:** A provisional proposal calendar, responsibility map, deadline-verification request, and daily exception-report template.

### Supplied-input register

| Input ID | Kind | Source record(s) | What the packet supplies | Where I used it |
|---|---|---|---|---|
| M03-I01 | case-fact | F01 | The official submission deadline is September 18 at 2:00 p.m. Eastern. | |
| M03-I02 | case-fact | F03 | Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment. | |
| M03-I03 | case-fact | F04 | The internal calendar still displays the original deadline in Mountain Time. | |
| M03-I04 | case-fact | F07 | Finance totals $486,200 and the required price form totals $468,200. | |
| M03-I05 | case-fact | F10 | The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics. | |
| M03-I06 | case-fact | F11 | The coordinator lacks authority to sign the offer or certify representations. | |
| M03-I07 | case-fact | F12 | The current upload folder is 31 megabytes and includes internal working notes. | |
| M03-B01 | case-brief | CB01 | Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment. | |
| M03-S01 | assignment-scope | F01, F03, F04, F07, F10, F11, F12 | Build a starter version of “A provisional proposal calendar, responsibility map, deadline-verification request, and daily exception-report template.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it. | |

### Completion boundary

Complete a bounded starter and gap analysis using only CB01, F01, F03, F04, F07, F10, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

### Prerequisite check

- [ ] Confirm the official Eastern deadline and internal Mountain-time discrepancy.
- [ ] Do not calculate a local deadline without the year and date-specific conversion evidence.
- [ ] Identify price and representation approvals that must precede packaging.

### Operating procedure

1. Anchor the calendar on September 18 at 2:00 p.m. Eastern and cite F01.
2. Mark the year and date-specific local conversion not supplied instead of using the internal Mountain-time entry.
3. Sequence compliance, amendment, price, representation, page, package, and submission reviews backward from the official deadline.
4. Place price reconciliation and representation authorization before final packaging or upload preparation.
5. Assign accountable owner and backup roles to each critical handoff without inventing staff names.
6. Add exception triggers for deadline conflict, page overage, price mismatch, signature boundary, and package contamination.
7. Quality-check time zone, dependencies, review gates, and absence of invented dates or completed milestones.

### Field-by-field guidance — M03-A01

| Field | What high-quality completion requires |
|---|---|
| Milestone or date | Use the official deadline or a proposed relative milestone; mark calendar dates not supplied. |
| Deliverable | Name the specific compliance, price, representation, page, package, or submission output. |
| Evidence | Cite the supplied deadline or constraint and preserve its status. |
| Owner | Use accountable proposal, pricing, representation, packaging, or submission roles only. |
| Dependency | State prerequisite evidence or approval that must close first. |
| Review gate | Define the evidence and authorized disposition required to advance. |
| Exception | Name deadline, version, price, page, authority, or package problem. |
| Status | Use Proposed, Conflict open, Blocked, Review pending, or Ready for authorized review. |

### Completed supported example — M03-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Milestone or date | Deliverable | Evidence | Owner | Dependency | Review gate | Exception | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| September 18, 2:00 p.m. Eastern; year and local conversion not supplied | Authorized final submission | M03-I01 (F01, confirmed) | Authorized submission owner; name not supplied | Price, representations, page limit, package, signature, and amendment acknowledgment must be approved. | Proceed only after authorized package-readiness disposition and confirmed portal plan. | Internal calendar uses original Mountain-time deadline. M03-I03 (F04, confirmed). | Official deadline recorded — conversion gap open |

### Completed known-gap example — M03-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Milestone or date | Deliverable | Evidence | Owner | Dependency | Review gate | Exception | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Date-specific internal cutoff | Verified local deadline and team handoff schedule | Official Eastern deadline supplied; year and correct local conversion not supplied. | Authorized proposal lead | Official year, date-specific time-zone conversion, and approved internal buffer. | Do not publish the local cutoff until verified against the controlling source. | Current internal Mountain-time entry conflicts with official deadline. | Gap open — schedule not final |

### Supporting artifact build sequence

1. **M03-A02 · Responsibility map** — Produce a bounded, reviewable responsibility map from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M03-I02 and address M03-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M03-A03 · Deadline-verification request** — Produce a bounded, reviewable deadline-verification request from cited packet evidence while exposing unsupported fields and required approvals. Build 1 row from M03-I03 and address M03-EC01, M03-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
3. **M03-A04 · Daily exception-report template** — Produce a bounded, reviewable daily exception-report template from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M03-I04 and address M03-EC01. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop packaging or submission when deadline conversion, price, representations, version, page limit, or authority remains unresolved. |
| **Go** | Go to the next calendar gate when its dependencies, owner, backup, and evidence are visible. |
| **Escalate** | Escalate official deadline interpretation and submission authority to the authorized proposal or contracting reviewer. |

### Completion test

- [ ] The official Eastern deadline is preserved and missing year/local conversion remain explicit.
- [ ] Critical approvals precede packaging and submission.
- [ ] Each handoff has accountable and backup roles without invented staff names.

### Secondary evidence-trace crosswalk

The authored procedure and schema-exact examples above are the main teaching method. This compact crosswalk links the legacy starter and gap controls to the original packet.

#### Legacy worked-starter trace

| Artifact | Criterion | Input | Supported value | How to use it | Boundary |
|---|---|---|---|---|---|
| M03-A01 | M03-EC01 | M03-I01 (F01) | The official submission deadline is September 18 at 2:00 p.m. Eastern. | Use the supplied timing condition as an anchor and mark any date, dependency, or completion claim not supplied. Cite M03-I01 (F01) in the row. | This is one evidence-backed starter entry, not a completed proposal calendar or an operational result. |

#### Legacy known-gap trace

| Artifact | Criterion | Missing evidence | Why it matters | Authorized owner or reviewer | Bounded next step | Status |
|---|---|---|---|---|---|---|
| M03-A01 | M03-EC01 | The packet does not supply the complete live records, approvals, or execution results needed to finish the proposal calendar. | Without that evidence, the learner cannot truthfully satisfy M03-EC01 or represent this artifact as complete. | Authorized proposal lead or contracting reviewer | Record the missing evidence in M03-A01, name the authorized reviewer, and leave the outcome pending; do not obtain or simulate the live record in this exercise. | Open — not supplied |

### Decision prompt

**M03-I07:** What bounded decision can the Authorized proposal lead or contracting reviewer make from M03-I07, and what must remain pending until the missing evidence or approval is supplied?

### Artifact-build tables

### M03-A01 · Proposal calendar

**Purpose:** Produce a bounded, reviewable proposal calendar from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M03-I01, M03-I03, M03-I05, M03-I06, M03-I07

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M03-EC01:** Retains the official 2:00 p.m. Eastern deadline and marks the year and date-specific local conversion as required missing evidence

| Milestone or date | Deliverable | Evidence | Owner | Dependency | Review gate | Exception | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 03A01R-01 |  |  |  |  |  |  | Not started |
| 03A01R-02 |  |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M03-I01, M03-I03, M03-I05, M03-I06, M03-I07).
- [ ] Every mapped rubric criterion (M03-EC01) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M03-A02 · Responsibility map

**Purpose:** Produce a bounded, reviewable responsibility map from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M03-I02

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M03-EC02:** Places price and representation approval before packaging

| Item ID | Supported evidence | Source input ID | Criterion or required state | Gap or learner proposal | Owner or reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 03A02R-01 |  |  |  |  |  | Not started |
| 03A02R-02 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M03-I02).
- [ ] Every mapped rubric criterion (M03-EC02) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M03-A03 · Deadline-verification request

**Purpose:** Produce a bounded, reviewable deadline-verification request from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M03-I03

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M03-EC01:** Retains the official 2:00 p.m. Eastern deadline and marks the year and date-specific local conversion as required missing evidence
- **M03-EC03:** Assigns an accountable owner and backup to the critical handoffs evidenced by the packet without inventing staff names

| Section | Supported statement | Source input ID | Assumption or gap | Decision requested | Reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 03A03R-01 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M03-I03).
- [ ] Every mapped rubric criterion (M03-EC01, M03-EC03) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M03-A04 · Daily exception-report template

**Purpose:** Produce a bounded, reviewable daily exception-report template from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M03-I04

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M03-EC01:** Retains the official 2:00 p.m. Eastern deadline and marks the year and date-specific local conversion as required missing evidence

| Entry ID | Issue or event | Evidence and source ID | Risk or impact | Owner | Bounded next step | Review point | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 03A04R-01 |  |  |  |  |  |  | Not started |
| 03A04R-02 |  |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M03-I04).
- [ ] Every mapped rubric criterion (M03-EC01) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### Artifact coverage map

| Artifact | Expected rows | Mapped criteria | Scoped case-fact inputs |
|---|---:|---|---|
| M03-A01 · Proposal calendar | 2 | M03-EC01 | M03-I01, M03-I03, M03-I05, M03-I06, M03-I07 |
| M03-A02 · Responsibility map | 2 | M03-EC02 | M03-I02 |
| M03-A03 · Deadline-verification request | 1 | M03-EC01, M03-EC03 | M03-I03 |
| M03-A04 · Daily exception-report template | 2 | M03-EC01 | M03-I04 |

### Decision and revision record

| Decision or question | Supported observations with input IDs | Contradictory evidence | Learner proposal | Alternative | Evidence that would change the recommendation |
|---|---|---|---|---|---|
| | | | | | |

### Evidence-criteria checklist

- [ ] **M03-EC01:** Retains the official 2:00 p.m. Eastern deadline and marks the year and date-specific local conversion as required missing evidence
- [ ] **M03-EC02:** Places price and representation approval before packaging
- [ ] **M03-EC03:** Assigns an accountable owner and backup to the critical handoffs evidenced by the packet without inventing staff names

### Self-review note

- What did I initially assume?
- Which input contradicted or weakened that assumption?
- What remains outside my role or authority?
- What will I revise before asking for human feedback?

## Module 4 — Repair evidence claims

**Task mode:** bounded-case-starter

**Prompt:** Validate resume, past performance, subcontractor, delivery, and price-support statements.

**Deliverable:** An evidence-ledger starter and claim-correction plan for the resume, warehouse, pricing, delivery, and past-performance issues; source excerpts and permissions not supplied remain explicit gaps.

### Supplied-input register

| Input ID | Kind | Source record(s) | What the packet supplies | Where I used it |
|---|---|---|---|---|
| M04-I01 | case-fact | F03 | Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment. | |
| M04-I02 | case-fact | F06 | A proposed subcontract warehouse supplied only an unsigned availability email. | |
| M04-I03 | case-fact | F07 | Finance totals $486,200 and the required price form totals $468,200. | |
| M04-I04 | case-fact | F08 | The resume claims program leadership while approved records show a deputy role for nine months. | |
| M04-I05 | case-fact | F09 | One proposed past-performance contact has not provided current reference permission. | |
| M04-B01 | case-brief | CB01 | Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment. | |
| M04-S01 | assignment-scope | F03, F06, F07, F08, F09 | Build a starter version of “An evidence-ledger starter and claim-correction plan for the resume, warehouse, pricing, delivery, and past-performance issues; source excerpts and permissions not supplied remain explicit gaps.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it. | |

### Completion boundary

Complete a bounded starter and gap analysis using only CB01, F03, F06, F07, F08, F09, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

### Prerequisite check

- [ ] Confirm the amendment, provisional warehouse evidence, price conflict, resume conflict, and missing reference permission.
- [ ] Separate a claim defect from a missing source record and from an authorized corrected claim.
- [ ] Do not contact references or rewrite resumes as approved evidence in this exercise.

### Operating procedure

1. Create one ledger entry for each material delivery, price, role, date, scope, and permission claim.
2. Record the claim as currently stated and cite the supplied fact showing confirmation, conflict, provisional status, or missing permission.
3. Identify the exact underlying source needed to support or correct the claim.
4. Distinguish correction text as a learner proposal and preserve the original claim and version history.
5. Route price, resume, subcontract availability, delivery, and reference permission to their authorized source owners.
6. Block claim use until the source, permission, reviewer, and corrected version are documented.
7. Quality-check every ledger entry for role, dates, value, scope, delivery, price, permission, and no invented source.

### Field-by-field guidance — M04-A01

| Field | What high-quality completion requires |
|---|---|
| Entry ID | Use a stable claim identifier tied to one statement. |
| Issue or event | Quote or summarize the claim defect without adding unsupported detail. |
| Evidence and source ID | Cite the exact M04-Ixx fact and confidence. |
| Risk or impact | State the compliance, credibility, pricing, delivery, or permission exposure. |
| Owner | Use the authorized source owner or proposal reviewer role. |
| Bounded next step | Request or locate the specific source, then propose correction for review. |
| Review point | Define when the claim must be rechecked before reuse. |
| Status | Use Confirmed defect, Conflict open, Permission missing, Source pending, or Approved use not supplied. |

### Completed supported example — M04-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Entry ID | Issue or event | Evidence and source ID | Risk or impact | Owner | Bounded next step | Review point | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| CLAIM-ROLE-01 | Resume claims program leadership while approved records show a deputy role for nine months. | M04-I04 (F08, conflicting) | Role and duration may be materially overstated in the proposal. | Authorized resume source owner and proposal reviewer | Approved role and date source: not supplied. Obtain it, draft a source-faithful correction, and retain both versions. | Before resume or past-performance content is released. | Conflict open — claim use blocked |

### Completed known-gap example — M04-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Entry ID | Issue or event | Evidence and source ID | Risk or impact | Owner | Bounded next step | Review point | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| CLAIM-PERM-01 | Proposed past-performance contact has not provided current reference permission. | M04-I05 (F09, confirmed) | Unpermitted contact use may create privacy, relationship, or compliance exposure. | Authorized past-performance source owner | Record a permission request requirement; do not contact or claim permission in this exercise. | Before naming the contact or submitting the reference. | Permission not supplied — use blocked |

### Supporting artifact build sequence

1. **M04-A02 · Claim-correction plan** — Produce a bounded, reviewable claim-correction plan from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M04-I02 and address M04-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M04-A03 · Source-permission register** — Produce a bounded, reviewable source-permission register from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M04-I01, M04-I03, M04-I04, M04-I05 and address M04-EC02, M04-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop use of any claim whose role, date, value, scope, delivery, price, or permission lacks authorized source support. |
| **Go** | Go to review when original claim, source conflict, proposed correction, owner, and version history are visible. |
| **Escalate** | Escalate price, resume, subcontract, delivery, and reference-permission claims to their authorized source owners. |

### Completion test

- [ ] All five supplied claim issues are separated into source, defect, correction, permission, and owner fields.
- [ ] No corrected claim is represented as approved or used.
- [ ] Version history and review status preserve original and proposed wording.

### Secondary evidence-trace crosswalk

The authored procedure and schema-exact examples above are the main teaching method. This compact crosswalk links the legacy starter and gap controls to the original packet.

#### Legacy worked-starter trace

| Artifact | Criterion | Input | Supported value | How to use it | Boundary |
|---|---|---|---|---|---|
| M04-A01 | M04-EC01 | M04-I01 (F03) | Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment. | Open a traceable register entry for the supplied condition and route the unresolved decision to the named authorized role. Cite M04-I01 (F03) in the row. | This is one evidence-backed starter entry, not a completed claim-evidence ledger or an operational result. |

#### Legacy known-gap trace

| Artifact | Criterion | Missing evidence | Why it matters | Authorized owner or reviewer | Bounded next step | Status |
|---|---|---|---|---|---|---|
| M04-A01 | M04-EC01 | The packet does not supply the complete live records, approvals, or execution results needed to finish the claim-evidence ledger. | Without that evidence, the learner cannot truthfully satisfy M04-EC01 or represent this artifact as complete. | Authorized proposal lead or contracting reviewer | Record the missing evidence in M04-A01, name the authorized reviewer, and leave the outcome pending; do not obtain or simulate the live record in this exercise. | Open — not supplied |

### Decision prompt

**M04-I05:** What bounded decision can the Authorized proposal lead or contracting reviewer make from M04-I05, and what must remain pending until the missing evidence or approval is supplied?

### Artifact-build tables

### M04-A01 · Claim-evidence ledger

**Purpose:** Produce a bounded, reviewable claim-evidence ledger from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M04-I01

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M04-EC01:** Uses F03, F06, F07, F08, and F09 to separate known claim defects from missing source records

| Entry ID | Issue or event | Evidence and source ID | Risk or impact | Owner | Bounded next step | Review point | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 04A01R-01 |  |  |  |  |  |  | Not started |
| 04A01R-02 |  |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M04-I01).
- [ ] Every mapped rubric criterion (M04-EC01) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M04-A02 · Claim-correction plan

**Purpose:** Produce a bounded, reviewable claim-correction plan from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M04-I02

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M04-EC03:** Routes each corrected excerpt and commitment claim to the authorized source owner before use

| Step or milestone | Trigger or date | Evidence and source ID | Owner | Gate or threshold | Dependency or gap | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 04A02R-01 |  |  |  |  |  | Not started |
| 04A02R-02 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M04-I02).
- [ ] Every mapped rubric criterion (M04-EC03) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M04-A03 · Source-permission register

**Purpose:** Produce a bounded, reviewable source-permission register from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M04-I01, M04-I03, M04-I04, M04-I05

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M04-EC02:** Provides fields for role, dates, value, scope, delivery, price, and permission without inventing the unavailable underlying documents
- **M04-EC03:** Routes each corrected excerpt and commitment claim to the authorized source owner before use

| Entry ID | Issue or event | Evidence and source ID | Risk or impact | Owner | Bounded next step | Review point | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 04A03R-01 |  |  |  |  |  |  | Not started |
| 04A03R-02 |  |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M04-I01, M04-I03, M04-I04, M04-I05).
- [ ] Every mapped rubric criterion (M04-EC02, M04-EC03) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### Artifact coverage map

| Artifact | Expected rows | Mapped criteria | Scoped case-fact inputs |
|---|---:|---|---|
| M04-A01 · Claim-evidence ledger | 2 | M04-EC01 | M04-I01 |
| M04-A02 · Claim-correction plan | 2 | M04-EC03 | M04-I02 |
| M04-A03 · Source-permission register | 2 | M04-EC02, M04-EC03 | M04-I01, M04-I03, M04-I04, M04-I05 |

### Decision and revision record

| Decision or question | Supported observations with input IDs | Contradictory evidence | Learner proposal | Alternative | Evidence that would change the recommendation |
|---|---|---|---|---|---|
| | | | | | |

### Evidence-criteria checklist

- [ ] **M04-EC01:** Uses F03, F06, F07, F08, and F09 to separate known claim defects from missing source records
- [ ] **M04-EC02:** Provides fields for role, dates, value, scope, delivery, price, and permission without inventing the unavailable underlying documents
- [ ] **M04-EC03:** Routes each corrected excerpt and commitment claim to the authorized source owner before use

### Self-review note

- What did I initially assume?
- Which input contradicted or weakened that assumption?
- What remains outside my role or authority?
- What will I revise before asking for human feedback?

## Module 5 — Run controlled reviews

**Task mode:** bounded-case-starter

**Prompt:** Plan compliance, content, price, and final-production reviews with finding closure.

**Deliverable:** A review plan and finding log showing retest and authorized disposition.

### Supplied-input register

| Input ID | Kind | Source record(s) | What the packet supplies | Where I used it |
|---|---|---|---|---|
| M05-I01 | case-fact | F03 | Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment. | |
| M05-I02 | case-fact | F05 | The compliance matrix and current drafts do not reflect the amendment. | |
| M05-I03 | case-fact | F07 | Finance totals $486,200 and the required price form totals $468,200. | |
| M05-I04 | case-fact | F10 | The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics. | |
| M05-I05 | case-fact | F11 | The coordinator lacks authority to sign the offer or certify representations. | |
| M05-I06 | case-fact | F12 | The current upload folder is 31 megabytes and includes internal working notes. | |
| M05-B01 | case-brief | CB01 | Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment. | |
| M05-S01 | assignment-scope | F03, F05, F07, F10, F11, F12 | Build a starter version of “A review plan and finding log showing retest and authorized disposition.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it. | |

### Completion boundary

Complete a bounded starter and gap analysis using only CB01, F03, F05, F07, F10, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

### Prerequisite check

- [ ] Confirm amendment omission, price conflict, page overage, signature limit, and upload-folder condition.
- [ ] Define review entry criteria and severity before assigning reviewers.
- [ ] No reviewer names, retest results, dispositions, or approved package versions are supplied.

### Operating procedure

1. Define each review’s purpose, entry evidence, reviewer role, severity scale, due point, and exit evidence.
2. Sequence compliance, pricing, technical/page, representations, and package reviews against one controlled version.
3. Create findings for amendment omission and price mismatch with exact source IDs and release-blocker severity.
4. Assign corrective evidence and retest method without rewriting the artifact for its owner.
5. Record authorized disposition separately from finding closure and never infer approval from a retest request.
6. Block release when the wrong version, unresolved price, amendment, page, signature, or internal-note issue remains.
7. Quality-check reviewer independence, version identity, finding trace, owner, retest evidence, and disposition status.

### Field-by-field guidance — M05-A01

| Field | What high-quality completion requires |
|---|---|
| Step or milestone | Name a specific review stage and purpose. |
| Trigger or date | State the entry condition or mark due time not supplied. |
| Evidence and source ID | Cite the facts that justify the review or blocker. |
| Owner | Use the authorized review role, not an invented person. |
| Gate or threshold | Define entry, severity, closure evidence, and authorized exit disposition. |
| Dependency or gap | Record missing current version, correction, reviewer, time, or retest evidence. |
| Status | Use Proposed review, Entry blocked, Finding open, Retest pending, or Disposition pending. |

### Completed supported example — M05-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Step or milestone | Trigger or date | Evidence and source ID | Owner | Gate or threshold | Dependency or gap | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Compliance review of amendment one | Before price, technical, and package release; exact review time not supplied. | M05-I01 (F03, confirmed); M05-I02 (F05, confirmed) | Authorized compliance reviewer | Current matrix and drafts must reflect changed delivery, quantity, and acknowledgment before release. | Corrected controlled version, reviewer identity, retest evidence, and disposition: not supplied. | Release blocker — finding and retest pending |

### Completed known-gap example — M05-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Step or milestone | Trigger or date | Evidence and source ID | Owner | Gate or threshold | Dependency or gap | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Package review for clean upload set | Before portal upload; exact cutoff not supplied. | M05-I06 (F12, confirmed) | Authorized package and submission reviewer | Only required files, no internal notes, and approved size/version controls may pass. | Portal size limit, clean package, hash, review evidence, and disposition: not supplied. | Entry blocked — package evidence missing |

### Supporting artifact build sequence

1. **M05-A02 · Finding and retest log** — Produce a bounded, reviewable finding and retest log from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M05-I02, M05-I03 and address M05-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M05-A03 · Authorized disposition record** — Produce a bounded, reviewable authorized disposition record from cited packet evidence while exposing unsupported fields and required approvals. Build 1 row from M05-I03 and address M05-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop release while any material compliance, price, page, representation, version, signature, or package finding remains open. |
| **Go** | Go to authorized disposition only after a focused retest confirms the exact closure evidence on the controlled version. |
| **Escalate** | Escalate final finding disposition and release authority to the authorized proposal lead or contracting reviewer. |

### Completion test

- [ ] Every review names purpose, entry criteria, severity, owner, due point, and exit evidence.
- [ ] Unresolved compliance and price findings are release blockers.
- [ ] Review, retest, disposition, and package version remain distinct records.

### Secondary evidence-trace crosswalk

The authored procedure and schema-exact examples above are the main teaching method. This compact crosswalk links the legacy starter and gap controls to the original packet.

#### Legacy worked-starter trace

| Artifact | Criterion | Input | Supported value | How to use it | Boundary |
|---|---|---|---|---|---|
| M05-A01 | M05-EC01 | M05-I01 (F03) | Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment. | Use the supplied condition to define one bounded step and a review gate; leave dates and execution results pending unless supplied. Cite M05-I01 (F03) in the row. | This is one evidence-backed starter entry, not a completed controlled review plan or an operational result. |

#### Legacy known-gap trace

| Artifact | Criterion | Missing evidence | Why it matters | Authorized owner or reviewer | Bounded next step | Status |
|---|---|---|---|---|---|---|
| M05-A01 | M05-EC01 | The packet does not supply the complete live records, approvals, or execution results needed to finish the controlled review plan. | Without that evidence, the learner cannot truthfully satisfy M05-EC01 or represent this artifact as complete. | Authorized proposal lead or contracting reviewer | Record the missing evidence in M05-A01, name the authorized reviewer, and leave the outcome pending; do not obtain or simulate the live record in this exercise. | Open — not supplied |

### Decision prompt

**M05-I06:** What bounded decision can the Authorized proposal lead or contracting reviewer make from M05-I06, and what must remain pending until the missing evidence or approval is supplied?

### Artifact-build tables

### M05-A01 · Controlled review plan

**Purpose:** Produce a bounded, reviewable controlled review plan from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M05-I01, M05-I04, M05-I05, M05-I06

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M05-EC01:** Defines reviewer purpose, entry criteria, severity, owner, and due time
- **M05-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

| Step or milestone | Trigger or date | Evidence and source ID | Owner | Gate or threshold | Dependency or gap | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 05A01R-01 |  |  |  |  |  | Not started |
| 05A01R-02 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M05-I01, M05-I04, M05-I05, M05-I06).
- [ ] Every mapped rubric criterion (M05-EC01, M05-EC04) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M05-A02 · Finding and retest log

**Purpose:** Produce a bounded, reviewable finding and retest log from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M05-I02, M05-I03

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M05-EC02:** Treats unresolved compliance and price gaps as release blockers

| Entry ID | Issue or event | Evidence and source ID | Risk or impact | Owner | Bounded next step | Review point | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 05A02R-01 |  |  |  |  |  |  | Not started |
| 05A02R-02 |  |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M05-I02, M05-I03).
- [ ] Every mapped rubric criterion (M05-EC02) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M05-A03 · Authorized disposition record

**Purpose:** Produce a bounded, reviewable authorized disposition record from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M05-I03

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M05-EC03:** Uses version control so reviewers assess the correct package

| Decision | Evidence for | Evidence against | Options and tradeoffs | Decision owner | Required approval | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 05A03R-01 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M05-I03).
- [ ] Every mapped rubric criterion (M05-EC03) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### Artifact coverage map

| Artifact | Expected rows | Mapped criteria | Scoped case-fact inputs |
|---|---:|---|---|
| M05-A01 · Controlled review plan | 2 | M05-EC01, M05-EC04 | M05-I01, M05-I04, M05-I05, M05-I06 |
| M05-A02 · Finding and retest log | 2 | M05-EC02 | M05-I02, M05-I03 |
| M05-A03 · Authorized disposition record | 1 | M05-EC03 | M05-I03 |

### Decision and revision record

| Decision or question | Supported observations with input IDs | Contradictory evidence | Learner proposal | Alternative | Evidence that would change the recommendation |
|---|---|---|---|---|---|
| | | | | | |

### Evidence-criteria checklist

- [ ] **M05-EC01:** Defines reviewer purpose, entry criteria, severity, owner, and due time
- [ ] **M05-EC02:** Treats unresolved compliance and price gaps as release blockers
- [ ] **M05-EC03:** Uses version control so reviewers assess the correct package
- [ ] **M05-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

### Self-review note

- What did I initially assume?
- Which input contradicted or weakened that assumption?
- What remains outside my role or authority?
- What will I revise before asking for human feedback?

## Module 6 — Prove submission readiness

**Task mode:** bounded-case-starter

**Prompt:** Design a clean-package and portal-submission simulation without uploading, signing, hashing, timestamping, or claiming receipt.

**Deliverable:** A submission-readiness checklist, package-manifest starter, mock-receipt template, and lessons-learned template with execution evidence pending.

### Supplied-input register

| Input ID | Kind | Source record(s) | What the packet supplies | Where I used it |
|---|---|---|---|---|
| M06-I01 | case-fact | F01 | The official submission deadline is September 18 at 2:00 p.m. Eastern. | |
| M06-I02 | case-fact | F02 | The base package contains 47 requirements, 12 price line items, and two mandatory representations. | |
| M06-I03 | case-fact | F03 | Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment. | |
| M06-I04 | case-fact | F10 | The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics. | |
| M06-I05 | case-fact | F11 | The coordinator lacks authority to sign the offer or certify representations. | |
| M06-I06 | case-fact | F12 | The current upload folder is 31 megabytes and includes internal working notes. | |
| M06-B01 | case-brief | CB01 | Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment. | |
| M06-S01 | assignment-scope | F01, F02, F03, F10, F11, F12 | Build a starter version of “A submission-readiness checklist, package-manifest starter, mock-receipt template, and lessons-learned template with execution evidence pending.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it. | |

### Completion boundary

Complete a bounded starter and gap analysis using only CB01, F01, F02, F03, F10, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

### Prerequisite check

- [ ] Confirm official deadline, base-package counts, amendment acknowledgment, page overage, signature boundary, and upload-folder condition.
- [ ] Treat package hash, portal timestamp, receipt, retained version, and authorized signatures as future fields only.
- [ ] No upload, portal action, acknowledgment, signature, or receipt is supplied.

### Operating procedure

1. List every required package and portal control supported by the packet before preparing a readiness result.
2. Define evidence required for page limit, file size, clean files, price agreement, amendment acknowledgment, representations, and authorized signature.
3. Cite the source input for each check and distinguish fact supplied from result not supplied.
4. Assign role-level owners for content, price, representations, signature, packaging, and submission.
5. Use the manifest and mock receipt fields only as templates; never fabricate hash, timestamp, portal receipt, or retained version.
6. Block readiness if internal notes, page overage, price conflict, signature, or acknowledgment remain unresolved.
7. Quality-check manifest-to-checklist coverage, versions, permissions, exact deadline, and absence of implied submission.

### Field-by-field guidance — M06-A01

| Field | What high-quality completion requires |
|---|---|
| Check ID | Use a stable readiness-control identifier. |
| Control or check | Name the exact file, page, price, acknowledgment, signature, representation, or portal control. |
| Evidence required | Specify the file, comparison, approval, receipt, hash, or timestamp needed. |
| Source input ID | Cite the supplied fact that creates the control. |
| Owner | Use authorized content, pricing, signature, packaging, or submission role. |
| Result | Use Not tested, Fact supplied, Exception present, or Approval not supplied. |
| Exception or gap | State the exact missing or failing evidence. |
| Status | Use Blocking, Ready for review, Template only, or Submission not performed. |

### Completed supported example — M06-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Check ID | Control or check | Evidence required | Source input ID | Owner | Result | Exception or gap | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| READY-PAGE-01 | Technical volume complies with stated page limit | Controlled final technical volume and independent page-count evidence. | M06-I04 (F10, confirmed) | Authorized technical-volume and compliance reviewer | Current draft exceeds its stated limit by 1.5 pages before final graphics. | Corrected final volume, final graphics impact, page-count evidence, and approval: not supplied. | Blocking — readiness not demonstrated |

### Completed known-gap example — M06-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Check ID | Control or check | Evidence required | Source input ID | Owner | Result | Exception or gap | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| READY-PORTAL-01 | Portal package upload and receipt evidence | Approved package hash, upload timestamp, portal receipt, and retained submitted version. | M06-I06 (F12, confirmed, package condition only) | Authorized submission owner | No upload or receipt is supplied; current folder contains internal working notes. | Clean package, portal limit, hash, timestamp, receipt, and retained version: not supplied. | Template only — submission not performed |

### Supporting artifact build sequence

1. **M06-A02 · Package-manifest starter** — Produce a bounded, reviewable package-manifest starter from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M06-I02, M06-I03, M06-I05 and address M06-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M06-A03 · Mock receipt template** — Produce a bounded, reviewable mock receipt template from cited packet evidence while exposing unsupported fields and required approvals. Build 1 row from M06-I03 and address M06-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
3. **M06-A04 · Lessons-learned template** — Produce a bounded, reviewable lessons-learned template from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M06-I04 and address M06-EC04. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop upload when any required file, size, page, price, acknowledgment, representation, signature, version, or package-cleanliness control is unresolved. |
| **Go** | Go to authorized upload only after every readiness check has traceable evidence and approval. |
| **Escalate** | Escalate signature, representations, amendment acknowledgment, and final submission to authorized owners. |

### Completion test

- [ ] The checklist covers required files, portal controls, page, package, signature, representations, and acknowledgment.
- [ ] Future hash, timestamp, receipt, and retained-version fields remain not supplied.
- [ ] No submission, signature, acknowledgment, or portal result is fabricated.

### Secondary evidence-trace crosswalk

The authored procedure and schema-exact examples above are the main teaching method. This compact crosswalk links the legacy starter and gap controls to the original packet.

#### Legacy worked-starter trace

| Artifact | Criterion | Input | Supported value | How to use it | Boundary |
|---|---|---|---|---|---|
| M06-A01 | M06-EC01 | M06-I01 (F01) | The official submission deadline is September 18 at 2:00 p.m. Eastern. | Use the supplied condition to define one check, then mark the result pending until the required verification evidence exists. Cite M06-I01 (F01) in the row. | This is one evidence-backed starter entry, not a completed submission-readiness checklist or an operational result. |

#### Legacy known-gap trace

| Artifact | Criterion | Missing evidence | Why it matters | Authorized owner or reviewer | Bounded next step | Status |
|---|---|---|---|---|---|---|
| M06-A01 | M06-EC01 | The packet does not supply the complete live records, approvals, or execution results needed to finish the submission-readiness checklist. | Without that evidence, the learner cannot truthfully satisfy M06-EC01 or represent this artifact as complete. | Authorized proposal lead or contracting reviewer | Record the missing evidence in M06-A01, name the authorized reviewer, and leave the outcome pending; do not obtain or simulate the live record in this exercise. | Open — not supplied |

### Decision prompt

**M06-I06:** What bounded decision can the Authorized proposal lead or contracting reviewer make from M06-I06, and what must remain pending until the missing evidence or approval is supplied?

### Artifact-build tables

### M06-A01 · Submission-readiness checklist

**Purpose:** Produce a bounded, reviewable submission-readiness checklist from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M06-I01, M06-I04, M06-I06

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M06-EC01:** Lists the required-file and portal-size controls supported by F10 and F12 while leaving exact final files pending

| Check ID | Control or check | Evidence required | Source input ID | Owner | Result | Exception or gap | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 06A01R-01 |  |  |  |  |  |  | Not started |
| 06A01R-02 |  |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M06-I01, M06-I04, M06-I06).
- [ ] Every mapped rubric criterion (M06-EC01) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M06-A02 · Package-manifest starter

**Purpose:** Produce a bounded, reviewable package-manifest starter from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M06-I02, M06-I03, M06-I05

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M06-EC02:** Requires authorized signature, representations, and amendment acknowledgment without recording completion

| Item | Source or location | Version or date | Owner | Access or review status | Gap |
| --- | --- | --- | --- | --- | --- |
| 06A02R-01 |  |  |  |  | Not started |
| 06A02R-02 |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M06-I02, M06-I03, M06-I05).
- [ ] Every mapped rubric criterion (M06-EC02) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M06-A03 · Mock receipt template

**Purpose:** Produce a bounded, reviewable mock receipt template from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M06-I03

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M06-EC03:** Provides fields for a future package hash, portal timestamp, receipt, and retained version but does not fabricate those results

| Section or field | Purpose | Supported entry | Source input ID | Gap or learner proposal | Owner or reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 06A03R-01 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M06-I03).
- [ ] Every mapped rubric criterion (M06-EC03) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### M06-A04 · Lessons-learned template

**Purpose:** Produce a bounded, reviewable lessons-learned template from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M06-I04

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M06-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

| Section or field | Purpose | Supported entry | Source input ID | Gap or learner proposal | Owner or reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 06A04R-01 |  |  |  |  |  | Not started |
| 06A04R-02 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M06-I04).
- [ ] Every mapped rubric criterion (M06-EC04) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Authorized proposal lead or contracting reviewer is named for decisions or review; no approval or execution is implied.

### Artifact coverage map

| Artifact | Expected rows | Mapped criteria | Scoped case-fact inputs |
|---|---:|---|---|
| M06-A01 · Submission-readiness checklist | 2 | M06-EC01 | M06-I01, M06-I04, M06-I06 |
| M06-A02 · Package-manifest starter | 2 | M06-EC02 | M06-I02, M06-I03, M06-I05 |
| M06-A03 · Mock receipt template | 1 | M06-EC03 | M06-I03 |
| M06-A04 · Lessons-learned template | 2 | M06-EC04 | M06-I04 |

### Decision and revision record

| Decision or question | Supported observations with input IDs | Contradictory evidence | Learner proposal | Alternative | Evidence that would change the recommendation |
|---|---|---|---|---|---|
| | | | | | |

### Evidence-criteria checklist

- [ ] **M06-EC01:** Lists the required-file and portal-size controls supported by F10 and F12 while leaving exact final files pending
- [ ] **M06-EC02:** Requires authorized signature, representations, and amendment acknowledgment without recording completion
- [ ] **M06-EC03:** Provides fields for a future package hash, portal timestamp, receipt, and retained version but does not fabricate those results
- [ ] **M06-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

### Self-review note

- What did I initially assume?
- Which input contradicted or weakened that assumption?
- What remains outside my role or authority?
- What will I revise before asking for human feedback?

## Final packet review

- [ ] Every material statement cites an input ID.
- [ ] Every omitted record is marked **not supplied**.
- [ ] Every designed control or template is marked **learner proposal**.
- [ ] Every mapped criterion is addressed in its artifact or a named gap.
- [ ] Contracted row counts and row IDs remain intact.
- [ ] Specialist and decision-owner handoffs are explicit.
- [ ] No simulated work is represented as a completed real-world action, approval, test, signature, or professional opinion.