You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 98083c0
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: examples/perplexity-demo/README.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,3 +129,19 @@ Use the maintained [connection verification evidence rules](https://github.com/v
129
129
Keep private titles and raw payloads outside Git/Linear. A successful server access log with no saved demo result is a failed consumer-delivery attempt, not end-to-end success. Preserve its receipt and cost; a fresh charged attempt requires an explicit operator decision rather than automatic replacement. Compare saved content to what the browser actually displays, and retain failure attempts rather than relabelling them. A grant's chain finalization and consumer acknowledgement are separate observations.
130
130
131
131
[Motel composition guidance](https://github.com/vana-com/unity-surfaces/blob/a87843f90b9b570ce493e769d348b1a869a9ebae/.agents/skills/us-verify-with-motel/SKILL.md) is optional diagnosis. Its existing exporter is Desktop-specific and does not capture this example. Use existing request/payment/save evidence first; add app-owned, metadata-only probes only for a concrete unresolved failure. Do not launch Desktop, upgrade Personal Server or build an observability programme for this milestone.
132
+
133
+
## Iterate through the same grant — BUI-932
134
+
135
+
After the first result is saved, displayed and acknowledged, **Read latest** performs a fresh SDK read using the owner/app/network/grant/server binding retained privately by the backend. It accepts no grant, server, scope or request overrides from the browser and does not reopen the completed Direct request. The backend rechecks the live grant and owner-bound server. If access has expired or been revoked, the saved list stays visible and **Review access again** is available. Funding and transient server errors remain read/funding problems.
136
+
137
+
Every deliberately fresh read can incur the current capped test-VANA fee. Earlier successful receipts remain in private history; a failed or uncertain fresh attempt reuses its own receipt instead of authorizing another fee. A delivered body that has not been decoded/saved, or a saved response lost before the browser received it, is recovered before another paid read. Acknowledgement follows rendering of the recovered/new revision. The BUI-931 ledger is adopted only when its saved, acknowledged revision matches its retained received body; uncertain legacy payments are not relabelled as successful.
138
+
139
+
To prove a connector change:
140
+
141
+
1. Record one real conversation's stable ID and current title in private evidence. Keep the same app, grant, owner, network and conversations scope.
142
+
2. In an isolated, unpublished checkout of the **same connector version**, edit `connectors/perplexity/parsers.ts` so `conversationRecord` prefixes only that record's returned title with `CLI edit — `. Keep its ID and scope unchanged and respect the title's 500-character bound. Do not edit exported JSON, the app's saved list or synthetic fixtures.
143
+
3. Rerun `vana connect perplexity --from /path/to/edited/data-connectors --streams conversations --network moksha --yes --ipc`. The selected 0.1.1 conversations-only path emits its listed conversations on every run; do not clear cursors, bypass refresh limits or import messages merely to force an update. Keep the CLI receipt and prove that the actual emitted record contains the changed title.
144
+
4. Verify ingestion and serving of the changed payload on the same owner-bound server. A new version number alone is insufficient. Record any manual setup/copy assistance explicitly; a development-wallet copy is not automatic CLI delivery.
145
+
5. After the original Direct request is complete, click **Read latest**. Prove a new saved revision with the changed title in the real demo, using the same grant, then observe acknowledgement after rendering. Record the current fee, preserved previous receipts and total authorized amount. Refresh the page to verify the saved result survives.
146
+
147
+
The local connector edit is an acceptance experiment, not a connector publication or upstream feature. Keep its private record ID and real data outside this repository. Mainnet, native per-account delivery, publishing, review and the public Registry remain separate.
0 commit comments