Skip to content
bucker

Closed capture: ingest keeps only the fields a person accepted

A capture manifest lists the fields an SDK release says it collects. Until a person accepts one, a project is open: the manifest is a record of what arrives, and nothing is removed. Once a person accepts a manifest (or pins one), the project is closed for that SDK: ingest keeps only the fields the accepted manifest declares, from any client, and removes the rest before anything is stored.

An open project is unchanged. The implicit manifest Bucker writes the first time an SDK reports closes nothing.

What closed capture does

  • Field grain. Every key of an event, span, log record, session, check_in, product_event, feedback or repro_capsule payload that the accepted fields do not declare is removed, including keys no manifest names (a field a fork added by hand). A declared path keeps its whole subtree, so open-ended fields such as contexts, tags and request.headers are single manifest entries.
  • The envelope is still accepted. Each item keeps its accepted result. Removal is reported as a count, not as a refusal, so an SDK that adds a field does not start losing events.
  • Passed as sent. A Sentry transaction, item types the manifest does not describe or lists under notCovered, and payloads that are not JSON.
  • A sender Bucker holds no manifest for (a renamed fork, a hand-written client, a Sentry SDK) is held to the union of the project's person-accepted fields for that item type.

Rules and remote configuration are held to the same manifest

The capture rules a caller can state only remove collection. What can switch a field on is the exception capture entry of the same document, and a live document that names a field the accepted manifest does not declare is refused when it is previewed or updated. The document an SDK is served is cut to the accepted fields as well, so a manifest change takes effect without a new version.

Seeing what was removed

sdk_inventory_get with include: ["field_diff"] returns, for a closed or implicit SDK:

  • the accepted version and the newest version, with field counts;
  • the fields the newest release declares that the accepted version does not (stripped while closed);
  • the fields no longer declared;
  • a count per field of what was removed, under the reason field_not_in_manifest.

Counts are kept per field-key hash. A path is shown only where a manifest this server holds names the field or one of its ancestors; otherwise only the hash appears, and the raw key is never stored. At most 200 hashes are counted per manifest version, then an other bucket.

Who may change it

Narrowing capture (capture_manifest.narrow) needs capture:write and goes through the same policy, freeze and review-mode checks as every other change. A release that adds even one field the project has not accepted is not a narrowing: widening is a person's act. Pinning the release a project already accepted implicitly is allowed, and is how a project closes capture without widening anything.

There is no REST or MCP door for the narrowing yet; until it is added, an agent cannot reach it.