| Required operating inputs | - Approved matter categories, jurisdiction, urgent-date, safety, and conflict-preparation rules
- The intake record and authorized person who decides consultation routing and exceptions
- Audience question, service scope, proof source, approved claims, page owner, and accessible content
- Conversion path, required intake context, source attribution, analytics consent, and failure fallback
|
|---|
| Release acceptance test | Run one de-identified or synthetic prospective-matter inquiry through the configured path and verify that a visitor can understand fit, verify the stated basis, complete the intended next step, and arrive in the correct record with source context. Record the expected state, actual state, exception owner, and corrective action before release. |
|---|
| Stop condition | Do not release or continue the automated path when the inquiry requires legal advice, conflict judgment, emergency direction, matter acceptance, or handling outside the firm's approved intake scope, or when the service owner, factual basis, accessible path, next-step capacity, data purpose, or destination record is undefined. Preserve the record and route the case to the named human owner. |
|---|
| Human boundary | Lawyers and authorized firm staff retain conflict decisions, legal judgment, advice, deadlines, matter fit, representation, scope, and acceptance. The configured system may collect approved intake context and coordinate a consultation but cannot make a legal decision. |
|---|