v0.3.0: verifier evidence and measured outcomes
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 20/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Tranquilla
- Stack tecnologico
- playwright, typescript
- Ambito
- testing-qa
Direzione di ricerca
The issue points to the full plan in the usabl-plans repository at 09-verifier-evidence-and-outcomes.md; start by reading that plan and the repository's existing gate and voicing-lane entry points. The scope spans six evidence and measurement mechanisms plus wiring the voicing lane, and work is held until v0.3.0 opens. Done means implementing the plan while preserving the stated verdict and receipt invariants.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Tracking issue for the v0.3.0 verifier work. The full plan is held in the
usabl-plans repository (09-verifier-evidence-and-outcomes.md); this issue records
the scope so it is not lost. No work starts until v0.3.0 is opened.
Scope
v0.3.0 extends usabl from a gate that proves the present into one that also
publishes evidence about its own sensitivity and measured outcomes. Six
mechanisms, plus wiring the voicing lane:
- Task-start proof brief: a machine-readable brief an agent reads before a task,
declaring what must be proven and what counts as done. - Sensitivity evidence: a mutation catalog and runner that inject declared
defects and show the gate detects them, with an attestation and two
sensitivity levels. - Published Orca calibration: compare predicted announcements against Orca on a
fixed corpus, with a calibration attestation, a promotion rule, and staleness
handling. - Observed barrier-days: a ledger measuring how long real barriers persist, as
measurement only, with no verdict and no receipt. - Evidence-bound assistive-technology docs: publish AT behavior docs bound to
the evidence that produced them. - Agent self-correction study: measure whether agents repair barriers when the
gate tells them what is wrong.
Plus: wire the voicing lane, which is built, exported, and currently unwired in
v0.2.0.
Non-negotiables carried from the engine
The gate stays the only verdict authority. Measurement surfaces mint no verdict
and no receipt. Honesty invariants do not flex: a wrong guess is a gap or a
refusal, not a verdict.
Status
Held for v0.3.0.
- Lingua principale
- TypeScript
- Stelle
- 0
- Fork
- 0
- Merge medio
- 2h 48m
- PR unite (30g)
- 8
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di usabl-dev/usabl
-
area: engine bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
-
Stop hook allows a stop on an unknown verdict, and the self-check prints IDLE for a null verdictApertaarea: assistants bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
area: engine bug security
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Overlay: browser context failures are counted per plugin, not per browser, and close is not sharedApertaarea: overlay bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
-
area: engine enhancement performance
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Tutte le issue di usabl-dev/usabl
Issue simili
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
cloudscape-design/components#5184 ·
I maintainer di solito rispondono entro 2 giorni
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
JarX-Concepts/react-native-platform-components#130 ·
I maintainer di solito rispondono entro 1 giorno
-
fix(api): optimize-for-web /preview outer catches miss asDecoderOutOfMemory on V8 OOM and SIGKILLApertaarea: backend bug priority: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
snapotter-hq/SnapOtter#3773 ·
I maintainer di solito rispondono entro 1 giorno
-
ai-driven-qa ux-audit
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
linagora/twake-contacts-frontend#386 ·
I maintainer di solito rispondono entro 1 giorno
-
git: README should state plainly that without --repository every reachable repository is in scopeApertadocumentation server-git v2
Difficoltà 1/5 1-3 ore Idoneità per principianti 84/100
modelcontextprotocol/servers#5225 ·
I maintainer di solito rispondono entro 1 giorno