Source
Invoice, lot, recipe, policy, and provider references retain their identity.
Attached or unavailableTrust
Show the source.
Show the decision.
Trust comes from what the system can show: the source, the calculation, the decision, and the receipt.
Evidence ledger
Six links that should never disappear.
Calculation
Deterministic math is separated from an estimated business interpretation.
Deterministic or estimatedAuthority
A named manager can approve, edit, reject, or ignore a consequential action.
Needs review or manager decidedDecision
Before and after values, limits, actor, and time are recorded.
Session receiptReceipt
Approval and audit references stay linked to the source context.
Created or failed safelyBoundary
The iPhone talks to Dynamic.ly Backend; provider authority and disabled writes remain explicit.
Read-first and backend-ownedRecommendation REC-11902
Lower Salmon Bowl for 5–7 PM
Pending reviewCurrent$18.00Deterministic
Proposed$15.50Deterministic
Margin floor$14.20Policy boundary
Quantity cap40Manager limit
Why now
18 lb salmon expires tomorrow while the 5–7 PM window is slower than the scenario baseline.
82% confidence
Estimated impact
$420 revenue recovery · $96 waste avoided · 18 bps margin lift
Estimated
Sources
Ocean Fresh invoice · Salmon lot · Square order velocity
3 attached
Review decisionEdit or reject
Source and calculation
The recommendation is inspectable before the decision.
Price, floor, cap, window, sources, confidence, and estimated impact remain visible on one pending action.
Pending manager review · impact estimatedApproved by Elena · Owner
Decision recorded
Session receiptBefore$18.00
After$15.50
Window5–7 PM
Cap40
Approval
APR-8841
Created
Audit event
AUD-20487
Saved
Estimated outcome
$420 recovery · $96 waste avoided
Not measured
View audit eventDone
Authority and receipt
A decision receipt is not an outcome claim.
The example records who approved what and which audit reference was created. The projected business impact remains unmeasured.
Session receipt · no automatic publicationAudit events
What happened and what proves it?
4 example eventsAudit EventsSync Jobs
Events4
Failed jobs1
Queued jobs2
Elena approved Salmon Bowl action
AUD-20487 · APR-8841 · 3:45 PM
Approved
System parsed Ocean Fresh invoice
AUD-20486 · INV-784512 · 3:31 PM
Parsed
Marco corrected vendor alias
AUD-20485 · ING-SALMON-001 · 3:20 PM
Edited
Inventory sync attempt failed
AUD-20484 · JOB-55210 · 3:02 PM
Failed safely
View sync jobs
Audit
Success, edits, and safe failures share one evidence vocabulary.
Actor, time, reference, and state remain readable. An integration failure is shown as a failure and never upgraded to success.
Example evidence architectureSource: Dynamic.ly Backend · Sandbox
Square connection
ConnectedLocationDowntown
MappingReviewed
ScopeMerchant profile read
Imported Square locations
Imported location
100 Demo Avenue, Demo City, NY 10001
Mapped
Provider authority
OAuth and credentials remain on Dynamic.ly Backend
Backend-owned
Write capability
Catalog, order, inventory, and payment write access is not enabled
Disabled
Sync locationsDisconnect
Integration boundary
Provider authority stays on the backend.
The connection surface distinguishes an imported location from write capability. Square writeback is not represented.
Sandbox example · backend-owned tokenEvidence state is written in words.
Estimated · Evidence partial · Confirmed · Needs review · Blocked · Stale
Color supports these labels; it never replaces them.