NIVQRA Authority Review
A skills-only authoring package. You describe the authority you intend to delegate to an agent; the package reviews what you supplied and writes it up as an inactive draft with the gaps marked.
Drafts are labelled DRAFT · NOT ACTIVE. Test cases are labelled NOT RUN. The package has no live access, makes no decisions and enforces nothing.
A — What you provide
- Mandate fields
- You supply the mandate values yourself: a monthly ceiling in EUR, a per-action ceiling, the actions in scope and the review threshold above which a human must approve.
- Provenance for each field
- Each supplied value is recorded with a supporting quote or source location. A value without supporting evidence is flagged for human review; the package does not invent a source.
- Missing and conflicting inputs
- The package flags fields that are absent and fields that contradict each other. Unknowns are left blank rather than filled with a plausible number.
B — The four outputs
- Inactive JSON draft
- A machine-readable mandate draft, labelled DRAFT · NOT ACTIVE. It is a document, not a configuration: nothing reads it, nothing enforces it.
- Permission matrix
- A table of proposed mandate fields, limits, owners and their supporting evidence. It records the proposed boundary; it does not calculate live permission decisions.
- Readable report
- A plain-language review of the drafted boundary, its provenance, its gaps and its contradictions.
- Acceptance-test specifications
- Written test cases for the drafted boundary, labelled NOT RUN. The package does not execute them against any system.
C — Worked example
A fictional example, used only to show the shape of the output: a Research Agent with a ceiling of €500 per month, €20 per action, and human review required for anything above €10.
- €500
- €20
- €10
- left blank
The agent, the figures and the thresholds above are invented for illustration. Unknown fields stay blank in every output — the package does not guess a value.
D — How it runs
The package is a set of skills. Your existing host account handles the conversation and holds the files it creates; there is no separate application to sign into.
Python 3 execution must be available in the host environment for the compiler step that produces the JSON draft and the test specifications. Without it, the written review is still produced but the compiled artifacts are not.
A public directory listing is not yet available, so there is no install link on this page.
E — Limits
- No live authority, no execution and no enforcement of any kind.
- No payment execution and no funds movement.
- No certification, accreditation or validated runtime.
- No API, and no workflow data transmitted to I.O.V by the package.
- Outputs are drafts for you to review, not decisions.
F — Package pages
Provided by I.O.V · John Izaguirre.