Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 5 Nov 2026. What's built · Install 0.3.0
jadpo
ReferenceErrors

ErrorsTools · rule

acceptance.invalid

Acceptance file isn't written as an acceptance.

Area 14, Tools; not declinable; the next step is usually the agent's.

An acceptance file holds one acceptance { changes: { ... } }, each entry subject: Kind.change as jadpo check's message gives it, with the reason on a /// line above acceptance. Here the reason was written as a member instead:

example
acceptance {    reason: "No client shows the tag"    changes: {        main.MemoView.tag: ApiChange.output_field_removed    }}
jadpo checkcheck failed: 1 error, 2 files

error An acceptance holds only changes:

--> acceptances/20261030T1400_remove_memo_tag.jadpo:2:5

  |2 |     reason: "No client shows the tag"  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not part of an acceptance
reason
An acceptance is one acceptance { changes: { ... } } per file, each entry subject: Kind.change copied from the compiler's message, with the reason on a /// line above acceptance.
next
Remove it, and put the reason on a /// line above acceptance (agent)
rule
acceptance.invalid
help
https://jadpo.dev/docs/errors/acceptance.invalid
before
none, so acceptances aren't judged: not a git repository

Markdown for agents: /docs/errors/acceptance.invalid.md.Built from Jadpo main at aee2e8f.