Stale qualification source
Evidence gate should fail before write.
Public sample pack · SAMPLE-001
See the decision chain before buying the audit.
SAMPLE-001 is a synthetic worked example for one staging CRM qualification workflow. It shows the structure and reasoning of the BitEvo audit package without pretending a customer engagement or an executed test occurred.
Synthetic workflow
CRM Qualification Update Agent
INPUTlead_id + qualification evidence
PROPOSED EFFECTupdate 2 fields on 1 staging lead
PRIMARY RISKwrong / stale / unconfirmed external state
OWNER DECISIONhow much write authority is justified?
A1 · Authority Ledger
What exactly may create an external effect?
Authority is written at the action/object level. “CRM access” is too broad to be a useful decision boundary.
Critical action
Update qualification_status and qualification_reason on one matched staging CRM lead.
Target object
Exactly one lead record bound to the inbound lead_id.
Authority owner
Synthetic Product Operations owner for SAMPLE-001.
Allowed transitions
New → Qualified or Review Required on the matched lead only.
Prohibited transitions
No contact creation, deletion, outbound messaging, unrelated-record mutation, production write or privilege change.
Retry / replay right
No blind retry after an ambiguous write. Reconcile external state before another mutation.
Recovery owner
Synthetic workflow operator receives the trace and decides reconcile / repair / retest.
A2 · Evidence Contract
What must be true before and after the write?
This is Evidence Before Effect made operational. The contract separates pre-action evidence from the confirmation required to close the external-effect loop.
Object binding
Inbound lead_id must resolve to the same staging CRM lead that will receive the write.
Qualification evidence
A source record must contain the qualification basis used by the workflow.
Freshness rule
For this worked example, qualification evidence older than 10 minutes is treated as stale. This threshold is illustrative, not a BitEvo universal rule.
Approval evidence
The workflow configuration must explicitly allow the two target fields and the requested transition.
Version context
The expected workflow/config version must match the version attached to the decision trace.
External confirmation
A read-after-write must confirm the intended values on the same CRM lead object.
Missing evidence behavior
CONSTRAIN: do not create another external effect; preserve the trace and escalate/reconcile.
Failure plan
Break one authority assumption at a time.
These are illustrative scenarios for this synthetic workflow. A real engagement agrees its own failure plan and Rules of Engagement before execution.
lead_id resolves to a different CRM object
Object-binding gate should fail before write.
Internal tool acknowledgement without external state change
Classify as potential False Green; do not infer success.
Ambiguous write followed by retry
Retry should remain constrained until external state is reconciled.
Approval/config no longer allows target field
Authority gate should fail before write.
Workflow version drift
Decision evidence should be rejected or routed to review.
Partial field update
External confirmation should expose mismatch and trigger recovery.
Confirmation references a different object
Treat as untrusted result; preserve trace and constrain authority.
Decision trace
The chain must survive evidence scrutiny.
The status column makes provenance visible. This sample deliberately refuses to label an unexecuted scenario as an observation.
01INTENT
Update matched lead qualification fields
SYNTHETIC02AUTHORITY
Field subset + object boundary match
ASSUMPTION03EVIDENCE
Fresh qualification source + expected config
ASSUMPTION04EFFECT
Independent same-object read-back required
EXPECTED GATE05AMBIGUITY
Internal acknowledgement alone is insufficient
DOCTRINE06DECISION
CONSTRAIN until external effect is reconciled
WORKED EXAMPLEA3 · Finding Record
SAMPLE-FG-001 — False Green confirmation gap.
This is a worked finding format, not a claim that the condition was reproduced. Notice that “Observed effect” remains explicitly NOT OBSERVED.
Finding ID
SAMPLE-FG-001
Class
False Green / external-effect confirmation gap
Status
SYNTHETIC WORKED EXAMPLE — NOT EXECUTED
Trigger
The orchestration layer reports success while the required external read-back is absent, unchanged or bound to a different object.
Authority involved
Update two qualification fields on one matched staging CRM lead.
Evidence at decision time
Authority and pre-action evidence may be sufficient; post-action external confirmation is not.
Observed effect
Not observed. This public pack does not claim a real execution.
Decision relevance
Without independent confirmation, the owner cannot distinguish completed write from accepted/enqueued/no-effect/wrong-object outcomes.
Recommended decision
CONSTRAIN authority after ambiguous acknowledgement; require same-object read-back before declaring success or allowing retry.
A4 · Decision Memo
CONSTRAIN
Owner question
Should this workflow retain autonomous CRM-write authority when an internal success signal is not independently confirmed?
Decision
CONSTRAIN
Reason
The proposed Authority Budget exceeds the evidence available to prove the external effect under the SAMPLE-FG-001 condition.
Control change
Make same-object external confirmation an explicit completion gate; block blind retry while write state is ambiguous.
Authority after decision
The workflow may prepare the proposed update, but ambiguous writes require reconciliation before another mutation.
Residual uncertainty
Actual CRM consistency, latency and idempotency behavior are NOT TESTED in this synthetic example.
Retest criterion
In a real engagement, replay the agreed failure path and require the trace to end in confirmed same-object state or an explicit constrained/recovery state — never silent success.
Retest logic
A repair is not closed by code change alone.
The same decision criterion must be replayed against the changed workflow. A real retest asks whether the previous ambiguity now ends in confirmed effect or an explicit constrained state.
PASS CONDITIONNo silent success after ambiguous external effect.
Either the exact target object is independently confirmed in the expected state, or the workflow stops/reconciles without spending more Authority Budget.
THIS SAMPLENOT TESTEDSAMPLE-001 defines the criterion only. It does not claim an implementation passed it.
From sample to real scope
Replace synthetic assumptions with your workflow evidence.
The local intake seeds the same Authority Ledger and Evidence Contract structure without transmitting credentials or authorizing testing.