kushi-agents 3.4.1

package/plugin/templates/snapshot/ado-item.template.md

@@ -0,0 +1,45 @@
+# ADO Work Item: #<id>
+
+> **Snapshot.** Replaced on every refresh.
+> Last fetched: <YYYY-MM-DD HH:mm TZ>
+
+## Header
+
+- **Title**: <title>
+- **Type**: <Epic | Feature | User Story | Task | Bug | Engagement>
+- **State**: <state>
+- **Parent**: #<parent-id> — <parent-title>
+- **Area**: <areaPath>
+- **Iteration**: <iterationPath>
+- **Assigned To**: <name>
+- **Tags**: <tags>
+
+## Source Basis
+- Tool used: <WorkIQ | ADO REST via az-cli token>
+- Mutable hint: `ado.engagementId` = <id>
+
+## Fields
+
+| Field | Value |
+|-------|-------|
+
+## Description (verbatim)
+
+<verbatim work item description body>
+
+## Repro Steps / Acceptance Criteria (if present, verbatim)
+
+<verbatim>
+
+---
+
+> Comments, state changes, attachments are in `stream/items/<id>/<week>_ado-stream.md`.
+
+## Validation
+
+> Thoroughness detector checklist — per `thoroughness-detector.instructions.md`.
+
+- [ ] bodies-present (full body, not just metadata/link)
+- [ ] metadata-fields-complete
+- [ ] no-link-only-stubs
+- [ ] coverage-notes-explain-any-gaps

package/plugin/templates/snapshot/crm-record.template.md

@@ -0,0 +1,34 @@
+# CRM Record: <record-id>
+
+> **Snapshot.** Replaced on every refresh.
+> Entity: <entitySetName>
+> Last fetched: <YYYY-MM-DD HH:mm TZ>
+
+## Source Basis
+- Tool used: <WorkIQ | Dataverse REST via az-cli token>
+- Mutable hint: `crm.recordId` = <guid>
+
+## Fields (every field the API returned)
+
+| Field | Value |
+|-------|-------|
+| <name> | <value> |
+
+## Linked entities (lookups)
+
+| Lookup | Target entity | Display name | Id |
+|--------|---------------|--------------|----|
+
+---
+
+> Annotations, activity logs, and field-level changes are in `stream/<record-id>/<week>_crm-stream.md`.
+> NEVER editorialize or summarize fields here — preserve the API's raw values.
+
+## Validation
+
+> Thoroughness detector checklist — per `thoroughness-detector.instructions.md`.
+
+- [ ] bodies-present (full body, not just metadata/link)
+- [ ] metadata-fields-complete
+- [ ] no-link-only-stubs
+- [ ] coverage-notes-explain-any-gaps

package/plugin/templates/snapshot/meetings-series-index.template.md

@@ -0,0 +1,32 @@
+# Meetings Series Index — <project>
+
+> **Snapshot.** Replaced on every refresh.
+> Last fetched: <YYYY-MM-DD HH:mm TZ>
+
+## Source Basis
+- Tool used: <WorkIQ | m365_list_meetings | Graph>
+- Mutable hint: `calendarContext.subjectKeywords` = [...]
+
+## Recurring Series
+
+| Series ID | Subject | Cadence | Organizer | Required Attendees | Optional | Next Occurrence |
+|-----------|---------|---------|-----------|--------------------|----------|-----------------|
+| <id>      | <subj>  | weekly  | <org>     | <list>             | <list>   | <date>          |
+
+## One-off Meetings (project-tagged)
+
+| Meeting ID | Subject | Date | Organizer | Attendees |
+|------------|---------|------|-----------|-----------|
+
+## Notes
+
+- Per-meeting transcripts and decisions are in `stream/<week>_meetings-stream.md`.
+
+## Validation
+
+> Thoroughness detector checklist — per `thoroughness-detector.instructions.md`.
+
+- [ ] bodies-present (full body, not just metadata/link)
+- [ ] metadata-fields-complete
+- [ ] no-link-only-stubs
+- [ ] coverage-notes-explain-any-gaps

package/plugin/templates/snapshot/onenote-page.template.md

@@ -0,0 +1,28 @@
+# OneNote Page: <Page Title>
+
+> **Snapshot.** Replaced on every refresh.
+> Section: <section name>
+> Notebook: <notebook name>
+> Last modified: <YYYY-MM-DD HH:mm TZ> by <author>
+> Last fetched: <YYYY-MM-DD HH:mm TZ>
+
+## Source Basis
+- Tool used: <WorkIQ | Graph (often 40001) | user-paste>
+- Mutable hint: `one_sectionFileId` = <id>
+
+## Body (verbatim)
+
+<full page body — NOT a summary, NOT a paraphrase. Reproduce content as faithfully as the source allows.>
+
+---
+
+> Edits to this page during refresh windows are captured in `stream/<week>_onenote-stream.md`.
+
+## Validation
+
+> Thoroughness detector checklist — per `thoroughness-detector.instructions.md`.
+
+- [ ] bodies-present (full body, not just metadata/link)
+- [ ] metadata-fields-complete
+- [ ] no-link-only-stubs
+- [ ] coverage-notes-explain-any-gaps

package/plugin/templates/snapshot/sharepoint-file.template.md

@@ -0,0 +1,31 @@
+# SharePoint File: <relative/path/to/file.ext>
+
+> **Snapshot.** Replaced on every refresh of this file.
+> Last modified: <YYYY-MM-DD HH:mm TZ> by <author>
+> Size: <bytes>
+> Web URL: <url>
+> Last fetched: <YYYY-MM-DD HH:mm TZ>
+
+## Source Basis
+- Tool used: <local sync read | WorkIQ | m365_download_file>
+
+## Content Summary
+
+<brief summary of what this file contains and why it matters to the engagement>
+
+## Body (verbatim or close paraphrase, where extractable)
+
+<extracted text content. For binary/Office files: extracted text via WorkIQ or downloaded conversion. Do NOT truncate filenames or invent content.>
+
+---
+
+> File-level change events are in `stream/<week>_sharepoint-stream.md`.
+
+## Validation
+
+> Thoroughness detector checklist — per `thoroughness-detector.instructions.md`.
+
+- [ ] bodies-present (full body, not just metadata/link)
+- [ ] metadata-fields-complete
+- [ ] no-link-only-stubs
+- [ ] coverage-notes-explain-any-gaps

package/plugin/templates/snapshot/sharepoint-tree.template.md

@@ -0,0 +1,39 @@
+# SharePoint Folder Tree — <project>
+
+> **Snapshot.** Replaced on every refresh.
+> Last fetched: <YYYY-MM-DD HH:mm TZ>
+
+## Source Basis
+- Tool used: <local sync walk | WorkIQ | m365_list_files | helpers/sharepoint-pull.ps1>
+- Mutable hint: `sharePoint.localFolder` = <path>; `sharePoint.siteUrl` = <url>
+
+## Root: <site/library path>
+
+```
+/
+├── <subfolder>/
+│   ├── <subfolder>/
+│   │   └── <file.ext>           (size, modifiedBy, modifiedOn)
+│   └── <file.ext>               (size, modifiedBy, modifiedOn)
+└── <file.ext>                   (size, modifiedBy, modifiedOn)
+```
+
+## Filters applied
+
+- `path_includes`: [...]
+- `path_excludes`: [...]
+- `author_filter`: [...]
+
+## Notes
+
+- Per-file change events are in `stream/<week>_sharepoint-stream.md`.
+- Key file bodies are in `snapshot/files/<relative-path>.md`.
+
+## Validation
+
+> Thoroughness detector checklist — per `thoroughness-detector.instructions.md`.
+
+- [ ] bodies-present (full body, not just metadata/link)
+- [ ] metadata-fields-complete
+- [ ] no-link-only-stubs
+- [ ] coverage-notes-explain-any-gaps

package/plugin/templates/snapshot/teams-roster.template.md

@@ -0,0 +1,27 @@
+# Teams Chat Roster — <project>
+
+> **Snapshot.** Replaced on every refresh. Date-stamped at top, but no date in filename.
+> Last fetched: <YYYY-MM-DD HH:mm TZ>
+
+## Source Basis
+- Tool used: <WorkIQ | m365_list_chats | Graph>
+- Mutable hint: `teamsChatContext.chatIds` = [...]
+
+## Chats
+
+| Chat ID | Topic | Type (1:1, group, channel) | Members | Last activity |
+|---------|-------|-----------------------------|---------|---------------|
+| <id>    | <topic> | <type>                    | <count> | <ts>          |
+
+## Notes
+
+- Membership changes between refreshes are captured in `stream/<week>_teams-stream.md` as join/leave events.
+
+## Validation
+
+> Thoroughness detector checklist — per `thoroughness-detector.instructions.md`.
+
+- [ ] bodies-present (full body, not just metadata/link)
+- [ ] metadata-fields-complete
+- [ ] no-link-only-stubs
+- [ ] coverage-notes-explain-any-gaps

package/plugin/templates/state/00_overview.template.md

@@ -0,0 +1,44 @@
+# Noridian — Project Overview (Current State)
+
+**As of:** 2026-05-06 · **Phase:** Pre-engagement / fit-assessment
+
+---
+
+## One-line
+
+Microsoft ISE is evaluating a non-billable FDE (Front-Door Engineer) engagement with **Noridian**, anchored on the **MPXe Policy Comments** use case, while the customer is still settling on which use case to pursue.
+
+## Engagement type
+
+- **Non-billable FDE — approved** `[as of 2026-04-13, source: ushak/OneNote/2026-04-13_onenote-summary.md]`
+
+## Customer profile (working assumptions, unconfirmed)
+
+- Open question: **Is Noridian a regional operator?** `[asked 2026-04-13, source: ushak/Teams-Chats/2026-04-13_teams-summary.md]`
+- Existing AWS solution **not scaling** — likely the catalyst for considering Microsoft. `[as of 2026-04-13, source: ushak/OneNote/2026-04-13_onenote-summary.md]`
+- **CMS interest** noted as part of context. `[as of 2026-04-13, source: ushak/OneNote/2026-04-13_onenote-summary.md]`
+
+## Where it stands right now
+
+- Apr 13 client-prep + client-facing meeting **completed**; recording exists.
+- Customer is **bouncing between use cases** after being exposed to broader FDE engagement context. `[as of 2026-04-20, source: ushak/Teams-Chats/2026-04-20_teams-summary.md]`
+- Microsoft side had a **"slight miss" on follow-up material** (week of Apr 27); customer awaiting that material before choosing an approach. `[as of 2026-05-01, source: ushak/Teams-Chats/2026-04-27_teams-summary.md]`
+- **Re-ping planned for early week of May 4** by Alesha. `[as of 2026-05-01, source: ushak/Teams-Chats/2026-04-27_teams-summary.md]`
+
+## Sponsorship
+
+- **Executive sponsorship: confirmed** `[as of 2026-04-13, source: ushak/OneNote/2026-04-13_onenote-summary.md]`
+
+## Headline risks
+
+- Use-case ambiguity (customer indecision on direction).
+- Momentum: ~3 weeks since last client touchpoint with no customer decision; aggravated by delayed follow-up material.
+- Engineering "catcher" readiness — whoever delivers (Noridian internal, third party, or partner-at-arms-length) must be set up for success.
+
+## Headline next steps
+
+1. Send Noridian the overdue follow-up material.
+2. Re-ping customer (Alesha, wk of May 4).
+3. Internal alignment on engineering staffing model — who delivers if this proceeds.
+
+See sibling state files for detail.

package/plugin/templates/state/01_decisions.template.md

@@ -0,0 +1,41 @@
+# Noridian — Decisions Log (Current State)
+
+**As of:** 2026-05-06
+**Convention:** Decisions are listed newest-first. Superseded decisions remain in place with `~~strikethrough~~` and a `Supersedes:` pointer on the new entry. Each decision carries `[as of DATE, source: …]`.
+
+---
+
+## Active Decisions
+
+### D-002 — Engagement model: Non-billable FDE
+- **Decided:** 2026-04-13
+- **Decided by:** Acct team (per OneNote "4/13 - Acct team")
+- **Status:** Approved
+- **Detail:** Microsoft will pursue Noridian via a non-billable Front-Door Engineer engagement.
+- `[as of 2026-04-13, source: ushak/OneNote/2026-04-13_onenote-summary.md]`
+
+### D-001 — Executive sponsorship secured
+- **Decided:** ≤ 2026-04-13 (logged in 4/13 acct team page)
+- **Status:** Confirmed
+- **Detail:** Executive sponsor in place for the Noridian engagement.
+- `[as of 2026-04-13, source: ushak/OneNote/2026-04-13_onenote-summary.md]`
+
+---
+
+## Pending / Not-Yet Decided
+
+- **PD-001 — Use case to anchor the engagement.** MPXe Policy Comments was the originating asset; customer is currently bouncing between options. `[as of 2026-04-20, source: ushak/Teams-Chats/2026-04-20_teams-summary.md]`
+- **PD-002 — Engineering staffing model.** Co-engineering with a third party vs. Noridian internal team — unresolved. `[as of 2026-04-13, source: ushak/Teams-Chats/2026-04-13_teams-summary.md]`
+- **PD-003 — Customer's chosen approach.** Awaiting Noridian's response on follow-up material. `[as of 2026-05-01, source: ushak/Teams-Chats/2026-04-27_teams-summary.md]`
+
+---
+
+## Superseded / Reversed
+
+_None yet._
+
+---
+
+## Conflicts
+
+_None._

package/plugin/templates/state/02_stakeholders.template.md

@@ -0,0 +1,48 @@
+# Noridian — Stakeholders & Roles (Current State)
+
+**As of:** 2026-05-06
+
+---
+
+## Microsoft — Account / Delivery Team
+
+| Person | Role (as last evidenced) | Most recent activity | Source |
+|--------|--------------------------|----------------------|--------|
+| Todd Morris | Acct team — engagement lead-side voice | Posted post-meeting status update Apr 20; targeted internal sync wk of Apr 20 | `ushak/Teams-Chats/2026-04-20_teams-summary.md` |
+| Alesha Baerenwald | Acct team — primary customer-facing follow-up owner | Acknowledged delayed follow-up material; will re-ping customer wk of May 4 | `ushak/Teams-Chats/2026-04-27_teams-summary.md` |
+| Kim Swafford | Acct team — chat owner, included in follow-up loop | Implied via tag in chat | `ushak/Teams-Chats/2026-04-27_teams-summary.md` |
+
+## Microsoft — ISE Team
+
+| Person | Role | Most recent activity | Source |
+|--------|------|----------------------|--------|
+| Bhargav Nookala | ISE — driving fit-assessment, follow-up nudges | 2 follow-up pings to acct team wk of Apr 27 | `ushak/Teams-Chats/2026-04-27_teams-summary.md` |
+| Sara Spalding | ISE — surfaced MPXe deck; chases status | Asked Alesha for next steps on Apr 17 | `ushak/Teams-Chats/2026-04-13_teams-summary.md` |
+| Kavitha Govindarajulu | ISE — surfaced engineering staffing question; tagged Bret | Asked engineering staffing question Apr 13; tagged Bret Stateham Apr 21 | `ushak/Teams-Chats/2026-04-13_teams-summary.md`, `…/2026-04-20_teams-summary.md` |
+| Bret Stateham | ISE — engineering perspective (tagged in) | Tagged into thread Apr 21 | `ushak/Teams-Chats/2026-04-20_teams-summary.md` |
+| Usha Krishnan | ISE — attended Apr 13 prep | Apr 13 attendee | `ushak/Meetings/2026-04-13_meetings-summary.md` |
+| Shiney Koshy | ISE — chat owner | Apr 13 attendee | `ushak/Meetings/2026-04-13_meetings-summary.md` |
+| Chris Mullins | ISE | Apr 13 attendee | `ushak/Meetings/2026-04-13_meetings-summary.md` |
+| Chad Dotzenrod | ISE | Apr 13 attendee | `ushak/Meetings/2026-04-13_meetings-summary.md` |
+
+## Executive
+
+- **Executive sponsor:** Confirmed; specific name not yet captured in evidence. `[as of 2026-04-13, source: ushak/OneNote/2026-04-13_onenote-summary.md]`
+
+## Customer — Noridian
+
+- **Specific customer contacts not yet captured in available evidence.** Pending action: identify Noridian counterparts and add them here.
+
+## Partners / Third Parties
+
+- **Possible co-engineering partner** — undecided. (See PD-002 in `01_decisions.md`.)
+
+---
+
+## Role Changes / Supersedes
+
+_None yet recorded._
+
+## Conflicts
+
+_None._

package/plugin/templates/state/03_architecture-and-solution.template.md

@@ -0,0 +1,56 @@
+# Noridian — Architecture & Solution (Current State)
+
+**As of:** 2026-05-06
+**Maturity:** Pre-design — only use-case framing exists; no solution architecture committed.
+
+---
+
+## Anchor Use Case
+
+### MPXe — Policy Comments
+- Originating asset: `Noridian_2026Feb26_MPXe-Microsoft_PolicyCommentsUseCase.pptx` (in project SharePoint folder; last modified 2026-05-05)
+- Surfaced as the working use-case in Apr 13 prep.
+- `[as of 2026-04-13, source: ushak/Teams-Chats/2026-04-13_teams-summary.md]`
+
+### Status of use-case selection
+- **Open.** Customer is "bouncing between use cases" after seeing broader FDE engagement context. `[as of 2026-04-20, source: ushak/Teams-Chats/2026-04-20_teams-summary.md]`
+
+---
+
+## Existing Customer Landscape
+
+- **Current state:** Noridian operates an **AWS-based solution** that is **not scaling**. This is the trigger for considering Microsoft. `[as of 2026-04-13, source: ushak/OneNote/2026-04-13_onenote-summary.md]`
+- **Adjacent context:** **CMS** is a relevant party / interest area. `[as of 2026-04-13, source: ushak/OneNote/2026-04-13_onenote-summary.md]`
+
+---
+
+## Proposed Microsoft Solution
+
+- **No solution architecture has been authored yet.** Reference framing material:
+  - "Microsoft Agent Factory — FDE Customer Presentation" (slides 6 and 21 used as **fit-assessment lens**). `[as of 2026-04-13, source: ushak/Teams-Chats/2026-04-13_teams-summary.md]`
+
+---
+
+## Components, Integrations, Data
+
+- **TBD.** No component diagram, data flow, or integration list captured to date.
+
+---
+
+## Open Architectural Questions
+
+- **Engineering delivery model** — co-engineering with a third party vs. Noridian internal team. (PD-002.)
+- **Catcher readiness** — whichever party catches the implementation needs operational readiness. `[as of 2026-04-13, source: ushak/Teams-Chats/2026-04-13_teams-summary.md]`
+- **Scalability target** — what specifically about AWS isn't scaling? Throughput? Cost? Operations? Not yet captured.
+
+---
+
+## Conflicts
+
+_None._
+
+---
+
+## Supersedes / History
+
+_No prior architecture has been replaced — this is the first capture._

package/plugin/templates/state/04_workshops-and-key-meetings.template.md

@@ -0,0 +1,43 @@
+# Noridian — Workshops & Key Meetings (Current State)
+
+**As of:** 2026-05-06
+
+---
+
+## Past — Significant Sessions
+
+### 2026-04-13 — Noridian | FDE Request prep before client meeting
+- **Type:** Internal prep + client-facing call (combined session per chat trail)
+- **Why it matters:** First substantive engagement with Noridian; surfaced anchor use case (MPXe Policy Comments), executive sponsorship confirmation, non-billable FDE approval, and key open questions on staffing and customer profile.
+- **Attendees (Microsoft):** Bhargav Nookala, Sara Spalding, Kavitha Govindarajulu, Alesha Baerenwald, Todd Morris, Kim Swafford, Shiney Koshy, Chris Mullins, Chad Dotzenrod, Bret Stateham, Usha Krishnan
+- **Outputs:** Two reference decks circulated; decisions D-001 & D-002 logged; PD-001/PD-002 raised.
+- **Recording:** Yes — `Noridian FDE Request prep before client meeting-20260413_170623-Meeting Recording.mp4` (SharePoint approval seen 2026-05-04).
+- **Transcript:** Not yet pulled. (Action: pull via `m365_get_transcript` for richer content extraction.)
+- `[source: ushak/Meetings/2026-04-13_meetings-summary.md]`
+
+---
+
+## In-Flight / Unconfirmed
+
+### Internal alignment sync (planned wk of Apr 20)
+- Todd Morris flagged he would schedule one. **No calendar evidence found** — either it happened off-calendar, was deferred, or the calendar wasn't scanned wide enough.
+- `[as of 2026-04-20, source: ushak/Teams-Chats/2026-04-20_teams-summary.md]`
+
+---
+
+## Planned / Upcoming
+
+- **Re-engagement ping with Noridian** — early wk of May 4 (Alesha). Not a meeting, but the next customer touchpoint. `[as of 2026-05-01, source: ushak/Teams-Chats/2026-04-27_teams-summary.md]`
+- **Workshop(s):** None scheduled yet. A scoping/use-case workshop is the natural next step once the customer commits to a use case.
+
+---
+
+## Recurring Cadences
+
+- **None established for Noridian specifically.** (Several recurring "FDE Intake — Triage Stand-up" meetings exist on the broader FDE calendar but are not Noridian-specific.)
+
+---
+
+## Conflicts
+
+_None._

package/plugin/templates/state/05_action-items.template.md

@@ -0,0 +1,29 @@
+# Noridian — Open Action Items (Current State)
+
+**As of:** 2026-05-06
+**Scope:** Open / in-progress only. Closed items move to `_archive` section at the bottom.
+
+---
+
+## Open
+
+| ID | Action | Owner | Due | Opened | Latest evidence | Source |
+|----|--------|-------|-----|--------|-----------------|--------|
+| AI-001 | Send Noridian the overdue follow-up material (the asset that prompted Alesha's "slight miss" comment) | Alesha Baerenwald | wk of May 4 | 2026-04-13 (implied) | "still waiting to hear what approach they want to take" | `ushak/Teams-Chats/2026-04-27_teams-summary.md` |
+| AI-002 | Re-ping Noridian on chosen approach | Alesha Baerenwald | early wk of May 4 | 2026-05-01 | Committed in chat 2026-05-01 | `ushak/Teams-Chats/2026-04-27_teams-summary.md` |
+| AI-003 | Hold internal sync to align on next steps (engineering staffing in particular) | Todd Morris | wk of Apr 20 (overdue / status unknown) | 2026-04-20 | Bhargav's follow-up pings on Apr 28/30 suggest internal sync hasn't yielded next steps yet | `ushak/Teams-Chats/2026-04-20_teams-summary.md`, `…/2026-04-27_teams-summary.md` |
+| AI-004 | Confirm Noridian's organizational profile (regional operator?) | Acct team | — | 2026-04-13 | Open | `ushak/Teams-Chats/2026-04-13_teams-summary.md` |
+| AI-005 | Pull Apr 13 meeting transcript for richer detail | ushak | — | 2026-05-06 | Run-log gap | `Evidence/run-log.md` |
+| AI-006 | Identify Noridian customer counterparts and capture in stakeholders state | Acct team | — | 2026-05-06 | No customer contacts captured yet | derived |
+
+---
+
+## Recently Closed
+
+_None yet._
+
+---
+
+## Conflicts
+
+_None._

package/plugin/templates/state/06_risks-and-issues.template.md

@@ -0,0 +1,43 @@
+# Noridian — Risks & Issues (Current State)
+
+**As of:** 2026-05-06
+**Severity scale:** LOW / MED / HIGH
+
+---
+
+## Active
+
+### R-001 — Customer indecision on use case (MED, trending up)
+- **Description:** Customer is "bouncing between use cases" after broader FDE context was presented; no committed direction.
+- **Impact:** Blocks scoping, sizing, architecture, and timeline.
+- **Mitigation:** Send focused follow-up material; re-ping wk of May 4 (AI-001, AI-002).
+- `[as of 2026-04-20, source: ushak/Teams-Chats/2026-04-20_teams-summary.md]`
+
+### R-002 — Momentum loss / Microsoft-side slip (MED, active)
+- **Description:** Acknowledged "slight miss" on getting follow-up material to Noridian; ~3 weeks since the Apr 13 touchpoint with no customer-side decision.
+- **Impact:** Risks customer disengagement or pursuit of alternative paths.
+- **Mitigation:** Close AI-001 immediately; deliberate re-ping (AI-002).
+- `[as of 2026-05-01, source: ushak/Teams-Chats/2026-04-27_teams-summary.md]`
+
+### R-003 — Engineering catcher readiness (MED, latent)
+- **Description:** Whichever party catches delivery (Noridian internal, a third party, or a partner-at-arms-length) needs to be set up for operational success.
+- **Impact:** Implementation quality and post-engagement sustainability.
+- **Mitigation:** Resolve PD-002 (staffing model) before commit; gate decision on catcher readiness check. Owner: Bhargav Nookala / Todd Morris.
+- `[as of 2026-04-13, source: ushak/Teams-Chats/2026-04-13_teams-summary.md]`
+
+### R-004 — Customer profile unknown (LOW, informational)
+- **Description:** It's still unclear whether Noridian is a regional operator and what the org profile implies for solution scale and procurement path.
+- **Mitigation:** Confirm via acct team (AI-004).
+- `[as of 2026-04-13, source: ushak/Teams-Chats/2026-04-13_teams-summary.md]`
+
+---
+
+## Closed
+
+_None yet._
+
+---
+
+## Conflicts
+
+_None._

package/plugin/templates/state/07_timeline-and-milestones.template.md

@@ -0,0 +1,45 @@
+# Noridian — Timeline & Milestones (Current State)
+
+**As of:** 2026-05-06
+
+---
+
+## Past
+
+| Date | Event | Significance | Source |
+|------|-------|--------------|--------|
+| 2026-02-26 | MPXe Policy Comments use-case deck created | Originating asset for the engagement | filename `Noridian_2026Feb26_MPXe-Microsoft_PolicyCommentsUseCase.pptx` |
+| 2026-03-09 → 2026-03-11 | Initial intake / triage notes (OneNote `Noridian.one` → "3/11") | First captured discussion of Noridian | `ushak/OneNote/2026-04-13_onenote-summary.md` (references prior pages) |
+| 2026-04-10 | Teams meeting chat "Noridian \| FDE Request prep before client meeting" created | Communications channel established | `ushak/Teams-Chats/2026-04-13_teams-summary.md` |
+| 2026-04-13 | Apr 13 prep + client-facing meeting | First substantive client touchpoint; D-001 & D-002 captured | `ushak/Meetings/2026-04-13_meetings-summary.md` |
+| 2026-04-17 | Sara asks Alesha for next steps | Status visibility kicks in | `ushak/Teams-Chats/2026-04-13_teams-summary.md` |
+| 2026-04-20 | Todd posts post-meeting status — customer "bouncing between use cases" | First explicit signal of use-case ambiguity | `ushak/Teams-Chats/2026-04-20_teams-summary.md` |
+| 2026-04-28 / 04-30 | Bhargav follow-up pings | Pressure to resolve next steps | `ushak/Teams-Chats/2026-04-27_teams-summary.md` |
+| 2026-05-01 | Alesha acknowledges "slight miss" on follow-up material | Captures the momentum risk | `ushak/Teams-Chats/2026-04-27_teams-summary.md` |
+| 2026-05-04 | SharePoint edit-request approval for Apr 13 meeting recording | Recording now editable / shareable | inbox notification 2026-05-04 |
+| 2026-05-05 | MPXe deck modified (latest edit) | Asset updated | SharePoint folder listing |
+
+---
+
+## Present (this week)
+
+| Target | Owner | Status |
+|--------|-------|--------|
+| Send overdue follow-up material to Noridian (AI-001) | Alesha | Open |
+| Re-ping customer (AI-002) | Alesha | Planned early wk of May 4 |
+| Internal alignment on staffing model (AI-003) | Todd | Status unknown |
+
+---
+
+## Planned / Anticipated
+
+- **Customer commits to a use case.** No date — gates everything downstream.
+- **Scoping / use-case workshop.** No date — natural next step after customer commit.
+- **Engineering staffing decision (PD-002).** Should precede any solution-design work.
+- **Solution architecture draft.** Not started.
+
+---
+
+## Conflicts
+
+_None._

package/plugin/templates/state/08_artifacts-and-deliverables.template.md

@@ -0,0 +1,55 @@
+# Noridian — Artifacts & Deliverables (Current State)
+
+**As of:** 2026-05-06
+
+---
+
+## Decks
+
+| Title | Purpose | Last modified | Location |
+|-------|---------|---------------|----------|
+| Noridian_2026Feb26_MPXe-Microsoft_PolicyCommentsUseCase.pptx | Anchor use-case framing (MPXe Policy Comments) | 2026-05-05 | `…\Engagement Assets\Noridian\` (project SharePoint folder) |
+| Microsoft Agent Factory — FDE Customer Presentation.PPTX | Reference deck for FDE engagement framing; **slides 6 & 21** used as fit-assessment lens | — | Shared in Teams chat 2026-04-13 (not in project folder) |
+
+---
+
+## Recordings
+
+| Title | Date | Location | Notes |
+|-------|------|----------|-------|
+| Noridian FDE Request prep before client meeting (recording .mp4) | 2026-04-13 17:06 UTC | SharePoint (edit-approved 2026-05-04) | Available; transcript not yet pulled. |
+
+---
+
+## OneNote Pages (ISE Work › Noridian.one)
+
+| Page | Date | Content highlights |
+|------|------|-------------------|
+| 4/13 - Acct team | 2026-04-13 | AWS not scaling; CMS interest; exec sponsorship confirmed; non-billable FDE approval |
+| 3/11 (and a 3/11 meeting-notes variant) | 2026-03-09 → 2026-03-11 | Earlier intake / triage notes |
+
+---
+
+## Documents / Code / Diagrams
+
+- **None captured.** No design docs, ADRs, repos, or diagrams have been created for this engagement yet.
+
+---
+
+## CRM / System-of-Record Links
+
+- Dynamics CRM record link shared in chat 2026-04-13 (URL captured in `ushak/Teams-Chats/2026-04-13_teams-summary.md`).
+
+---
+
+## Known Gaps
+
+- No customer-facing artifacts (proposal, scoping doc, ROM) have been produced.
+- Apr 13 meeting transcript not yet captured.
+- No architecture artifacts (see `03_architecture-and-solution.md`).
+
+---
+
+## Conflicts
+
+_None._