Agent Architecture and Design

NCP-AAI · 31 questions

• A city 311 portal redesigns its resident chat so callers can see what the agent is about to do before it files a service request. Which UI pattern best supports that goal?
• A permitting office wants counter staff to watch an agent draft checklist items while a homeowner sees only a simplified status strip. What architecture choice best protects that dual-audience design?
• A library chatbot adds quick-reply chips for hours, holds, and fine disputes instead of relying on free-text alone. When does that structured UI affordance most improve human–agent clarity?
• A transit authority mobile app shows the agent's next planned tool call as a readable step before booking a paratransit ride. What design principle does that preview primarily support?
• A county fraud-review agent must alternate between reasoning about a benefits claim and calling eligibility APIs. Which approach best fits that tool-using workflow?
• A water-utility outage bot keeps looping Thought→Action→Observation until it can cite a work-order ID. Which ReAct step is primarily responsible for grounding the agent's advice in the tool result?
• Emergency-management planners compare a ReAct-style agent to a static FAQ decision tree for storm-debris pickup guidance. When is the reason–act framework the better architectural choice?
• A clerk's agenda agent proposes actions only after writing an intermediate rationale the auditor can later read. Why make those reasoning traces an architectural requirement?
• A permitting planner agent must hand a parcel ID and zoning flags to a fee-calculation agent without free-form chat noise. What communication design best supports that handoff?
• Public-health case agents share only de-identified encounter codes when asking a scheduling agent for clinic slots. What does that protocol choice primarily enforce?
• Two 311 triage agents disagree on priority and the architecture needs a defined way to escalate. Which collaboration pattern element is most important to add?
• A transit disruptions agent must notify both a rider-notification agent and an ops-dashboard agent when delays occur. Which communication style best fits that citywide event fan-out?
• A multi-turn housing-intake chat must remember the current session's income answers without permanently storing them. Which memory design matches that requirement?
• A parks reservation agent stores recurring group preferences across seasons but expires one-off picnic details. What memory policy best describes that architecture?
• Court-clerk assistants lose case context when the token window rolls, so architects add episodic memory retrieval. What problem does that architectural layer primarily solve?
• A benefits agent wrongly recalls last year's household size because long-term memory lacked version stamps. What memory design change best prevents that class of error?
• A city AI pilot coordinates intake, eligibility, and notification agents for rental-assistance applications. Which orchestration pattern best fits an accountable end-to-end civic workflow?
• Snow-route planning uses a planner agent plus validator and dispatcher agents that share a task board. What does the shared workflow state primarily enable?
• Permit review stalls when two specialist agents wait on each other indefinitely. What coordination design most directly prevents that deadlock?
• A school-district IEP assistant routes speech, OT, and admin agents with clear ownership of each step. Why is role specialization important in that orchestration?
• Business-license renewal needs a chained sequence: validate entity → check taxes → generate invoice draft. Which architectural approach best implements that ordered municipal process?
• Code-enforcement triage uses a logic tree for severity then a prompt chain for remedy letters. What does combining those techniques provide?
• A grant-writing helper must keep workflow state across days so staff can resume mid-draft. Which orchestration capability is essential?
• Assessor appeal prep must branch if comparable sales are missing versus if comps exist. How should stateful orchestration handle that?
• Zoning agents must reason over parcel–use–ordinance relationships. When is a knowledge graph a better architectural fit than flat document RAG alone?
• A public-works outage agent must answer which hydrants lose pressure when a water main is isolated, using links among mains, hydrants, and open work orders. Why should the architecture integrate a knowledge graph rather than flat document retrieval alone?
• A social-services agent must spot when a household is enrolled in two programs that conflict under city policy. What knowledge-graph design choice best supports that relational conflict check?
• City attorneys want a research agent to follow ordinance citation links for precedent lookup without inventing case law. How should knowledge-graph integration support that relational reasoning?
• Summer tourism spikes 311 volume. Architects need more agent capacity without redesigning every tool integration. Which adaptability and scalability approach best fits?
• Public works launches a new stormwater fee program and needs a specialist agent in the existing multi-agent stack. What architectural adaptability pattern should the team use?
• County IT fears a single monolithic tax-season agent will cascade failures across filing, payment, and FAQ tasks. Which architecture best improves failure isolation and scalability?