eden/docs/design-records/t08-inventory-location.md

T08 inventory location integration

Status: implemented against T07 checkpoint fe7d218195f8f501569c5a1e72f302733340be43.

• GET /universe/structures/{structure_id} is a fixed ESI operation pinned to esi-universe.read_structures.v1 and the captured OpenAPI evidence in docs/research/eve-openapi-evidence.json.
• inventory_query remains assets-only. inventory_locations is an additive, explicit consent capability for structure evidence; existing grants are never silently expanded.
• Helper calls remain bounded to 1,000 IDs. Larger snapshots retain every response batch in the generation-level deterministic input pin; no cap is lifted.
• Location rows stage in private Convex chunks tied to the exact asset generation, authority counters/scopes, reference version, helper observations and deterministic enrichment version. Public station/system/region facts are included in the bounded pin with an internal consistency digest; that digest is not treated as external authenticity, and the pinned reference version remains the provenance boundary. Asset and enrichment manifests publish atomically.
• Partial/failed helper, reference and structure coverage is explicit. Raw assets remain usable, but only complete enrichment is complete; 403/404 structures remain unresolved and docking permission is always unknown. The initial optional-enrichment persistence prototype is conservatively capped at 2,500 rows and 16 MiB server-side; the worker preflights deterministic chunks at 192 KiB (below the 256 KiB conservative envelope target) and an aggregate 2 MiB budget before staging. Larger or oversized single-row enrichments publish raw assets with a truthful failed enrichment instead of attempting an unmeasured near-50k transaction.
• The sync worker receives only REFERENCE_DIR and a read-only reference-data mount. It opens an immutable pinned reader and has no reference import/write credentials. The mount must contain a compatible production-profile manifest/artifact; an invalid, missing, or fixture-profile artifact is treated as honest reference unavailability and raw assets still publish without enrichment. Host archives are not deployment volumes and must not be promoted as a deployed reference artifact.
• T09 projection, filtering and cursor behavior remains unimplemented by design; T09 consumes the generation-matching manifest/chunk seam.