Bee Box documentation · directory: https://beebox.run/docs/reference/cards/ · index: https://beebox.run/docs/reference/cards/index.md · root: https://beebox.run/llms.txt

# glink Card

# Glink Cards

A `.glink.card` says **"this Drive item exists, here is where it lives, here
is what it is for."** Nothing is copied into the box — no attach scope, no
export. To read the item, open `link:` or run `bbx drive inspect <drive-id>`.

Two ways one shows up:

- `origin: mirror` — a `.gfolder.card` mirror found a child it cannot sync
  (a PDF, a Slides deck, an image) and left a pointer instead. It sits beside
  the folder's synced children.
- `origin: manual` — someone ran `bbx drive link <url> <path>`, usually
  because a single Drive item is worth remembering without mirroring anything.

## Frontmatter is the connector's; the body is yours

`drive-id`, `link`, `name`, and `mime` are stamped from Drive on every
sync — hand-edit them and the next sync writes them back. Do not.

The **body is purpose notes**, written by the boxholder or by an agent on their
behalf, and the connector never touches it: what the item is for, what is in
it, who asked for it, what to do with it. A mirror emits a pointer with an
empty body; filling it in is how the box learns why the item matters. Write
plain prose:

```markdown
The signed lease. Renewal decision is due each February — check the
escalation clause in section 7 before renewing.
```

## Not a synced file

A pointer is not a `.gdoc.card` / `.gsheet.card`. There is no local copy to
edit and nothing pushes back to Drive. If the item is a Doc or a Sheet and you
want it synced, mount it with `bbx drive add` instead — a pointer to a
syncable type usually means someone chose not to copy it.

## The `contains:` field

Give this card a one-sentence `contains:` — the prime retrieval field for
`bbx search` and listings. How to write a good one (carry the information when
it's concise, never a list of parts, under 200 characters) is in the agent
guide's ABOUT_CARDS section.