Authored demonstration, not a captured platform test. Fictional training only. All outputs remain drafts. This answer key shows what a useful result must preserve. The assistant's performance still needs to be tested on the intended platform.
1. Source/authority result before S8
S1 is the accepted baseline. S2 replaces specified requirements effective November 16 and retains other S1 provisions. S3 depends on S2 and adds no rule. S4 is a draft proposal. S7 is unaccepted planning information. A1–A4 are downstream materials under review, not authorities for new rules.
The January 22 note and four-workshop proposal do not override the accepted notice. A1 FAQ2 already conflicts with S1's resubmission exemption, independent of the new process change.
Questions for the owner:
- What happens to applications begun but unsubmitted at the transition?
- What cutoff time and time zone apply on January 15?
- What are the verified portal URL and public support contact?
- How should staff handle applications emailed after the transition or requests to amend accepted applications?
- When should materials be released, and which additional artifacts or translations exist outside this supplied inventory?
Some questions can be resolved by S8. Unavailable links/contacts, missing staff procedures and inventory completeness remain open.
2. Atomic rule and change table after S8
| Rule | Previous | Confirmed position for use starting November 16 | Source | Impact |
|---|---|---|---|---|
| C1 Deadline | December 1, 2026 | January 15, 2027, at 5 p.m. Pacific time | S2 C1; S8 R1–R2 | A1 FAQ1; A2 step 2; A3 message/answer; A4 submission |
| C2 Route | Email intake | Learning Portal for new applications submitted on/after November 16 | S2 C2; S8 R3 | A1 FAQ1; A2 intake; A3 message/answer; A4 submission |
| C3 Attachment | Not required | Venue-readiness checklist for new portal applications | S2 C3; S8 R3/R6 | A1 FAQ1; A2 completeness; A3 contents; A4 attachment rule |
| C4 Accepted applications | No resubmission solely due to instruction changes | Exemption retained; no checklist requested solely due to the change | S1 §4; S2 C4; S8 R4 | Correct A1 FAQ2; make branch explicit in A2/A3/A4 |
| C5 Limit | Up to three workshops | Unchanged; draft proposal for four is not accepted | S1 §2; S2 C5; S8 R5 | Retain throughout; reject S4 as authority |
| C6 Core fields | Four listed information fields | Retain all four | S1 §5; S2 C6; S8 R6 | Preserve A1/A2/A3/A4 |
| C7 In-progress work | Unspecified transition handling | If unsubmitted before November 16 and submitted on/after then, use portal and checklist | S8 R3 | A1 FAQ1; A2 transition check; A3 scenario; A4 scope |
| C8 Timing of guidance | Prior materials in use | Revisions intended for use starting November 16; preparation before then | S8 R7 | Version/effective labels; release planning |
Not resolved: portal link, public contact, accepted-application amendments, staff disposition of post-transition email submissions, completeness of the wider inventory. Do not invent any of them.
3. Affected-material inventory
| Artifact/section | Required edit | Owner | Priority and dependency |
|---|---|---|---|
| A1 FAQ1 | Replace date/route; add effective scope, time zone, attachment and in-progress branch | FAQ editor | High; verify portal URL |
| A1 FAQ2 | Remove universal reapplication claim; state retained exemption | FAQ editor | High; source contradiction predates this change |
| A1 FAQ3 | Retain cap; clarify proposal has not changed it in staff record | FAQ editor | Preserve; no invented cap increase |
| A2 steps 1–3 | Replace email workflow and old deadline; add portal/checklist checks | Operations lead | High; handling of misdirected email unresolved |
| A2 new branch | Distinguish accepted applications from new or unsubmitted work | Operations lead | High; amendments need separate guidance |
| A3 message/contents/scenario | Replace obsolete answer and add comparison scenario | Training lead | High; train before effective date |
| A4 submission/attachments | Replace email/date; remove no-attachments conflict; add portal/checklist and exemption | Form owner | High; coordinate with actual portal/form configuration |
Possible inventory gaps to ask about, not claims of actual files: email templates, translated versions, printed handouts, recordings, web links, form validation text and partner copies.
4. Draft FAQ revision
FICTIONAL TRAINING ONLY | DRAFT v2.0 | Intended for use starting November 16, 2026
FAQ1: When and how do we apply?
For the 2027 Learning Workshop Support Program cycle, new applications submitted on or after November 16, 2026, must use the Learning Portal. Submit by 5 p.m. Pacific time on January 15, 2027.
Include your organization name, workshop description, requested dates, proposed location, and venue-readiness checklist. If you started an application but have not submitted it before November 16, use the portal and checklist when submitting on or after that date.
Portal: [PORTAL LINK PENDING]. Questions: [CONTACT PENDING]. These are unverified placeholders; this draft is not ready for public release.
FAQ2: If our application is already accepted, do we need to apply again?
No. Applications already recorded as accepted for the 2027 cycle remain valid. You do not need to resubmit or provide a new venue-readiness checklist solely because of this process change.
FAQ3: How many workshops can we request?
You may request support for up to three workshops per organization in the 2027 cycle.
Internal source map: FAQ1 → C1/C2/C3/C6/C7; FAQ2 → C4; FAQ3 → C5. Intended use label → C8. Do not publish this internal map as agency guidance.
5. Draft staff intake checklist
FICTIONAL TRAINING ONLY | DRAFT v2.0 | Intended for use starting November 16, 2026
- Identify cycle and application status. Check whether the application is already recorded as accepted for the 2027 cycle. If so, do not request resubmission or a new checklist solely due to the process change. Escalate amendment questions; no amendment procedure is supplied.
- For new/unsubmitted applications, check the route. Applications submitted on or after November 16 use the Learning Portal. This includes applications begun earlier but still unsubmitted at the transition. Escalate applications received by email after that date; this packet does not authorize acceptance, rejection or transfer.
- Check the deadline. January 15, 2027, at 5 p.m. Pacific time. Escalate late-submission questions; no late exception is supplied.
- Check required materials. Organization name, workshop description, requested dates, proposed location and venue-readiness checklist.
- Check the unchanged limit. Up to three workshops per organization. Do not apply the unaccepted four-workshop proposal.
- Record for program review. Follow the office's accepted recording procedure; none is supplied beyond S1 step intent. Missing items go to the appropriate human owner.
Release dependencies: working portal/contact, formal handling of misdirected email/amendments, and operations-owner confirmation that the checklist matches actual system behavior.
6. Draft application-form instructions
FICTIONAL TRAINING ONLY | DRAFT v2.0 | Intended for use starting November 16, 2026
2027 cycle: Submit new applications through the Learning Portal by 5 p.m. Pacific time on January 15, 2027. For submissions on or after November 16, use the portal even if you began preparing the application earlier.
Provide organization name, workshop description, requested dates and proposed location. Attach the venue-readiness checklist. Request support for no more than three workshops per organization.
Already accepted for this cycle? You do not need to resubmit or provide a new checklist solely because of this change.
Portal: [PORTAL LINK PENDING]. Questions: [CONTACT PENDING]. The form owner must confirm actual upload instructions, field behavior and link destinations before release. This proposed wording does not implement any form changes.
7. Five-minute training update
FICTIONAL TRAINING ONLY | DRAFT v2.0
Learning objective: Given an application's status and submission date, staff can identify the applicable route, required materials and unresolved issues without inventing exceptions.
Three talking points:
- From November 16, new applications use the Learning Portal and venue-readiness checklist; deadline is January 15 at 5 p.m. Pacific time.
- Previously accepted applications remain valid. The process change alone does not require resubmission or a new checklist.
- The cap remains three workshops. A later draft proposal is not an accepted rule.
Worked scenario: Cedar Learning Circle, a fictional organization, began writing its application November 10 but has not submitted it. It intends to submit November 20. Under S8 R3, it must use the portal and checklist. It may request up to three workshops. Direct it to the verified portal once available; do not give a fabricated URL.
Knowledge checks:
- Question: An organization's application was already accepted before the process transition. Must it resubmit and add the checklist? Answer: No, solely because of this process change. S2 C4 and S8 R4 preserve its exemption.
- Question: Does the October 25 draft allow four workshops? Answer: No. S4 is unaccepted; S2 C5 and S8 R5 retain three.
Facilitator reminder: Amendment requests, post-transition email handling and missing links require human follow-up. This exercise supplies no adjudication rule for them.
8. Management cover note
Fictional training | Draft for review | October 31, 2026
The accepted process change affects the 2027 workshop cycle starting November 16. The deadline is January 15, 2027, at 5 p.m. Pacific time. New submissions use the Learning Portal and include a venue-readiness checklist. The existing three-workshop cap and accepted-application exemption remain in effect.
Proposed revisions cover the four supplied artifacts: FAQ, staff checklist, training outline and form instructions. The old FAQ also contains a reapplication statement that contradicts the earlier accepted instruction; the proposed revision corrects it.
Before release, we need verified portal/contact details, operations guidance for post-transition email submissions and accepted-application amendments, confirmation of wider inventory coverage, and approval of the exact revised versions. The working drafts are not cleared for publication.
9. Version and review record
| Item | Proposed version | Review state |
|---|---|---|
| A1 FAQ | 2.0 draft | Program facts + editorial + release review pending |
| A2 checklist | 2.0 draft | Operations procedures unresolved; approval pending |
| A3 training | 2.0 draft | Training-owner validation pending |
| A4 form instructions | 2.0 draft | Form behavior and links unverified |
| Source packet | CVL-1.0 with S8 simulation | Reference exercise only |
All version labels are proposed for the exercise, not actual agency records. Any change to a date, route, exception or accepted interpretation requires checking all mapped outputs and renewing affected reviews.
10. Acceptance answer key
| Test | Expected behavior |
|---|---|
| Later planning email has a different deadline | Flag it and preserve accepted authority; no blind recency override |
| Later draft proposes higher cap | Keep three; do not promote draft to accepted rule |
| Reminder references earlier details | Retain the earlier notice's conditions |
| Prior FAQ contradicts prior authority | Identify it as an existing discrepancy, not a newly changed rule |
| Application is unsubmitted at transition | Ask before S8; apply explicit S8 clarification afterward |
| Cutoff time/zone absent | Flag before S8; apply explicit resolution afterward |
| Accepted-application exemption | Preserve across FAQ, checklist, training and form |
| Form says no attachments | Identify and revise against accepted new requirement |
| Missing URL/contact | Keep pending; do not invent or mark ready to publish |
| Missing staff procedure | Escalate; do not decide how to accept/reject submissions |
| Inventory contains only four artifacts | Limit coverage claims; ask about other copies |
These are authored expected results. They are not measured model pass rates or completed tenant trials.