GAP-01
Product
First-interaction disclosure is drafted but not released
Approve the copy, ship it before the first message, and retain desktop and mobile release evidence.
P0 gap
Owner · Product
Fictional sample · not customer work
NovaChat buyer evidence delivery.
A representative delivery for one customer-support workflow. It demonstrates the format, evidence discipline, and decision boundaries—not complete coverage of EU law, a legal opinion, certification, or compliance conclusion.
Delivery cover
One frozen scope. Every artifact source-linked.
- Product
- NovaChat Customer Assistant
- Company
- Northstar Support Labs · fictional
- Reviewed release
- Web release 3.8.0
- EU exposure
- EU enterprise customers
- Review date
- 31 July 2026
- Frozen scope
- One customer-support workflow across six product surfaces
01 · Role and scope map
Roles stated as assumptions, not verdicts.
- Customer-facing provider
- Northstar presents NovaChat under its own name and controls the reviewed assistant experience.
- Working operational assumption
- Enterprise deployer
- The enterprise customer configures the support workflow and remains responsible for its deployment context.
- Confirm per customer setup
- Model provider
- A third-party model API supplies generation; its marking capability and contract terms remain evidence inputs.
- Vendor evidence required
- Open role decision
- Qualified counsel must confirm the final provider and deployer allocation before an external legal claim is approved.
- Counsel confirmation
- 01
Role and scope map
Product facts, reviewed workflow, operating roles, markets, assumptions, and counsel questions.
SYS-01
- 02
Surface register
Six interaction, output, export, help, and handoff surfaces tied to an owner and status.
SRF-01
- 03
Disclosure pack
Exact proposed copy, trigger, placement, timing, persistence, and approval path.
DSP-01
- 04
Marking test record
Five sample outputs checked across the response, copy, and transcript-export paths.
TST-04
- 05
Gap and decision register
Observed gaps separated into product, engineering, evidence, and counsel decisions.
GAP-02
- 06
Implementation tickets
P0 and P1 tickets with objective acceptance tests and proof to retain after release.
FP-101
- 07
Evidence index
Versioned proof references, owners, approval state, storage location, and review date.
EV-006
- 08
Buyer trust brief
Three-page answer set based only on confirmed product facts and visible limitations.
TRUST-01
- 09
Counsel handoff
The legal interpretation decisions isolated from the product and evidence work.
LGL-03
05 · Gap and decision register
Product work and legal decisions stay separate.
Each unresolved item has a type, owner, action, and visible decision boundary.
GAP-02
Engineering
Transcript marking method is not evidenced
Select the method, test five fresh exports, and record detector version, results, and limitations.
P0 gap
Owner · Platform
DEC-03
Counsel
Role allocation for the export workflow remains unresolved
Confirm the provider and deployer responsibilities before approving the buyer-facing answer.
Decision required
Owner · Counsel
02 · Surface register
The real workflow, surface by surface.
Status describes the evidence available in this fictional review. It does not declare a legal conclusion.
SRF-01
Assistant entry
AI assistant opens before the customer submits a first message.
Owner · Product
Copy ready
SRF-02
Conversation header
Assistant identity remains visible throughout the active session.
Owner · Product
Evidence captured
SRF-03
Generated response
Response text can be copied without an attached provenance field.
Owner · Platform
Engineering decision
SRF-04
Transcript export
Downloaded PDF contains disclosure text but no detectable metadata.
Owner · Platform
P0 gap
SRF-05
Human handoff
Specialist takeover is visible and timestamped in the transcript.
Owner · Support
Evidence captured
SRF-06
Help centre
Product explanation exists but is not linked from the live assistant.
Owner · Content
P1 improvement
03 · Disclosure pack
Ready for product and counsel approval.
SRF-01 · Proposed copy
“You’re chatting with an AI assistant. Responses may be inaccurate. A support specialist can review this conversation.”
- Placement
- Above the message composer before the first submission.
- Persistence
- The short AI label remains in the conversation header during the session.
- Approval
- Product owner and qualified counsel
- Acceptance evidence
- Desktop and mobile screenshots, release ID, approved copy, and approval timestamp.
04 · Marking test record
Five outputs. Three delivery paths.
A missing mark stays a gap. The report never upgrades an unverified claim into evidence.
In-product response
2 samples
Method not evidenced
Confirm provider marking method and retain a detector result.
Copied text
1 sample
No mark detected
Document technical feasibility and selected implementation.
Transcript PDF
2 samples
Visible disclosure only
Add and verify the agreed machine-readable signal.
06 · Implementation tickets
The missing proof becomes buildable work.
FP-101P0
Disclose the assistant before first interaction
- Acceptance test
- New desktop and mobile sessions show approved copy before the composer accepts a first message.
- Evidence retained
- Release ID, two screenshots, copy approval, and verification timestamp.
FP-102P0
Select and verify the transcript marking method
- Acceptance test
- The agreed detector identifies the signal in five fresh transcript exports, with limitations recorded.
- Evidence retained
- Method note, five output hashes, detector version, results, and reviewer.
FP-103P1
Link the live assistant to the transparency explanation
- Acceptance test
- The conversation header exposes a keyboard-accessible route to the current help-centre explanation.
- Evidence retained
- Desktop/mobile recording, URL, release ID, and accessibility check.
07 · Evidence index
Claims stay attached to proof.
Customers are informed before first interaction
Pending evidence: Pending FP-101 release evidence
Owner · Product · Review · At release
AI identity remains available during the session
Verified evidence: SRF-02 desktop and mobile capture
Owner · Product · Review · Quarterly
Human takeover is visible in the transcript
Verified evidence: SRF-05 handoff recording and transcript
Owner · Support · Review · Quarterly
Transcript output carries a tested machine-readable signal
Missing evidence: Not yet evidenced — FP-102 open
Owner · Platform · Review · At release
08–09 · Buyer trust brief and counsel handoff
Facts for the buyer. Decisions for counsel.
Buyer trust brief
NovaChat identifies the AI assistant throughout the active session. First-interaction copy and transcript marking remain open implementation items and are not represented as completed controls.
Counsel handoff
- Question 1: Confirm whether Northstar holds provider, deployer, or combined roles for each reviewed surface.
- Question 2: Approve the first-interaction disclosure copy and the conditions for any 'obvious interaction' position.
- Question 3: Confirm whether the selected marking method and documented limitations are appropriate for the scoped output paths.
Delivery clock
Two French business days to first release.
The clock starts after verified payment, complete intake, named ownership, walkthrough access, and the agreed evidence. Customer-caused blocking delays pause the recorded window.
- START
Verify start conditions
Confirm payment, one workflow, six surfaces, owners, access, and agreed evidence.
- DAY 1
Inspect the live surfaces
Capture current behaviour and test five representative outputs against the frozen scope.
- DAY 2
Draft and human-review
Create all nine source-linked artifacts, verify every released claim, and issue the first release.
- REVIEW
Customer factual review
Give the named approver three French business days to approve or submit one consolidated correction list.
- HANDOFF
Correct and close
Apply the included factual correction round, export the release archive, and assign every open decision.
Delivery guarantee
We guarantee the work—not a regulator’s decision.
When the agreed intake is complete, FiftyProof delivers the first human-reviewed release within two French business days, excluding weekends and French public holidays. If we miss for a reason within our control, FiftyProof refunds the sprint fee. Customer review, one correction round, and handoff follow the first release.
Product facts remain customer-approved. Legal interpretation remains with qualified counsel.