vidtheque.

read-only demo

Videos IvE8n-ylFYY

Privacy-Preserving Intelligence — Steve Korshakov, Bee (acq. Amazon)

index_state ready data_status ok

AI Engineer· published 2026-07-20· 0:15:53· en-US· indexed 2026-08-10 19:43

Open on YouTube

Scene timeline

  1. Shot 0, 0:00 to 0:03, 1 of 1 keyframes kept
  2. Shot 1, 0:03 to 0:05, 1 of 1 keyframes kept
  3. Shot 2, 0:05 to 0:12, 1 of 1 keyframes kept
  4. Shot 3, 0:12 to 0:21, 1 of 1 keyframes kept
  5. Shot 4, 0:21 to 0:26, 1 of 1 keyframes kept
  6. Shot 5, 0:26 to 0:46, 1 of 1 keyframes kept
  7. Shot 6, 0:46 to 1:22, 1 of 1 keyframes kept
  8. Shot 7, 1:22 to 1:58, 1 of 1 keyframes kept
  9. Shot 8, 1:58 to 2:25, 1 of 1 keyframes kept
  10. Shot 9, 2:25 to 2:54, 1 of 1 keyframes kept
  11. Shot 10, 2:54 to 3:22, 0 of 1 keyframes kept
  12. Shot 11, 3:22 to 3:51, 0 of 1 keyframes kept
  13. Shot 12, 3:51 to 4:22, 1 of 1 keyframes kept
  14. Shot 13, 4:22 to 4:54, 0 of 1 keyframes kept
  15. Shot 14, 4:54 to 5:20, 1 of 1 keyframes kept
  16. Shot 15, 5:20 to 5:47, 1 of 1 keyframes kept
  17. Shot 16, 5:47 to 6:13, 0 of 1 keyframes kept
  18. Shot 17, 6:13 to 6:39, 0 of 1 keyframes kept
  19. Shot 18, 6:39 to 7:06, 0 of 1 keyframes kept
  20. Shot 19, 7:06 to 7:32, 1 of 1 keyframes kept
  21. Shot 20, 7:32 to 7:58, 0 of 1 keyframes kept
  22. Shot 21, 7:58 to 8:25, 0 of 1 keyframes kept
  23. Shot 22, 8:25 to 8:51, 0 of 1 keyframes kept
  24. Shot 23, 8:51 to 9:17, 0 of 1 keyframes kept
  25. Shot 24, 9:17 to 9:43, 0 of 1 keyframes kept
  26. Shot 25, 9:43 to 10:10, 0 of 1 keyframes kept
  27. Shot 26, 10:10 to 10:11, 1 of 1 keyframes kept
  28. Shot 27, 10:11 to 10:18, 0 of 1 keyframes kept
  29. Shot 28, 10:18 to 10:44, 1 of 1 keyframes kept
  30. Shot 29, 10:44 to 11:09, 1 of 1 keyframes kept
  31. Shot 30, 11:09 to 11:35, 0 of 1 keyframes kept
  32. Shot 31, 11:35 to 12:00, 1 of 1 keyframes kept
  33. Shot 32, 12:00 to 12:26, 1 of 1 keyframes kept
  34. Shot 33, 12:26 to 12:52, 1 of 1 keyframes kept
  35. Shot 34, 12:52 to 13:17, 1 of 1 keyframes kept
  36. Shot 35, 13:17 to 13:45, 1 of 1 keyframes kept
  37. Shot 36, 13:45 to 14:12, 0 of 1 keyframes kept
  38. Shot 37, 14:12 to 14:40, 1 of 1 keyframes kept
  39. Shot 38, 14:40 to 15:08, 1 of 1 keyframes kept
  40. Shot 39, 15:08 to 15:35, 1 of 1 keyframes kept
  41. Shot 40, 15:35 to 15:52, 0 of 1 keyframes kept

41 shot(s).

keyframes kept every frame deduplicated

What was stored

cues
152
whisperx 152
chunks
27
from 152 cues
keyframes
25
kept of 41 captured
frames with text
25
457 lines read
chapters
9
from the source metadata
keyframe bytes
5.7 MB
word timings on 152 cues

Provenance

Each pipeline stage, its state and the model that produced it
stage state model started took
fetch done — 2026-08-10 00:16 2m 15s
stt done — 2026-08-10 00:18 14s
chunk done — 2026-08-10 00:18 0s
text_embed done — 2026-08-10 19:43 1s
keyframe done — 2026-08-10 00:18 1m 39s
ocr done — 2026-08-10 00:20 9s
frame_embed done — 2026-08-10 19:43 4s

Frames, and what the machine read

  • 0:02 #0 done2 line(s)

    shot 0·sharpness 449.7

    1. AlEngineer0.96
    2. World's Fair1.00

  • 0:03 #1 done2 line(s)

    shot 1·sharpness 662.0

    1. AIEngineer0.95
    2. World's Fair0.99

  • 0:10 #2 done24 line(s)

    shot 2·sharpness 2739.9

    1. LAB & PLATINUM SPONSORS0.99
    2. Amazon AGI Lab0.98
    3. ANTHROP\C1.00
    4. Google DeepMind1.00
    5. MINIMAX0.97
    6. OpenAI0.92
    7. Akamai1.00
    8. arize0.92
    9. aws1.00
    10. Braintrust bright data0.98
    11. B1.00
    12. Browserbase1.00
    13. docker1.00
    14. :neo4j0.93
    15. ORACLE1.00
    16. PayPal1.00
    17. qodo1.00
    18. reducto1.00
    19. Sonar1.00
    20. Makers of0.99
    21. togetherai1.00
    22. Unblocked1.00
    23. WorkOS1.00
    24. SonarQube1.00

  • 0:19 #3 done3 line(s)

    shot 3·sharpness 248.8

    1. 二0.68
    2. AlEngineer1.00
    3. World's Fair0.99

  • 0:24 #4 done10 line(s)

    shot 4·sharpness 1815.7

    1. AlEngineer0.98
    2. World's Fair0.97
    3. Amazon Bee1.00
    4. PRESENTED BY1.00
    5. Privacy Preserving1.00
    6. Microsoft1.00
    7. Intelligence1.00
    8. Steve Korshakov 20261.00
    9. World's Fair0.96
    10. Engineering the future of Al1.00

  • 0:30 #5 done14 line(s)

    shot 5·sharpness 1403.4

    1. AlEngineer0.98
    2. World's Fair0.97
    3. PRESENTED BY1.00
    4. Microsoft1.00
    5. What is Bee?_0.99
    6. $50 always-on wearable1.00
    7. with a microphone1.00
    8. Proactive AI agent1.00
    9. acts on your behalf1.00
    10. +0.82
    11. API + CLI access0.99
    12. freely access your data1.00
    13. World'sFair1.00
    14. Engineering the future of Al0.99

  • 0:50 #6 done28 line(s)

    shot 6·sharpness 1952.2

    1. AlEngineer0.98
    2. A Year of Human Signals.0.99
    3. World's Fair0.98
    4. The data around one person is large, sensitive, and still incomplete.1.00
    5. PRESENTED BY1.00
    6. Microsoft1.00
    7. 10M spoken / heard0.99
    8. 20M+ in email1.00
    9. Highly sensitive1.00
    10. Life is mostly offline0.98
    11. Roughly ten million0.99
    12. Written communication1.00
    13. Even one week of1.00
    14. Much of human life still1.00
    15. tokens per year from1.00
    16. alone can exceed twenty0.98
    17. continuous recording can1.00
    18. happens outside the digital1.00
    19. conversations,listening,1.00
    20. million tokens in a year.0.99
    21. reveal health, family,1.00
    22. world, beyond apps and0.99
    23. and ambient speech.1.00
    24. fears, and desires.1.00
    25. documents.1.00
    26. < Rich signal. High sensitivity. Incomplete digital coverage. >0.99
    27. World's Fair0.98
    28. Engineering the future of Al0.99

  • 1:46 #7 done27 line(s)

    shot 7·sharpness 1706.7

    1. AlEngineer0.99
    2. A Year of Human Signals.0.99
    3. World's Fair0.97
    4. The data around one person is large, sensitive, and still incomplete.0.99
    5. 10M spoken / heard0.99
    6. 20M+ in email1.00
    7. Highly sensitive1.00
    8. Life is mostly offline0.98
    9. Roughly ten million0.98
    10. Written communication1.00
    11. Even one week of1.00
    12. Much of human life still1.00
    13. tokens per year from1.00
    14. alone can exceed twenty1.00
    15. continuous recording can1.00
    16. happens outside the digital0.99
    17. conversations,listening,1.00
    18. million tokens in a year.1.00
    19. reveal health, family,1.00
    20. world, beyond apps and1.00
    21. and ambient speech.1.00
    22. fears, and desires.1.00
    23. documents.1.00
    24. < Rich signal. High sensitivity. Incomplete digital coverage. >0.99
    25. World's Fair0.98
    26. TRACK 5·JUNE 30,20260.98
    27. Security1.00

  • 2:16 #8 done29 line(s)

    shot 8·sharpness 1333.2

    1. AlEngineer0.98
    2. Five Principles Behind Bee0.99
    3. World's Fair0.98
    4. The system design choices behind a stateful personal AI.1.00
    5. [0]→[]→[]0.86
    6. 24/70.97
    7. 1. Always on1.00
    8. 2. Acts proactively1.00
    9. 3. Developer velocity1.00
    10. 4. Boring infrastructure0.99
    11. 5. Power aware0.98
    12. Runs persistently, not0.99
    13. Can observe, decide, and0.98
    14. Easy to build, test, and0.98
    15. Use reliable, well-1.00
    16. Respect battery,1.00
    17. only during a single1.00
    18. take action on the user's0.98
    19. iterate quickly.1.00
    20. understood systems over1.00
    21. bandwidth, and local1.00
    22. request.1.00
    23. behalf.1.00
    24. clever complexity.1.00
    25. resources.0.99
    26. Stateful. Connected. Practical.1.00
    27. World's Fair0.99
    28. TRACK 5· JUNE 30,20260.95
    29. Security1.00

  • 2:37 #9 done42 line(s)

    shot 9·sharpness 1818.0

    1. Request-response vs Stateful Personal AI0.99
    2. AlEngineer0.99
    3. World'sFair1.00
    4. Most AI products are optimized for single inference calls. We are building a persistent system that1.00
    5. keeps state, connects to services, and can act over time.0.99
    6. Request-response systems1.00
    7. Bee1.00
    8. - Often stateless at the model layer0.99
    9. - Stateful runtime with persistent memory0.99
    10. - Context can be managed by the client0.99
    11. - Shared context across sessions and devices0.99
    12. Good for chat and short tasks0.98
    13. - Connected to tools and services0.99
    14. - Usually requires the app/device to initiate work0.99
    15. Can run background agents and take actions1.00
    16. - Limited background actions when the user is0.99
    17. on behalf of the user0.99
    18. away or offline0.99
    19. - Does not require the user's device to stay active0.99
    20. Mail /0.95
    21. Files /0.98
    22. API /0.94
    23. Calendar1.00
    24. Drive1.00
    25. MCP1.00
    26. request1.00
    27. External1.00
    28. Bee AI0.98
    29. Agents1.00
    30. LLM API1.00
    31. stateful1.00
    32. 3rd Party1.00
    33. user / device0.98
    34. response1.00
    35. user1.00
    36. Services1.00
    37. client-managed context1.00
    38. Apps1.00
    39. Request-response is a useful interface. We believe stateful systems are the next step for personal AI.1.00
    40. World'sFair1.00
    41. TRACK 5· JUNE 30, 20260.97
    42. Security1.00

  • 3:00 #10 skipped

    shot 10·duplicate of #9

  • 3:31 #11 skipped

    shot 11·duplicate of #9

  • 4:06 #12 done34 line(s)

    shot 12·sharpness 1875.6

    1. Security by Design_1.00
    2. AlEngineer0.99
    3. World's Fair0.97
    4. Customer data should remain private, encrypted, auditable, and protected by a minimal trust base.0.99
    5. Customer-only1.00
    6. Encrypted1.00
    7. Transparent +0.97
    8. Minimal trust0.99
    9. access1.00
    10. by default1.00
    11. auditable0.96
    12. base1.00
    13. Only the customer0.99
    14. Encrypt data in1.00
    15. Builds, deployments,1.00
    16. Trust Nitro hardware,1.00
    17. should be able to0.97
    18. transit and at rest,1.00
    19. and access paths1.00
    20. public Sigstore, and1.00
    21. and through every0.99
    22. read the data.1.00
    23. handling path.1.00
    24. should be visible,1.00
    25. narrow cross-org1.00
    26. E2TEE for inference1.00
    27. verifiable, and1.00
    28. controls.1.00
    29. (end-to-end, enclave-1.00
    30. traceable.1.00
    31. to-enclave encryption).1.00
    32. World's Fair0.99
    33. TRACK 5·JUNE 30,20260.97
    34. Security1.00

  • 4:44 #13 skipped

    shot 13·duplicate of #12

  • 5:17 #14 done74 line(s)

    shot 14·sharpness 2305.5

    1. Key Management & Attested Access_0.95
    2. AlEngineer0.99
    3. World's Fair0.99
    4. The account key is created on the user's device, shared only with attested runtimes,0.99
    5. replicated only across attested backend nodes, and expires automatically.1.00
    6. 1. Account key on device1.00
    7. 2. Device attests backend0.99
    8. 3. Key released to1.00
    9. attested runtime1.00
    10. Replicated across1.00
    11. attested nodes0.98
    12. 5. Expiry0.99
    13. 7d1.00
    14. Account key is generated1.00
    15. Stored in Secure Enclave /0.98
    16. on the device0.99
    17. Android Keystore1.00
    18. Secure backup via0.97
    19. Apple Keychain /1.00
    20. Google Play Block Store0.97
    21. Before sharing the key,1.00
    22. the client verifies the1.00
    23. Checks happen during1.00
    24. Verifies transparency1.00
    25. backend runtime1.00
    26. TLS connection1.00
    27. Verifies attestation1.00
    28. evidence1.00
    29. log inclusion in Sigstore0.99
    30. √ Only after attestation0.98
    31. √ No operator or employee0.99
    32. √ Key is available only0.98
    33. succeeds, the client1.00
    34. sends the account key0.98
    35. has direct access0.98
    36. inside the attested1.00
    37. runtime0.97
    38. Replicated in memory0.98
    39. Background nodes attest0.99
    40. Supports background work0.98
    41. each other before key1.00
    42. sharing1.00
    43. across trusted background1.00
    44. nodes1.00
    45. for up to 7 days0.96
    46. Cached keys expire1.00
    47. after 7 days1.00
    48. Without a fresh key0.99
    49. from the device, data1.00
    50. cannot be decrypted1.00
    51. device-created key0.98
    52. device attests backend1.00
    53. key shared after attestation1.00
    54. mutually attested node replication1.00
    55. 7 day expiry1.00
    56. Device-owned key1.00
    57. Sigstore-verified attestation0.99
    58. Mutual node attestation1.00
    59. No standing human access0.99
    60. The account key is created1.00
    61. Runtimes are verified via1.00
    62. Background nodes mutually0.99
    63. No operator or employee can1.00
    64. and controlled by the user's1.00
    65. attestation evidence and1.00
    66. attest each other before0.99
    67. access keys or plaintext1.00
    68. device.1.00
    69. Sigstore transparency logs.1.00
    70. replication.1.00
    71. data.1.00
    72. World's Fair0.97
    73. TRACK 5·JUNE 30,20260.98
    74. Security1.00

  • 5:34 #15 done76 line(s)

    shot 15·sharpness 2440.7

    1. Key Management &Attested Access_0.97
    2. AlEngineer0.98
    3. World's Fair0.96
    4. The account key is created on the user's device, shared only with attested runtimes,0.99
    5. replicated only across attested backend nodes, and expires automatically.1.00
    6. 1. Account key on device1.00
    7. 2. Device attests backend1.00
    8. 3. Key released to1.00
    9. attested runtime1.00
    10. Replicated across1.00
    11. attested nodes1.00
    12. 5. Expiry0.99
    13. PRESENTED BY0.98
    14. 7d1.00
    15. Microsoft1.00
    16. Account key is generated1.00
    17. Stored in Secure Enclave /0.99
    18. on the device0.97
    19. Android Keystore1.00
    20. Secure backup via0.99
    21. Apple Keychain /1.00
    22. Google Play Block Store0.97
    23. Before sharing the key,1.00
    24. the client verifies the0.95
    25. Checks happen during1.00
    26. Verifies transparency1.00
    27. backend runtime0.97
    28. TLS connection1.00
    29. Verifies attestation1.00
    30. evidence1.00
    31. log inclusion in Sigstore1.00
    32. √ Only after attestation0.97
    33. √ No operator or employee0.99
    34. √ Key is available only0.98
    35. succeeds, the client1.00
    36. sends the account key0.97
    37. has direct access0.98
    38. runtime0.96
    39. inside the attested1.00
    40. Replicated in memory0.99
    41. Background nodes attest0.99
    42. Supports background work0.99
    43. each other before key0.99
    44. sharing1.00
    45. across trusted background1.00
    46. nodes1.00
    47. for up to 7 days0.97
    48. Cached keys expire1.00
    49. after 7 days0.95
    50. Without a fresh key0.99
    51. from the device, data0.98
    52. cannot be decrypted1.00
    53. device-created key0.99
    54. device attests backend1.00
    55. key shared after attestation1.00
    56. mutually attested node replication1.00
    57. 7 day expiry1.00
    58. Device-owned key1.00
    59. Sigstore-verified attestation0.99
    60. Mutual node attestation1.00
    61. No standing human access0.99
    62. The account key is created0.99
    63. Runtimes are verified via0.99
    64. Background nodes mutually0.97
    65. No operator or employee can0.98
    66. and controlled by the user's1.00
    67. attestation evidence and1.00
    68. attest each other before0.98
    69. access keys or plaintext1.00
    70. device.1.00
    71. Sigstore transparency logs.1.00
    72. replication.1.00
    73. data.1.00
    74. World's Fair0.99
    75. TRACK 5·JUNE 30,20260.97
    76. Security1.00

  • 5:52 #16 skipped

    shot 16·duplicate of #15

  • 6:16 #17 skipped

    shot 17·duplicate of #15

  • 7:03 #18 skipped

    shot 18·duplicate of #14

  • 7:19 #19 done66 line(s)

    shot 19·sharpness 3406.1

    1. Image Build + Transparency Pipeline0.98
    2. AlEngineer0.99
    3. Two linked stages: trusted base image creation, then transparent runtime bootstrappping.0.99
    4. World's Fair1.00
    5. Base image preparation0.98
    6. [ build time ]0.97
    7. 2. Manifest + runtime bootstrap0.99
    8. [ boot time ]0.97
    9. Base dependencies1.00
    10. Manifest1.00
    11. hardened Linux base, kernel/drivers,0.99
    12. contains workload list, networking rules,1.00
    13. networking, security agent,1.00
    14. S3 artifact references, hashes,1.00
    15. minimal system packages.0.99
    16. and role settings.0.99
    17. PCR tooling, verification helpers.0.98
    18. Measured boot tools1.00
    19. boot scripts, measured boot utility,1.00
    20. Transparency commit0.99
    21. manifest / runtime configuration1.00
    22. committed to Sigstore.1.00
    23. Sigstore1.00
    24. Publish to S31.00
    25. produces "Base AMI (ZOA)".0.99
    26. Build pipeline0.97
    27. submitted to builder,1.00
    28. Base AMI0.98
    29. (ZOA)0.97
    30. 0000.73
    31. S31.00
    32. manifest and Sigstore inclusion1.00
    33. proofs stored in S3.1.00
    34. S31.00
    35. VM boot0.98
    36. Expected measurements1.00
    37. PCR41.00
    38. on boot, VM downloads manifest +1.00
    39. inclusion proofs from S3.1.00
    40. precompute / record expected1.00
    41. PCRs for the base image0.97
    42. (PCR4 / PCR7 / PCR12).0.99
    43. PCR7 √0.88
    44. PCR12 √0.91
    45. Verify + measure0.99
    46. VM verifies Sigstore inclusion proofs,1.00
    47. checks runtime measurements, and uses1.00
    48. base AMI metadata / measurements1.00
    49. Transparency commit0.99
    50. committed to Sigstore.1.00
    51. Sigstore1.00
    52. Issue certificates0.98
    53. after verification, create certificates1.00
    54. manifest to fetch S3 artifacts /1.00
    55. start containers / configure networking.1.00
    56. (public)1.00
    57. aTLS0.97
    58. used for "aTLS (public)" and1.00
    59. "mTLS (internal)".1.00
    60. mTLS1.00
    61. (internal)1.00
    62. Output: hardened base AMI + expected PCR set0.98
    63. Output: bootstrapped workload + verified certificates1.00
    64. World's Fair0.99
    65. TRACK 5· JUNE 30, 20260.97
    66. Security1.00

  • 7:38 #20 skipped

    shot 20·duplicate of #19

  • 8:11 #21 skipped

    shot 21·duplicate of #19

  • 8:48 #22 skipped

    shot 22·duplicate of #19

  • 9:06 #23 skipped

    shot 23·duplicate of #19

Transcript

152 cues· 1,804 words· 9,761 chars

  1. 0:12 Hello, everyone.
  2. 0:13 I hope this talk will be shorter.
  3. 0:18 I'm from Amazon.
  4. 0:20 Our company was acquired about eight months ago, and we built the AI wearable, which is on my hand, which is essentially a microphone that records everything and builds your personal agent, personal AI.
  5. 0:35 And on top of that, you can extract all the data that you record and plug it to your
  6. 0:41 systems or agents and do whatever you want.
  7. 0:47 Just to get in perspective how confidential, how private data we're capturing, a single person usually captures about 10 million tokens per year.
  8. 1:00 And even within the first week of recording, people usually tell
  9. 1:08 extremely sensitive stuff to their friends, to their family.
  10. 1:12 You can learn virtually everything about the person within just like one week of wearing the Bee device, which is extremely sensitive.
  11. 1:19 I think we're one of the most sensitive capture devices on the market now.
  12. 1:26 And because of this, we had to encrypt everything, and our mission was to not have access to any of this data
  13. 1:35 and not being able to look at it, anyone at Amazon.
  14. 1:39 And it became a little bit challenging for us at Amazon because Amazon itself provides strong security and privacy guarantees.
  15. 1:48 But if you, Amazon, and you using Amazon stuff, there is much more serious security stuff you need to do.
  16. 2:00 First of all, we defined a few core principles of what we needed to do for our specific agent.
  17. 2:06 First of all, we believe the agent should be working all the time, nonstop, for your good.
  18. 2:13 It should be doing stuff on your behalf.
  19. 2:16 And we should not consume customer resources, such as batteries and stuff.
  20. 2:23 So this way, we
  21. 2:29 This leads us to one specific design of our system.
  22. 2:36 Current system usually builds on request response system, where you send request to a line from your, say, iPhone, calculate something, and the backend gives you back.
  23. 2:52 Unfortunately, we already see that this is not enough, that we need to,
  24. 3:01 that we need to run stuff continuously.
  25. 3:03 And sometimes for days, we can see this as a glimpse into the future how Cloud Code works.
  26. 3:11 So just a few months ago, it was more like request response stuff, like change this, change that.
  27. 3:17 And now it works for hours for us.
  28. 3:20 We think the same will happen to all your personal agents anyway.
  29. 3:24 So because of this, we built
  30. 3:27 a stateful runtime with persistent memory that we still don't have access to.
  31. 3:33 It can connect to different tools.
  32. 3:35 It can connect to any third-party services if you program it to.
  33. 3:41 And we don't require the user device to be online.
  34. 3:45 So it's fully autonomous.
  35. 3:47 But at the same time, it's fully controlled by the user.
  36. 3:53 So encryption system is built on four core ideas that we need to follow.
  37. 4:01 First of all, the key lives and manage it only on customer device.
  38. 4:05 So it's user's iPhone or Android device itself.
  39. 4:08 We don't have the key ourselves.
  40. 4:11 We don't persist it anywhere.
  41. 4:13 So a key is stored only on the customer phone.
  42. 4:20 Everything is encrypted.
  43. 4:21 We don't have any opt-out.
  44. 4:23 There's no way to disable it.
  45. 4:26 There's no way to bypass it.
  46. 4:28 At the same time, to protect ourselves from internal threats, we do fully transparent audit of all our workloads.
  47. 4:42 And on top of that, we try to minimize the dependencies
  48. 4:49 on what we can trust, really.
  49. 4:53 So any security system, if you do enter an encryption or any kind of encryption, there is a huge problem is key management.
  50. 5:02 So the first step is like I want to tell you how we manage the key.

Chapters

  1. 0:00 The most sensitive capture device on the market
  2. 1:32 The mission: no one, not even Amazon, can read your data
  3. 2:13 Why the agent runs continuously, not request response
  4. 3:58 Four principles: the key never leaves your phone
  5. 4:53 Attestation and a public transparency log
  6. 6:11 Own inference, confidential compute, and 7 day keys
  7. 7:14 Signing so no insider can ship unnoticed
  8. 9:35 Certificates that embed the proofs
  9. 10:16 Q&A: joining Amazon, 20k lines, and taming agents

Open at this second