> ## Documentation Index > Fetch the complete documentation index at: https://docs.wirevow.dev/llms.txt > Use this file to discover all available pages before exploring further. # The export bundle > One file per consented data class. A class not consented has no file, and the manifest's consent map says so, so a reviewer learns what travels by listing the directory `gitvow export` assembles the record into a directory a security team can read before anything moves. It carries the record, never the session: no transcript text, no working tree, no snapshot, no command line, no prompt. Nothing in this release sends; the bundle is the shape every sink will receive. ``` gitvow export --dry-run --why # what would leave, what never does, what was refused; writes nothing gitvow export --since 6m --out ./bundle gitvow export --consent decisions,claims ``` ## Layout ``` bundle-/ manifest.json # schema, kind, gitvow version, source, frontier, consent, parts with sha256, digest attestation.json # redaction rules digest, rows refused and why, what is never carried, signature (reserved) decisions.jsonl # one row per decision trailer, with its note fields when the note is present claims.jsonl # confirmed claims: id, text, paths, speaker, who confirmed with what standing observed.jsonl # Gitvow-Observed rows: finding, commit, date; no answer, no person rule-verdicts.jsonl # Gitvow-Rule-* with the frozen evidence run from the rules note sessions.jsonl # consented only: counts, attribution, usage, edits-elsewhere counts; never the plan text or paths gate-events.jsonl # consented only: counts per session per reason; never a command meter.json # commits, agent-signed commits, agent-authored lines, window, floor: true ``` ## Consent The committed file `.gitvow/export.json` is the repository's statement of what it lets leave: ```json theme={"dark"} {"consent": {"decisions": true, "claims": true, "observed": true, "rule_verdicts": true, "sessions": false, "gate_events": false, "meter": true}} ``` Those are also the defaults. `--consent a,b` overrides the file for one run. Consent widens only by a commit to that file, which is reviewed like any other change. ## Redaction is re-verified, never applied Every string in every row runs through the repository's redaction rules at export. A row that would change is **refused** and listed in `attestation.json` with the part, the row number and a digest of the offending field. It is never rewritten: a rewritten row would mean the write-time edge failed and the failure was hidden. Identifiers the record itself mints (claim ids, commit shas, session ids, digests) are exempt, since they look like tokens to the redactor and carry nothing. ## Manifest | Field | Meaning | | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | `kind` | always `record`; a raw-session artefact, if a customer ever produces one with a different command, is a different kind and is refused by every hosted sink | | `source.remote` | the normalised `origin` (host/owner/repo, no scheme, no `.git`), the join key across bundles from the same repository | | `frontier` | `head`, the note refs and their tips, the `since` window, `as_of`; exactly what this bundle covers | | `parts[]` | `path`, `class`, `sha256`, `rows`, `bytes` per file | | `digest` | sha256 over the part digests, in class order; the idempotency key. Sending the same bundle twice changes nothing | Parts are serialised canonically: rows sorted, keys sorted, no timestamps the exporter invented inside a part. The same repository at the same frontier yields the same digest. ## Rows Every row carries `source` and `sha` so it is meaningful on its own. `decisions.jsonl` rows carry `finding`, `kind`, `path`, `answer`, `by`, `authority`, `scope`, `to`, `note`, `human_turns_after_card`, `proposed`, `session_id`, `reason` and `binding` (`note` when the session note was present, `trivial` otherwise). `class` is `null` in this version: not computed, never "no class". `sessions.jsonl` rows carry `last_stated_plan: null`; the plan text is a sub-class that is off and not exportable here. Paths of edits made in other checkouts are never exported, only their counts. ## Sinks and `gitvow sync` A sink is where bundles go. Three kinds, all run by the customer: `git`, a store repository in the layout the store protocol describes (the bundle is committed under `bundles///` and the source's frontier file appended; the store's own tooling projects the index); `dir`, a directory or mounted object-store prefix (the bundle is copied to `//`); and `http`, a store served over HTTPS that speaks the store protocol's verbs (begin, one PUT per part, commit; idempotent by digest, parts already held are not resent). An `http` sink names a `url` and, for its bearer token, `token_env` (an environment variable, preferred) or `token`; TLS is the reverse proxy's job. A 4xx from an http store is a refusal, reported with the server's reason and never queued. ```json theme={"dark"} {"sinks": [{"name": "acme", "type": "git", "path": "~/acme-store"}, {"name": "archive", "type": "dir", "path": "/mnt/records"}, {"name": "store", "type": "http", "url": "https://store.acme.internal", "token_env": "WIREVOW_STORE_TOKEN"}]} ``` Sinks are configured only in files that are never committed: `.gitvow/export.local.json` in the repository, which `gitvow install` adds to `.git/info/exclude`, or `~/.gitvow/sinks.json`. A sink named in the committed `.gitvow/export.json` is ignored with a warning: a committed destination is how a contributor's record ends up in an upstream project's store. `gitvow sync [--sink NAME] [--since 90d] [--dry-run]` builds the bundle and delivers it to every configured sink. Delivery is idempotent by digest: a bundle a sink already holds is reported, not resent. When a sink is unreachable, the bundle waits in `~/.gitvow/outbox////` and the next sync drains the outbox oldest first. A sync never blocks a commit or a tool call, and it moves `kind: record` bundles only. ## What comes back: the pack and the brief After delivering to a `git` or `http` sink, `sync` copies what the store publishes for this repository into `~/.gitvow/cache/`: the organisation **pack** (`packs/.json` or `GET /v1/rules`, see [Policy schema](/gitvow/reference/policy)) and the **brief** (`brief/.json` or `GET /v1/brief`): standing per finding class across the organisation's repositories, accepted rules, confirmed claims, and gaps (conflict, unratified, decaying). Both are read from the cache only, never fetched during a tool call. `gitvow brief` prints the cached brief with its age and `source: cache`, marks it stale past the store's `stale_after`, and falls back to the repository's own record as `source: repo`; session start hands the same to the agent. A `dir` sink is a drop, not a store, so nothing comes back from it. ## What never leaves Transcripts, working trees, snapshots, command lines, prompts, and person-reach claims (a person's own preferences, which live in their `~/.gitvow/claims/` and nowhere else). The attestation states this list so it is on the record, not in a footnote. See also [Session note schema](/gitvow/reference/note) and [Decisions](/gitvow/concepts/decisions).