Firm lane
Conflict check
Kind: Fixed templates and rules — no model call.
Availability
ShippedLive on this deployment: it needs nothing more to run.
- Door
/admin/matter/[id] · /api/admin/conflict-check- Unlocks with
- A law firm's staff session, signed in with its second factor.
Every status follows one rule from this deployment's own configuration: a capability is marked shipped only when everything it needs is in place.
What it does
Records a matter's conflict check from a fixed questionnaire, and only an attorney with approval authority records the firm's determination.
Keep in mind
An unknown or missing answer keeps the check open; it is never a clearance.
What it refuses
| Answer | HTTP | Meaning |
|---|---|---|
forbidden | 403 | The session is not the firm's staff for this matter; the door reads nothing further. |
mfa-required | — | A staff session needs its second factor before any staff door opens: 401 to verify it, 403 to set one up. |
unavailable | 503 | The record could not be read: the door answers unavailable, never an empty list or a zero. |
- Answer
forbidden- HTTP
- 403
- Meaning
- The session is not the firm's staff for this matter; the door reads nothing further.
- Answer
mfa-required- HTTP
- —
- Meaning
- A staff session needs its second factor before any staff door opens: 401 to verify it, 403 to set one up.
- Answer
unavailable- HTTP
- 503
- Meaning
- The record could not be read: the door answers unavailable, never an empty list or a zero.
What can leave EstateDraft
The registry declares no action of this capability that reaches outside EstateDraft.
Evidence
src/lib/conflicts/determination.test.tssrc/app/api/admin/conflict-check/route.test.tssrc/lib/db/phase4a-migration.test.tssrc/lib/conflicts/determination.tssrc/components/ConflictCheck.tsx
Reviewed: