Engine layer

Frontier index.

The frontier index lets Canopus resolve route slugs to Vela frontier ids. It lets the platform resolve a human slug in local mode or hub mode. It is derived routing state, not the canonical frontier record.

slug entries

unique vfr ids

shared ids

hub

data mode

yes

hub url

record boundary

canonical

Frontiers are the record

Use the frontier pages for findings, sources, links, reviews, proof state, and correction history.

browse frontiers →

engine boundary

derived

The index is a resolver

This table resolves slugs to vfr ids so Canopus can fetch the same frontier from disk or the hub.

open capabilities →

trust boundary

not authority

Proof lives elsewhere

A route match does not prove freshness or acceptance. Proof packets, signatures, and traces remain under Trust.

inspect trust →

Resolver contract

The frontier index connects Canopus routes to Vela ids. It is useful because it is rebuilt from known records.

derived index

The resolver is not a second record

A slug match names where to go. It does not decide freshness, acceptance, or proof status.

record state

The vfr id points back to frontier state

Finding bundles, evidence, links, events, signatures, and proof packets remain attached to the frontier.

alias group

Shared ids are route aliases

Multiple slugs can resolve to the same content-addressed frontier without creating duplicate authority.

review path

Trust checks live under proof

Open the frontier or Trust surface when the question is whether the state is accepted, signed, or current.

Derived index freshness

Derived indexes help orientation. They stay below accepted frontier state and need visible source, freshness, and review boundaries.

surfacefreshnesssourceinputsboundary

frontier route resolver

frontier index build artifact

freshness

unknown · not declared

source

site-next/lib/frontier-index.json

inputs

28 slug entries · 27 unique vfr ids

boundary

hub route resolutionderived resolver, not frontier proof state

Shared frontier ids

Some routes intentionally resolve to the same content-addressed frontier id. This is route aliasing, not a second record.

index alias group

2 routes

vfr_5c602c9ef6bcbcd0

brain-tumor-translation, gbm-egfrviii-translation

Resolved routes

The table shows the first 18 entries in the generated route index. Open a frontier to inspect the record.

search index

route slug	vfr id	record
`ai-alignment-evaluations`	`vfr_14b9f65ab4037bac`	open
`alzheimers-bbb-dysfunction-delivery`	`vfr_bbbd20260507c001`	open
`anti-amyloid-translation`	`vfr_5076e7b3ff8e6b0f`	open
`antimicrobial-resistance-evolution`	`vfr_74a5680d270a118f`	open
`brain-tumor-translation`	`vfr_5c602c9ef6bcbcd0`	open
`cancer-immunotherapy-translation`	`vfr_416f768132dc85d3`	open
`co2-electroreduction-catalysts`	`vfr_d474cf297c99b0ce`	open
`crispr-off-target-fidelity`	`vfr_f5d2f2e0e35df366`	open
`early-ad-biomarker-calibration`	`vfr_a22c9022674a2304`	open
`enhanced-rock-weathering-mrv`	`vfr_ad7fab723e9a51c9`	open
`erdos-problems`	`vfr_2a00e138907c0c3e`	open
`exoplanet-biosignatures`	`vfr_8416da9690da6f1b`	open
`fusion-confinement-progress`	`vfr_30ac47d7e1277ba8`	open
`gbm-egfrviii-translation`	`vfr_5c602c9ef6bcbcd0`	open
`gw-transient-interpretation`	`vfr_44f1a004166ef85e`	open
`hubble-tension`	`vfr_9caed35d1222c706`	open
`open-targets-target-evidence`	`vfr_68680cce65ade89b`	open
`open-transformer-circuit-evidence`	`vfr_c94f4f79b4e341ad`	open