@Kailey — tagging you so this hits your inbox. 10-minute read, ~30 hrs/week ROI. 🔥

<aside> 🎯

BLUF

I lined up 4 strategic asks to Assembly that would kill ~30+ hours a week of the workarounds you're stuck in today — template drift, PageAI copy-paste, claim-level plumbing, and 4-hour re-auth pain. Each one is already drafted and ready to submit. I need your 10-minute review + green light before I send them.

Separately: 7 point-requests already submitted to Assembly today. This is the next wave — bigger, strategic, longer time-horizon.

</aside>

<aside> 💰

Why you care

• ~30+ hrs/week goes to human glue between Neos and external tools (PageAI, JotForm, our Python scripts, manual DRC uploads)
• Every tool we can't invoke via Neos API = drift between what Assembly ships and what OSDRI runs
• Every minute VALOR can't automate = a minute you or I do manually
• These 4 asks put Neos back as the single source of truth and unlock true 24/7 automation </aside>

📊 The 4 Asks (Tier 1 — ordered by impact)

<aside> 🔥

ASB-100 — Template Generation API · Critical (5/5)

😫 Your pain today:

OSDRI maintains custom Python scripts (fill_4138_*.py, build_4138_compare_on_form.py) that duplicate the Templates feature Assembly ships in admin UI. Every time you update a 4138 template, we have to update code too. Two sources of truth.

✨ What we want:

API endpoints to invoke Neos Templates programmatically:

• GET /v1/templates — list templates with schema
• POST /v1/templates/{id}/render — render with case data
• POST /v1/cases/{id}/documents/from-template — render + attach to case in one call

⏱️ You save: ~8 hrs/week of script maintenance + zero template drift risk

🤖 VALOR unlock: Auto-draft a 4138 the moment claim data is sufficient — no scheduled batch, no manual trigger

</aside>

<aside> 🧠

ASB-101 — AI Tag + AI Prompt Programmatic Control · Critical (5/5)

😫 Your pain today:

Neos has NeosAI Chat, AI Tags, and AI Prompts right there in admin UI — but no API to invoke them. EC workflow today:

1. Document arrives in Neos e-folder
2. Download, upload to PageAI (external)
3. Read PageAI analysis
4. Copy-paste key findings into Neos Note
5. Manually synthesize into Strategy tab

✨ What we want:

• POST /v1/ai/invoke — run any configured AI Prompt against case data
• POST /v1/cases/{id}/documents/{id}/analyze — apply AI Tags to a doc
• GET/POST/PATCH /v1/ai/tags and /v1/ai/prompts — programmatic control

⏱️ You save: ~10 hrs/week + kill PageAI subscription + kill JotForm dependency

🤖 VALOR unlock: AI analysis native in Neos — single source of truth, no external round-trips, no copy-paste

</aside>

<aside> ⚡

ASB-102 — Migrate Claims to DynamicForms · High (4/5) · 🔄 UPDATED

😫 Your pain today:

Claims are buried in UserCaseData. Every per-claim update = GET full case → mutate → PUT full case back. Slow. Race conditions with your UI edits. No per-claim webhook events.

✨ Updated ask (after deeper exploration of Neos today):

Neos already has a pattern called DynamicForms — uncapped, first-class custom entities tied to a case. It's already used for Line Item, Receipt, Medication, Medical Condition, Examinations, Dependent, etc. Cleaner ask: migrate Claims from UserCaseData to the DynamicForms pattern. Uses Assembly's existing architecture instead of inventing a new Claims API. Same outcome for us.

⏱️ You save: same as before — per-claim queries, faster updates, event-driven automation

🤖 VALOR unlock: React to individual claim events — when a statement arrives, auto-generate the 4138 for that specific claim (requires DynamicForms write+webhooks, tracked as ASB-116 + ASB-117 in Tier 2)

</aside>

<aside> 🔐

ASB-103 — OAuth2 / Service Account Authentication · High (4/5)

😫 Your pain today:

4-hour access tokens force re-auth every session. MCP server 401s when tokens expire mid-work. Credential rotation needs you + me + Assembly coordinating. Shared readonly/readwrite profiles = credential reuse across services (if one leaks, all leak).

✨ What we want:

• OAuth2 client_credentials grant
• Long-lived refresh tokens (24h access, 90-day refresh)
• Scoped access tokens (cases:read is different from cases:write)
• Per-service audit trail

⏱️ You save: ~2 hrs/week on re-auth + rotation headaches + MCP disruptions

🤖 VALOR unlock: True 24/7 automation that survives weekends, holidays, credential rotation, and individual staff turnover

</aside>

📈 Total Impact

*ASB-102 savings show up as VALOR time (instant 4138 generation on claim events) rather than direct Kailey hours, but compounds across every case.

🔮 What comes next (after Tier 1 lands)

Full detail: Strategic API Asks — Awaiting Kailey Review

<aside> 📦

Tier 2 — submit after Tier 1 response tempo is known:

• Bulk Case Operations — fleet-wide sweeps in one API call
• Activity Feed Writes — VALOR posts synthesis directly into case timeline
• Native DRC Portal + VA Lighthouse — kill manual uploads (likely out of Assembly scope, worth asking) </aside>

<aside> 🧪

Tier 3 brainstorm — 9 more asks I want to run by you for pain validation:

✅ What I need from you