Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 30 Oct 2026. What's built · Install 0.1.0
jadpo
Reference: Failures

Failures · rule

failure.invalid_outside_construction

Catch-all for rules is used on something that is not a construction.

Area 4, Failures; not declinable; the next step is usually the agent's.

invalid: covers only a construction's rules, never another call's failures or a write's conditions:

example
type Note = Text {}type NoteRefused = Failure {    kind: FailureKind.rejected}type NoteInvalid = Failure {    kind: FailureKind.invalid_value}action check_note(note: Note) fails NoteRefused -> Note {    if (note == "") {        reject NoteRefused    }    return note}action save_note(note: Note) fails NoteRefused, NoteInvalid -> Note {    return attempt check_note(note) {        invalid: NoteInvalid    }}
text
error: `check_note(...)` isn't a construction, so `invalid:` covers nothing --> main.jadpo:20:9   |20 |         invalid: NoteInvalid   |         ^^^^^^^ not a construction  reason: `check_note(...)` fails with the failures its `fails` list names; `invalid:` is the catch-all only for the rules a construction's value can break, never for another call's failures.  next: Remove `invalid: ...`; `attempt` passes `check_note(...)`'s failures on, and `match` turns one into another (agent)  rule: failure.invalid_outside_construction  help: https://jadpo.dev/docs/errors/failure.invalid_outside_constructioncheck failed: 1 error, 1 file

Markdown for agents: /docs/errors/failure.invalid_outside_construction.md.Built from Jadpo main at a707efb.