Screen 05[BUILT]

Authorized Behavior

Company XYZ's authorized reviewer does not approve the technical implementation. They authorize the business or policy outcome — the — that candidate 3.2.0 will be tested against. LoanCore owns the candidate implementation; Company XYZ's authorized domain reviewer owns the Authorized Expected Behavior.

Priya Ramanathan

Enterprise AI decision accountability

Company XYZ decision accountability · LoanCore Underwriting 3.2.0Customer Support · Case VR-NS-001— Representative lending boundary case

ACCOUNT1–3→
VERIFY4–7→
DEFEND8–9

VERIFYScreen 05

Question: Who has the authority to say what should happen in this decision?
Answer: Company XYZ's authorized domain reviewer—not LoanCore and not Notary AI—defines the acceptable business outcome under the applicable policy.
Output: A versioned, attributable authorization of expected behavior.

Responsibility model

LoanCore: Owns the candidate implementation.
Company XYZ: Owns acceptable business behavior and the release decision.
Notary AI: Preserves evidence and verifies the candidate under the recorded scope.

Decision case

Bereavement refund misstatement (NorthStar bot)

Customer Support · evidence E3

Captured

TOLD CUSTOMER: 'apply within 90 days for refund'

Response asserted policy; retrieval returned no matching document

[BUILT]fail-closed eligibilityevidence sufficient

Authority & policy provenance

reviewer: VP Customer Experience — Jordan Ochoa
authority_scope: Company XYZ customer-facing support responses
decision_family: Customer Support
policy: Customer Communications Standard 2.0
policy_version: 2026-03
effective_period: 2026-03-01 → open
expected_result: REFUSE_AND_HANDOFF
signature_status: Recorded append-only · signed oversight trail planned

Reviewer disposition

Approve expected behavior

Authorizes the expected result the candidate version will be tested against.

Request more context

Sends the case back for additional decision-time evidence.

Dismiss candidate

Records that this case does not warrant a Scenario.

Accept risk

Documents an accepted exposure with rationale and an owner.

Preserve next occurrence

Instructs capture to retain full evidence the next time this pattern occurs.

Create a scoped suppression

Narrow, time-bounded suppression with a recorded reason.

Escalate as an Incident

The only way a case becomes an Incident is an explicit reviewer promotion.

Applies to

Scenario family — all policy-bearing support responses

Rationale (required)Notes (append-only)

Screen anatomy

What this screen proves

Authorized Expected Behavior always carries authority provenance: who approved it, under which policy and version, for which scope, and for how long. Notary AI never decides what the acceptable outcome should be.

Why it matters

This is the business-authority step that makes a verification result meaningful. Without an authorized expected result, a passing test only proves the software did something — not that it did the right thing.

Built or Planned

Built capability. Authorized review and fail-closed eligibility exist today. A signed human-oversight trail is planned.

Important boundary

The bridge re-derives evidence sufficiency from the sealed record rather than trusting the caller, and preserves the . Rationale and notes are append-only.

Related requirements

The expected outcome is now authorized. Notary AI can compare LoanCore 3.2.0 against it under preserved conditions.

Candidate Verification →