Applications and Integration
CCDV-F · 66 questions
- A city product owner is starting a permitting FAQ on Claude. What should happen before API design begins?
- A county health clinic requires kiosks that still guide residents when the WAN drops. How should that shape Claude integration?
- A transit authority wants overnight ridership analytics summarized and cares more about cost than sub-second answers. What should developers prioritize?
- A court clerk requires that Claude never invent docket numbers missing from the case system. Which requirement class does that encode?
- A housing authority scopes a Claude chat assistant for applicants. Besides the model backend, what must the requirements include?
- A water utility mandates that Claude applications run only in the utility's approved cloud region. How should developers treat that?
- A school district needs Claude to summarize IEPs with different visibility for teachers versus admins. What must requirements capture?
- A city IT PMO is placing a Claude 311 bot under the municipal SDLC. Which life-cycle thinking is appropriate?
- A county must promote a new Claude prompt version from staging to production. What gate should apply?
- A transit team is about to launch a Claude rider assistant that replaces a legacy FAQ bot. What life-cycle step should they plan?
- A public-health app team wants to stay safe across Claude model releases. Which life-cycle practice fits?
- A parks department wants CLAUDE.md and tool schemas managed like other IT assets. How should they classify them?
- A court IT board will allow production Claude access to sealed case metadata only after which gate?
- A 311 backend must show progressive reply text while tools fetch ticket status. Which Messages API capability fits?
- A permitting app needs Claude to read uploaded site-plan images for checklist hints. Which API capability should be enabled?
- A county analytics job must summarize 8000 inspection reports overnight with cost as the main driver. Which API approach fits?
- A transit agent must reason through complex multi-agency detour planning before answering. Which Messages API feature helps?
- A library catalog assistant repeats a large static collection-policy preamble on almost every call. How should developers optimize?
- A housing portal must call Claude through an approved third-party cloud marketplace endpoint. What does that imply for developers?
- A water-utility agent calls a tool and must continue the Claude conversation with that result. Where do tool results go?
- A school-district bot must detect when Claude truncates IEP summaries. Which API handling practice fits?
- A city open-data chatbot must answer questions about large municipal datasets. How should Claude reach the data?
- An emergency dashboard needs Claude to draft live briefings during an active incident. Which API mode fits?
- A clerk app must keep court-assistant instructions and conversation turns correctly structured for Claude. What practice fits?
- A parks mobile app wants Claude to flag hazard indicators in trail photos from field staff. Which capability is required?
- A municipal finance bot reuses the same chart-of-accounts instructions across departments. Which caching practice fits?
- A county GIS assistant must show progressive map-description text while tools fetch parcel attributes. Which approach fits?
- A city team is changing Claude tool schemas for a civic integration. What engineering practice should they apply?
- A 311 service backend calls Claude over REST and must keep request threads responsive. Which practice fits?
- A permitting API returns JSON that Claude tools must consume. What engineering practice fits?
- A transit squad's Claude prompt helper has grown into one untestable file. What should they do?
- A water-utility team deploys Claude tool-argument builders. What should the CI pipeline do before release?
- A housing team must operate Claude beside a case-management API. How should they document failures?
- A school-district engineer is wiring production calls to Claude's REST API. Which client approach fits?
- A library IT review finds a PR that hard-codes secrets into Claude client constructors. What should happen?
- A court app mixes Claude orchestration logic inside UI controllers. What design change improves ownership?
- A parks team wants to introduce a new Claude tool to field staff carefully. Which delivery practice fits?
- A county open-data project will expose internal services for Claude to call. What contract practice fits?
- A public-health backend hits transient Claude HTTP 429 responses. Which resilience practice fits?
- A city devops group wants reproducible Claude client behavior across deploys. What dependency practice fits?
- A housing microservice needs operations visibility into Claude traffic. Which practice fits?
- A transit team's prompts are embedded inside UI code. What large-scale refactor fits?
- A city compares the same permitting instructions in Claude Code versus a Messages API app. What design insight matters?
- A 311 product must keep the resident assistant from advising on criminal complaints. What design control fits?
- A court filing assistant must fill party and case fields for downstream systems. Which output design fits?
- A housing counseling chat runs long and context grows stale. What session-hygiene design fits?
- A library Desktop Claude workspace needs local catalog plugins that a public web FAQ bot should not load. What design choice fits?
- A school district drafts curriculum in a Claude.ai project space but needs a production grading helper with audit trails. Which surface choice fits?
- A water utility SCADA-adjacent assistant must not invent free-text plant control commands. What schema design fits?
- A parks app must keep system trail policy separate from volunteer-uploaded trail notes. What content design fits?
- A county clerk wants the same tool names and descriptions on Desktop Claude bots and API bots. What design practice fits?
- A transit rider app must avoid inventing arrival times beyond published GTFS. What content-boundary design fits?
- A public-health intake bot must feed symptom checklist fields into an EHR API. Which output design fits?
- Municipal grant writers on Claude Desktop need local folder draft plugins managed carefully. What practice fits?
- A housing caseworker finishes eligibility chat and starts a payment-dispute chat with the same resident. What session design fits?
- A city legal-aide chatbot drafts plain-language answers residents might treat as official counsel. What content-boundary design fits?
- An emergency PIO assistant must produce press-release fields under time pressure. What output design fits?
- A county open-data team writes ETL scripts in Claude Code and serves the public with a separate API bot. What design separation fits?
- A parks volunteer scheduler gets JSON slot suggestions from Claude before committing shifts. What closing design step fits?
- A city repo must stop silent default model upgrades from changing permitting answers. What configuration practice fits?
- A 311 team must control production CLAUDE.md edits that change system prompts. What change-control practice fits?
- A transit monorepo needs shared Claude guidance plus service-specific rules. What configuration approach fits?
- A water utility wants approved Claude Code plugins tracked like other software. What configuration practice fits?
- A school district student-data assistant must allow only org-approved tools. Where should that constraint live?
- A housing authority needs to roll back bad eligibility-rule prompt deploys. What configuration practice fits?
- A court IT team must audit model pins, prompts, and plugins together. What configuration discipline fits?