{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T10:58:10Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 19.0, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a09543-72d3-7212-8836-00419a00ec40\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: light field\nSense to describe: (none recorded)\nDomain code: XCT.REL\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 044: 1001 reg", "usd": 0.0, "recall": true }, "codex": { "seconds": 70.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a09543-72e2-7642-83d5-b60583540707\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: light field\nRegistry id: vr.tr.light-field\nPlane / domain: XCT / XCT.REL\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\n" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:42:05+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:31+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q593161", "registryId": "vr.tr.light-field", "name": "light field", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "XCT.REL" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q593161/", "model": { "registry_id": "vr.tr.light-field", "name": "light field", "purpose": "Enable an agent to recognise a light field, assess its directional and spatial coverage, and decide which viewing, refocusing or measurement operations its evidence supports.", "definition": "A light field describes the radiance of light as a function of position and propagation direction, usually at a fixed time and wavelength or over a specified spectral band.", "scope_statement": "This model owns vr.tr.light-field as a position-and-direction-dependent description of optical radiance and its operational representations, provisionally adopting the geometrical-optics interpretation because the registry records no definition.", "in_scope": [ "Definitions distinguishing a general position-and-direction radiance function from a reduced four-dimensional ray representation", "Ray coordinates, spatial boundaries, directional coverage and propagation assumptions", "Spectral, temporal and radiometric interpretation of field values", "Measured, simulated and inferred light-field samples and their calibration", "Conditions supporting view synthesis, computational refocusing and geometric inference" ], "out_of_scope": [ "Construction and operation of plenoptic cameras, camera arrays and light-field displays", "Full electromagnetic fields, optical phase and wave-interference models", "Scene geometry, material reflectance and illumination sources as independently modelled entities", "Neural-network architectures and volumetric scene representations used to generate ray observations", "Image-file formats, storage infrastructure and compression implementations" ], "distinguishing_features": [ "A light-field representation associates values with both ray position and ray direction; a conventional photograph alone does not establish independently sampled variation across both.", "An environment map records directional appearance from a reference location or under an explicit distant-scene approximation; it does not generally establish spatially varying ray values.", "A depth map records geometric distance rather than directional radiance, even when both are derived from the same capture.", "A radiance light field does not by itself record optical phase or the electric and magnetic field components needed for wave-optics analysis.", "A model must declare whether its values describe radiance along rays or local emission and attenuation that require a transport calculation to produce ray observations." ], "characteristics": [ { "name": "Definition and retained dimensions", "kind": "category", "unit_or_values": "Position-direction function; four-dimensional ray function; declared spectral or temporal extension", "why_it_matters": "Determines which variations are represented and which are fixed, integrated out or assumed redundant." }, { "name": "Ray parameterisation", "kind": "category", "unit_or_values": "Position plus direction; two-plane coordinates; another explicitly defined ray chart", "why_it_matters": "Allows an agent to interpret sample addresses and compare representations." }, { "name": "Spatial and angular support", "kind": "measurement", "unit_or_values": "Spatial extent in m; directions in rad or unit vectors; supported solid angle in sr", "why_it_matters": "Constrains where viewpoints and aperture samples can be requested." }, { "name": "Radiometric interpretation", "kind": "category", "unit_or_values": "Band-integrated radiance in W m^-2 sr^-1; spectral radiance with declared wavelength unit; calibrated channel values; relative encoded values", "why_it_matters": "Prevents encoded pixel values from being treated as physical radiance." }, { "name": "Sampling footprint", "kind": "measurement", "unit_or_values": "Spatial and angular spacing and integration footprints, with units defined by the ray chart", "why_it_matters": "Makes resolution limits and interpolation assumptions assessable." }, { "name": "Temporal and spectral support", "kind": "measurement", "unit_or_values": "Capture times and exposure intervals in s; wavelength bands in nm; channel response functions", "why_it_matters": "Determines whether samples describe compatible scene conditions and optical bands." }, { "name": "Propagation regime", "kind": "category", "unit_or_values": "Declared homogeneous transparent region; participating medium; refractive region; unresolved", "why_it_matters": "Controls whether straight-ray transport and dimensional reduction are justified." }, { "name": "Sample evidence origin", "kind": "relation", "unit_or_values": "Links from ray samples or regions to measurements, simulation runs, reconstruction methods and calibration records", "why_it_matters": "Separates observed support from inferred or generated content." }, { "name": "Operational validity", "kind": "state", "unit_or_values": "Supported, conditionally supported, unsupported or unassessed for each requested operation", "why_it_matters": "Prevents a single quality label from authorising every use of the field." } ], "affordances": [ "Query directional radiance or channel values at supported ray coordinates.", "Reparameterise rays while recording coverage loss and resampling effects.", "Synthesize viewpoints with explicit limits on interpolation and extrapolation.", "Compute refocused images or aperture integrations where ray coverage permits.", "Estimate disparity or depth with stated correspondence assumptions and uncertainty.", "Identify missing ray coverage and specify additional capture requirements." ], "agent_conduct": { "may": [ "Explain the light field concept and its use in imaging, rendering and displays.", "Capture or process light field data the agent is authorized to handle." ], "must_not": [ "Capture light field images of people without their consent where consent is required.", "Use refocusing or depth recovery to reveal details people meant to keep out of view.", "Present synthetic views from light field data as unaltered photographs." ], "requires_human": [ "Using light field capture in surveillance or identification of people." ] }, "ethics": { "considerations": [ "Light field capture records depth and multiple views, making images more revealing than ordinary photographs.", "Synthetic views can be mistaken for real scenes." ], "affected_parties": [ "People captured in images", "Viewers", "Researchers" ] }, "owners": { "steward": "Nobody owns it; it is a concept of optics.", "master_systems": [] }, "failure_modes_and_hazards": [ "Sampling errors cause artefacts that can be mistaken for real details.", "Large datasets raise storage and privacy risks." ], "what_it_is_for": [ "Light fields are used in computational photography, optical measurement and computer graphics to describe how radiance varies with position and direction.", "Sampled light fields can support changes in viewpoint or computational refocusing when their coverage and resolution are sufficient." ], "standards_and_regulation": [ "The International Commission on Illumination publishes CIE S 017/E:2020, the International Lighting Vocabulary, which standardizes radiometric terminology including radiance." ], "facets_not_applicable": { "recognition": "A light field is a mathematical description whose identity cannot be established from visual appearance alone." } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q593161: light field", "url": "https://www.wikidata.org/wiki/Q593161", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Light field", "url": "https://en.wikipedia.org/wiki/Light_field", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "definition-and-instance", "name": "Definition and instance", "description": "Establish which meaning of light field applies and what constitutes an instance.", "rationale": "The registry provides no definition, so an agent must record its interpretation explicitly.", "layers": [ { "id": "radiance-convention", "name": "Radiance convention", "description": "Identify the quantity and independent variables used by the adopted definition.", "findings": [ { "id": "position-direction-definition", "name": "Position-direction definition", "description": "Record the adopted radiance definition and its authority. Levoy and Hanrahan define light fields through position and direction: [Light Field Rendering](https://www.graphics.stanford.edu/papers/light/).", "questions": [ { "text": "Which definition and source govern this instance, and what quantity does the function return?", "kind": "definition", "id": "position-direction-definition-q01" }, { "text": "Are wavelength and time explicit coordinates, fixed conditions or integrated variables?", "kind": "boundary", "id": "position-direction-definition-q02" } ] } ] }, { "id": "instance-boundaries", "name": "Instance boundaries", "description": "Separate the field being described from its captures and computational encodings.", "findings": [ { "id": "field-versus-representation", "name": "Field versus representation", "description": "Record whether an instance denotes a physical radiance distribution, a sampled observation or an inferred representation, and how these are related.", "questions": [ { "text": "Does this instance denote the optical distribution, a particular capture or a reconstruction?", "kind": "definition", "id": "field-versus-representation-q01" }, { "text": "Which changes in scene, illumination or time create a different field instance?", "kind": "boundary", "id": "field-versus-representation-q02" } ] } ] } ] }, { "id": "ray-domain-and-transport", "name": "Ray domain and transport", "description": "Specify ray identities, coverage and the physical assumptions behind their use.", "rationale": "A ray address is meaningful only with a coordinate convention and a valid propagation domain.", "layers": [ { "id": "ray-coordinate-system", "name": "Ray coordinate system", "description": "Describe how coordinates identify oriented rays.", "findings": [ { "id": "coordinate-interpretation", "name": "Coordinate interpretation", "description": "Record reference frames, orientation, units and any reference planes needed to interpret ray coordinates.", "questions": [ { "text": "How does a sample address map to a physical ray, including its direction of travel?", "kind": "definition", "id": "coordinate-interpretation-q01" }, { "text": "Which rays are excluded or singular under the chosen parameterisation?", "kind": "boundary", "id": "coordinate-interpretation-q02" } ] } ] }, { "id": "transport-assumptions", "name": "Transport assumptions", "description": "State where a reduced ray representation is valid.", "findings": [ { "id": "four-dimensional-reduction", "name": "Four-dimensional reduction", "description": "Record the region supporting a four-dimensional ray representation and the assumptions permitting position along a ray to be omitted. The classic formulation uses free-space regions: [Light Field Rendering](https://graphics.stanford.edu/projects/lightfield/gamma-corrected/).", "questions": [ { "text": "What evidence supports treating radiance as invariant along the represented ray segments?", "kind": "boundary", "id": "four-dimensional-reduction-q01" }, { "text": "Where do occlusion, attenuation, emission, scattering or refraction invalidate the adopted transport simplification?", "kind": "boundary", "id": "four-dimensional-reduction-q02" } ] } ] } ] }, { "id": "radiometric-spectral-temporal-meaning", "name": "Radiometric, spectral and temporal meaning", "description": "Make light-field values comparable and physically interpretable.", "rationale": "Ray geometry alone cannot establish what recorded brightness values mean.", "layers": [ { "id": "radiometric-values", "name": "Radiometric values", "description": "Track units, response corrections and unusable measurements.", "findings": [ { "id": "radiance-or-encoded-values", "name": "Radiance or encoded values", "description": "Require an explicit distinction between physical radiance and relative or display-encoded channel values.", "questions": [ { "text": "What units, exposure normalisation and response transformation define each value?", "kind": "measurement", "id": "radiance-or-encoded-values-q01" }, { "text": "Which samples are clipped, below the noise floor or affected by unresolved gain differences?", "kind": "measurement", "id": "radiance-or-encoded-values-q02" } ] } ] }, { "id": "spectral-temporal-compatibility", "name": "Spectral and temporal compatibility", "description": "Describe the wavelength and time intervals contributing to samples.", "findings": [ { "id": "compatible-ray-observations", "name": "Compatible ray observations", "description": "Record whether observations can be treated as samples of one field under the intended use.", "questions": [ { "text": "Which spectral responses and exposure intervals contribute to each group of ray samples?", "kind": "measurement", "id": "compatible-ray-observations-q01" }, { "text": "What evidence supports combining sequential views despite possible scene motion or illumination change?", "kind": "provenance", "id": "compatible-ray-observations-q02" } ] } ] } ] }, { "id": "sampling-and-reconstruction-evidence", "name": "Sampling and reconstruction evidence", "description": "Describe observed ray support and the evidence behind reconstructed values.", "rationale": "An agent must distinguish available observations from apparent completeness introduced by reconstruction.", "layers": [ { "id": "ray-sampling-support", "name": "Ray sampling support", "description": "Record sampling density, footprints and coverage gaps.", "findings": [ { "id": "measured-ray-coverage", "name": "Measured ray coverage", "description": "Describe the actual spatial-angular sample pattern, including finite integration footprints and missing observations.", "questions": [ { "text": "What are the spatial and angular sample spacings and footprints across the supported domain?", "kind": "measurement", "id": "measured-ray-coverage-q01" }, { "text": "Which requested rays fall between measured samples or outside observed coverage?", "kind": "boundary", "id": "measured-ray-coverage-q02" } ] } ] }, { "id": "calibration-and-inference", "name": "Calibration and inference", "description": "Connect ray assignments and reconstructed values to their supporting evidence.", "findings": [ { "id": "sample-lineage-and-error", "name": "Sample lineage and error", "description": "Record geometric calibration, value provenance and validation for measured, simulated, interpolated or learned samples.", "questions": [ { "text": "Which calibration records establish ray locations and directions, and with what residual error?", "kind": "provenance", "id": "sample-lineage-and-error-q01" }, { "text": "Which values are inferred, and what held-out observations or other evidence bound their error?", "kind": "measurement", "id": "sample-lineage-and-error-q02" } ] } ] } ] }, { "id": "supported-operations", "name": "Supported operations", "description": "Determine which transformations and inferences the particular field can support.", "rationale": "Useful actions depend on coverage, calibration and scene conditions rather than the light-field label alone.", "layers": [ { "id": "view-and-aperture-queries", "name": "View and aperture queries", "description": "Assess requested viewpoints and computational focus settings against available rays.", "findings": [ { "id": "rendering-query-admissibility", "name": "Rendering query admissibility", "description": "Record the ray support and validation required for a requested viewpoint, focus setting and synthetic aperture.", "questions": [ { "text": "Do the requested viewpoint and aperture require rays outside the calibrated support?", "kind": "action", "id": "rendering-query-admissibility-q01" }, { "text": "Which focus and aperture settings meet the task's stated sharpness and artifact tolerances?", "kind": "measurement", "id": "rendering-query-admissibility-q02" } ] } ] }, { "id": "geometric-inference", "name": "Geometric inference", "description": "Assess what directional variation permits an agent to infer about scene structure.", "findings": [ { "id": "disparity-and-depth-conditions", "name": "Disparity and depth conditions", "description": "Require geometric inference to state its calibration, correspondence and appearance assumptions and identify ambiguous regions.", "questions": [ { "text": "Which calibration and correspondence assumptions support converting angular variation into disparity or metric depth?", "kind": "definition", "id": "disparity-and-depth-conditions-q01" }, { "text": "Where do occlusion, weak texture, reflections or transparency make the inferred geometry ambiguous?", "kind": "boundary", "id": "disparity-and-depth-conditions-q02" }, { "text": "Should the agent return an uncertainty interval, request additional views or withhold a depth estimate?", "kind": "action", "id": "disparity-and-depth-conditions-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "No sense is recorded; this answer assumes the radiometric and computational-imaging concept.", "The four-dimensional reduction assumes straight rays through a homogeneous, nonattenuating region, where radiance is constant along each ray.", "Terminology varies across optics and computer graphics, particularly concerning the boundary between light fields and plenoptic functions." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of light field this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Five-dimensional position-and-direction light fields", "Four-dimensional ray-parameterized light fields in free space", "Spectral light fields", "Time-varying light fields" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of light field this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Computational photography, including refocusing after capture", "Novel-view synthesis and image-based rendering", "Depth estimation from variation across viewpoints", "Multiview and light-field displays", "Light-field microscopy" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of light field this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Radiance", "typical_range": "Nonnegative; magnitude depends on the scene and spectral band", "unit": "W·m⁻²·sr⁻¹" }, { "quantity": "Spectral radiance per unit wavelength", "typical_range": "Nonnegative; magnitude depends on the source and wavelength", "unit": "W·m⁻²·sr⁻¹·nm⁻¹" }, { "quantity": "Angular sampling interval", "typical_range": "Acquisition- or display-dependent", "unit": "rad" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of light field this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Insufficient angular sampling causes aliasing and artifacts in refocusing or synthesized views.", "Finite spatial and angular sampling limits recoverable detail; many capture systems trade spatial resolution against angular resolution.", "Camera or microlens calibration errors corrupt ray geometry and depth estimates.", "Occluded surfaces and views outside the captured range cannot generally be reconstructed without additional assumptions.", "A conventional radiance light field does not retain optical phase and cannot by itself describe interference or diffraction." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of light field this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Plenoptic function", "difference": "A common formulation includes position, direction, wavelength and time; light-field representations typically fix or suppress some of these variables." }, { "name": "Irradiance", "difference": "Irradiance integrates incoming radiance over directions with a cosine weighting, whereas a light field preserves directional information." }, { "name": "Electromagnetic field", "difference": "An electromagnetic field specifies electric and magnetic field quantities; a conventional light field specifies radiance along rays." }, { "name": "Depth map", "difference": "A depth map assigns distances to image locations; a light field records directional radiance, from which depth may be estimated." }, { "name": "Reflectance field", "difference": "A reflectance field describes appearance as illumination changes; a light field describes the light distribution for particular illumination conditions." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of light field this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.light-field intend the optical radiance concept, the four-dimensional computational-photography convention or a broader electromagnetic meaning?", "Which authoritative definition should govern the relationship between light field and plenoptic function in this registry?", "Should time, wavelength and polarisation be optional extensions within this entry or relations to neighbouring models?", "How should fields in participating or refractive media be represented without implying the free-space four-dimensional reduction applies?", "Which task-specific validation criteria should determine acceptable view synthesis, refocusing and geometric inference?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 16, "questions": 27 } }