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
227 findingsTop findings
all statePrussian blue analogues are open-framework metal-cyanide compounds M[Fe(CN)₆] (M = transition metal) with face-centered cubic lattice geometry that permits reversible, rapid sodium-ion insertion into interstitial sites without major structural distortion.
0.95vf_62e47d4f7304e1f0Sodium raw material (sodium carbonate) trades at ~$0.05/kg versus lithium carbonate at ~$15/kg, a 300× raw material cost differential as of mid-2025.
0.95vf_0df89b3a1b6ef320Lithium production is geopolitically concentrated (70% from Australia/Chile/China); sodium can be extracted from seawater or ubiquitous trona deposits, enabling distributed global supply independent of politically sensitive mining.
0.94vf_501ad16ffa201ac5inspect 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
227 findingsSodium is the 6th most abundant element (~2% of crust) and 2000× more abundant than lithium; sourcing from seawater/brine/rock salt is geographically unconstrained and scalable without specialized mining infrastructure.
0.93vf_730582f2c64fcbcbShowing 12 of 227. Clone the full state with vela registry pull vfr_abee720484ca4031.