Connect your Drive

objects in your store 4

Point the office at YOUR own store. Connect your Google Drive and your dreams and messages stay exactly where they are — in your Drive, in your hands. The engine never receives the bytes; it keeps only a reference and a hash, enough to know a file exists and has not changed, and nothing more. This is a MOCK Drive this beat — no real account is touched; the real-OAuth pass ahead is a swap, not a build.

  • my dream: read Kazantzakis in the original — lives in your google drive; the engine never held these wordsdream
  • my dream: a balcony that grows food — lives in your google drive; the engine never held these wordsdream
  • a sealed message to my teacher — lives in your google drive; the engine never held these wordsmessage
  • a message I later erased — ERASED from your Drive; the engine keeps only a tombstone where its hash used to bemessage
  • my dream: read Kazantzakis in the original — the engine keeps a reference and a witness hash, and nothing else148 B
  • my dream: a balcony that grows food — the engine keeps a reference and a witness hash, and nothing else137 B
  • a sealed message to my teacher — the engine keeps a reference and a witness hash, and nothing else159 B
  • a message I later erased — the hash is gone; only a tombstoned ref remains, and it can never be resurrectedtombstone

Erasure is yours and it is final. Delete an object from your Drive and the engine drops its hash, keeping only a tombstoned reference — proof that something was there and is now gone, with no way to bring the bytes back. 1 object erased in this walk; its hash is cleared.

The engine never sees your bytes. Your files flow between your own client and your own store; the engine is handed only a hash to witness that a file exists and is unchanged. It cannot read your dreams. It cannot read your messages. It holds references, never contents — and when you erase, the reference is tombstoned and the hash is gone for good.