Capabilities · Approved index

Evidence before labels.

This index will connect each approved capability claim to the architecture component it exercises and the evidence that supports its scope. A capability appears only after public review. See the architecture components →

3 records shown

production-qualified · verified · active

Five bounded coding lanes (report-derived production qualification)

The current source report describes five bounded repair lanes as active production and reports 5/5 reuse-only checks. This site records that attributed qualification summary; it is not a fresh rerun of the lane tests or a claim of arbitrary repository mastery.

2026-10-31T00:00:00Z · Research area unclassified · Architecture link unassigned

Evidence: Five bounded coding lanes have report-derived production qualification

production-qualified · verified · active

RECAP bounded language generation (reported active; qualification inherited)

The source report describes seven bounded RECAP generator families and one bounded recursive composition record as present in active production. The qualification measurements are inherited from ancestor tests and were not rerun for this release; this is not a claim of unrestricted language generation.

2026-10-31T00:00:00Z · Research area unclassified · Architecture link unassigned

Evidence: RECAP generates bounded language and composes existing families

demonstrated · verified · active

Candidate qualification and model-governance controls

LARI’s documented workflow distinguishes isolated candidates from active production. A current receipt verifies one narrowly scoped fail-before/pass-after, reload, and exact-ablation lifecycle while production state remains read-only. This is evidence about those controls, not a guarantee that every candidate, rollback, or state path is universally safe.

2026-10-31T10:00:58.566Z · Research area unclassified · Architecture link unassigned

Evidence: Qualification keeps a verified candidate distinct from production

Discuss this page

Read and join this page’s discussion here. Sign in to GitHub when you want to reply or react.

Loading discussion from GitHub…