frontiers / frontier
Current answer
No synthesized decision answer has been authored yet. The current reading is assembled from the frontier’s strongest accepted findings, shown below.
Frontier operating path
A frontier is the bounded record object. The record holds accepted state, the engine routes reviewed work back into it, the body renders derived maps, and proof fixes the release boundary.
record
Finding bundles, source records, evidence atoms, typed links, review events, and trails are the canonical frontier record.
open state →
engine
Sources, gaps, attempts, checks, benchmark runs, and reviewable changes return through Workbench and Review before state changes.
inspect review →
body
Graphs, briefs, atlases, and constellations materialize accepted records into navigable bodies. They guide work; they do not become the record.
open graph →
proof
Proof packets, citation packages, source manifests, and release pins make the current state portable and replayable.
open proof →
next action
Open reviewable changes are waiting for checks and reviewer authority before they can change accepted state.
inspect review →
Signals show what can change this record next: review queues, campaign work, benchmark gaps, proof boundaries, contested findings, and event history.
review signal
review waitingOpen reviewable changes need checks and reviewer authority before the record changes.
inspect review →
review signal
never_exportedNo sealed proof packet is present for this frontier. Events can still be inspected, but the release boundary is not frozen.
A frontier is the record. Work enters as gaps, attempts, reviewable changes, checks, and reviews before accepted events update proof, atlases, and constellations.
gapframing
A missing experiment, unresolved contradiction, extraction defect, or stale proof cell worth reviewing.
reviewable changework
A reviewable frontier-state change with affected findings, evidence, rationale, checks, and expected proof impact.
attemptwork
An agent, capability, procedure, system, or human run with input material, declared output material, environment, disclosures, failure state, and cited artifacts.
checkgate
A schema, provenance, contradiction, benchmark, proof, or evaluation result over a reviewable change or release.
Finding types
16 findingsTop findings
all stateDimethyl sulfide (DMS) detected in K2-18b by JWST in 2024-2025 is based on 1-sigma significance, with reanalysis finding no statistically significant evidence for DMS; the detection fails basic standards of evidence for biosignatures
0.95vf_3a1261815f8e7587K2-18b's atmosphere is water-rich and photochemically complex but exhibits no confirmed biosignatures; recent joint-retrieval analysis of NIRISS+NIRSpec+MIRI confirms CH4 at 4-sigma but DMS/DMDS remain undetected
0.93vf_fd9e444420fba21bAbiotic oxygen (O2) can be produced abiotically through CO2 photolysis on terrestrial exoplanets, particularly around M dwarf stars with high UV flux, creating a significant false-positive risk for oxygen biosignatures
0.92vf_7c740d696e578450inspect proof →
reviewgate
A human or authorized reviewer decision over a reviewable change, check, candidate gap, or contested finding.
eventaccepted
A signed, reviewable state transition that changes the Vela-backed frontier record.
releaseaccepted
A citation-ready bundle of source state, proof artifacts, mirrors, and known caveats.
Review state
16 findingsNoise and retrieval degeneracies limit JWST to detecting only the most robust biosignature pairs (e.g., O2 + O3 at ppb levels) on the nearest Earth-analogs; marginal detections of single gases (DMS, N2O) lack sufficient statistical support for biosignature claims
0.92vf_fe494faeae855bf5Showing 12 of 16. Clone the full state with vela registry pull vfr_8416da9690da6f1b.