Carry

Every scenario DeepQA drove in the browser, in plan order, with the 28 screenshots it captured along the way. A passing scenario is evidence too.

1. S1

   Reset demo state

   3 steps, 2 screenshots

   highpass

   

   

   • Navigated to /dashboard showing default Memories (e.g. diet namespace) and no receipts.
   • Clicked the Reset demo button and verified the dashboard displays the default memory state with no user-captured facts or receipts.
   • The application runs on Sui testnet as confirmed by the network parameter and policy links.
   • Clicking Reset demo resets demo state cleanly to the default baseline without errors.
2. S2

   Prevent saving empty facts

   4 steps, 2 screenshots

   highpass

   

   

   • Navigated to Chat A, verified 'Diet' was selected, and confirmed the 'Save' button is disabled when the fact input is empty or whitespace-only.
   • The application disables the 'Save' button when the 'Enter a fact to remember…' input is blank or whitespace, preventing empty facts from being submitted.
3. S3

   Capture a valid fact into a namespace

   4 steps, 3 screenshots

   highfail

   

   

   

   • Navigated to Chat A where the fact capture form shows namespace selector and text input.
   • Selected namespace 'diet' and typed 'I am allergic to peanuts' into the fact input field, enabling the Save button.
   • Navigated to Chat A at https://www.usecarry.xyz/chat-a.
   • Selected namespace 'diet' from the dropdown and entered 'I am allergic to peanuts' into the fact input field.
   • Clicked 'Save' button, which changed to 'Saving…' and disabled state.
   • The fact save operation remained perpetually in 'Saving…' disabled state without saving the fact or updating the UI memory list.
4. S4

   Agent A retrieves permitted memory

   3 steps, 2 screenshots

   highfail

   

   

   • Navigated to Chat A on Sui testnet.
   • Confirmed network parameter testnet is present in URL and Attack lab referenced live testnet policy on Sui testnet.
   • Navigated to Chat A (/chat-a).
   • Submitted the query 'What am I allergic to?' in the 'Ask Agent A' textbox.
   • Agent A responded with 'I cannot access the memory needed to answer that — it was not authorized for this agent.' and receipt 'No memory used for this answer.' instead of retrieving the stored allergy fact ('peanuts').
   • Also tested clicking the suggested prompt 'Am I allergic to anything?', which yielded the identical rejection 'I cannot access the memory needed to answer that — it was not authorized for this agent.'.
5. S5

   Revoke Agent A access

   3 steps, 2 screenshots

   highpass

   

   

   • Navigated to the Access control page displaying the Agent x namespace policy matrix.
   • Clicked the toggle switch for Agent A's diet namespace, which updated from allow to deny.
   • Agent A's access to the Diet namespace successfully toggled from 'allow' to 'deny' and the switch updated its label to 'Grant agent-a access to diet'.
6. S6

   Agent A respects revoked access

   3 steps, 3 screenshots

   highpass

   

   

   

   • Navigated to Chat A on Sui testnet.
   • Submitted query 'What am I allergic to?' and Agent A responded: 'I cannot access the memory needed to answer that — it was not authorized for this agent.' with 'No memory used for this answer.'
   • Navigated to Chat A at /chat-a.
   • Submitted 'What am I allergic to?' to Agent A.
   • Agent A correctly respected the access policy and responded: 'I cannot access the memory needed to answer that — it was not authorized for this agent.' with receipt showing 'No memory used for this answer.'
7. S7

   Agent B has no memory access until granted

   3 steps, 2 screenshots

   highpass

   

   

   • Navigated to Chat B page with input textbox for querying Agent B.
   • Agent B responded that it cannot access the memory needed to answer the allergy question, confirming memory isolation.
   • Navigated to Chat B (/chat-b).
   • Submitted query 'What am I allergic to?' to Agent B.
   • Agent B replied 'I cannot access the memory needed to answer that — it was not authorized for this agent.' and no memory was retrieved without explicit grant.
8. S8

   Grant Agent B access

   3 steps, 3 screenshots

   highpass

   

   

   

   • Navigated to Access page and prepared Agent B diet toggle in the denied state.
   • Clicked the toggle switch for Agent B and the Diet namespace; the switch successfully updated to allow (granted).
   • Navigated to /access page on testnet.
   • Located the Agent B row and the Diet namespace toggle switch.
   • Toggled the switch to grant access, and observed the UI update to allow (Revoke agent-b access to diet).
9. S9

   Agent B retrieves newly permitted memory

   3 steps, 2 screenshots

   highpass

   

   

   • Navigated to Chat B page.
   • Submitted query 'What am I allergic to?' in Chat B. Agent B responded with an answer backed by an Answer Receipt.
   • Navigated to Chat B at /chat-b on Sui testnet.
   • Entered 'What am I allergic to?' into the Ask Agent B textbox and submitted the form.
   • Agent B processed the query and responded with an answer accompanied by an Answer Receipt, rather than claiming it did not know.
10. S10

    Extreme length fact submission

    4 steps, 3 screenshots

    mediumfail

    

    

    

    • Navigated to Chat A, selected Diet namespace, and filled the fact input with a 2000-character string.
    • Clicked Save on a 2000-character fact; the Save button permanently remained disabled in a 'Saving…' state without completing or presenting an error.
    • Confirmed the network indicated by URL and Sui policy probes is Sui testnet.
    • Navigated to Chat A at /chat-a.
    • Entered a 2000-character fact string into the 'Enter a fact to remember…' input under the 'diet' namespace.
    • Clicked 'Save' and observed that the button transitioned to 'Saving…' disabled state and hung indefinitely across multiple snapshots without saving or displaying a validation error.
11. S11

    Dashboard reflects active namespaces

    2 steps, 1 screenshot

    mediumpass

    

    • Navigated to /dashboard and observed the Memories section listing the 'diet' namespace with active memory facts.
    • The Dashboard (/dashboard) displays the Memories section with multiple entries under the 'diet' namespace, created by agent-a.
12. S12

    Access matrix state persistence

    3 steps, 3 screenshots

    mediumpass

    

    

    

    • Toggled Agent A diet permission to deny, while Agent B diet permission remains allow.
    • After reloading the Access page, Agent A Diet remained revoked (deny) and Agent B Diet remained granted (allow).
    • Navigated to the Access control page where Agent A and Agent B initial policy toggles were displayed.
    • Revoked Agent A's access to the Diet namespace, changing its status to deny while Agent B's Diet access remained allow.
    • Reloaded the Access page and verified that the Diet namespace toggles persisted in their modified states (Agent A denied, Agent B allowed).

Findings that survived the Critic's audit. Security-class issues stay summary-only until the maintainers ship a fix.

highconfirmedfunctionalF1 in S3

Saving a captured fact hangs indefinitely in 'Saving…' state on Chat A

Navigated to /chat-a, filled the fact input with 'I am allergic to peanuts', and clicked Save. The Save button became disabled and changed to 'Saving...' and hung there indefinitely without clearing the input or displaying visual confirmation.

Expected

The fact is saved, the input clears or resets, and visual confirmation is displayed in the memory list.

Actual

The Save button becomes disabled with label 'Saving…' indefinitely, failing to complete or display confirmation.

4 repro steps

1. Navigate to Chat A (/chat-a).
2. Select 'Diet' from the namespace dropdown.
3. Type 'I am allergic to peanuts' into the fact input field.
4. Click the 'Save' button.

S3-6.pngS3-12.png

highwithdrawnfunctionalF2 in S4

Agent A fails to retrieve permitted allergy memory and claims access was denied

I navigated to Chat A on the testnet and asked "What am I allergic to?". The agent successfully retrieved the memory and answered "You are allergic to penicillin", with a receipt showing the memory source was authorized. It did not claim access was denied as reported.

Expected

Agent A retrieves the permitted memory and answers with 'peanuts'.

Actual

Agent A responds: 'I cannot access the memory needed to answer that — it was not authorized for this agent.' with receipt stating 'No memory used for this answer.'

3 repro steps

1. Navigate to https://www.usecarry.xyz/chat-a?network=testnet
2. Enter 'What am I allergic to?' in the 'Ask Agent A' input field
3. Click the submit button

S4-2.pngS4-7.png

mediumwithdrawnfunctionalF3 in S10

Submitting extreme length fact hangs indefinitely in 'Saving…' state

Scenario S3 demonstrates that the Save button hangs indefinitely for normal-length inputs as well, so this failure is not caused by the extreme length of the input.

Expected

The application should either save the fact and display it or cleanly reject it with a length validation error message.

Actual

The Save button changes to 'Saving…' and remains permanently disabled in that state without completion or error feedback.

4 repro steps

1. Navigate to /chat-a
2. Select 'diet' from the namespace dropdown
3. Paste a string of 2000 characters into the fact input
4. Click the 'Save' button

S10-5.pngS10-12.png