Download the PHP package fissible/verdict-console without Composer

On this page you can find all versions of the php package fissible/verdict-console. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package verdict-console

Verdict Console

Human-in-the-loop approval runtime and operator UI for Laravel AI agents governed by Verdict.

Status: pre-1.0, headless. 0.1.0 ships the headless approval round trip — pause → authorized human decision → receipt transition → exact resume → execute at most once — driveable from your own code with no UI. Notifications, evidence projections, and the Blade / Livewire / Filament surfaces are specified in docs/design/0001-verdict-console-design.md and land in later minors; build order is tracked in MILESTONES.md. Substantial decisions are recorded in docs/adr/; start with ADR 0001, the approval-surface contract — including the rule that a Verdict deny is never approvable from the console.

What it is

Verdict decides at the tool boundary and records evidence; Laravel AI runs the agent and persists conversations. Neither owns the tissue between them and a human. Verdict Console is that tissue plus the operator surfaces: it turns a Verdict require_confirmation into a screen a person acts on, drives the receipt → resume round trip, and presents what Verdict recorded.

It never decides (Verdict does), never persists conversations (Laravel AI does), and is never a second authorization authority. It owns the approval workflow and the UI.

Scope boundary (read first)

The receipt-backed approval loop exists only for Verdict BoundTool on an agent using Laravel AI's RemembersConversations concern with a real (non-fake) gateway. Non-BoundTool approvals are observable but not Verdict-drivable. See design §3.

Verdict require_review is a separate, gated review lane: it has no receipt and does not resume an agent. Its durable review substrate shipped in Verdict 0.15 (#297, ADR 0035) with a ReviewStatusReader read API; this package's reviewer-queue surface is tracked in #48, and until it lands review items are not exposed here and decision evidence is not an inbox.

Package family

Install only the presentation stack you render in; all three sit on one headless core.

Package Contains
fissible/verdict-console (this repo) Headless runtime + publishable Blade stubs (a working UI on install).
fissible/verdict-console-livewire End-user chat with inline approval cards.
fissible/verdict-console-filament Operator console (approval queue, evidence browser, alarms).

Installation

Migrations are published, not auto-loaded: a console table must not appear on migrate without the host asking for it. Publish only the config or only the migration with --tag=verdict-console-config or --tag=verdict-console-migrations. Then bind the two host seams the round trip needs — ResumableAgents (how to rebuild your agent from a stable key) and, if your conversations carry a participant, ConversationParticipants — and define the approve-verdict-action Gate ability: the shipped authority fails closed until you do.

Requirements

Development

License

MIT — see LICENSE.md.

All versions of verdict-console with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
illuminate/console Version ^12.0||^13.0
illuminate/contracts Version ^12.0||^13.0
illuminate/database Version ^12.0||^13.0
illuminate/routing Version ^12.0||^13.0
illuminate/support Version ^12.0||^13.0
illuminate/view Version ^12.0||^13.0
fissible/verdict Version ^0.18
laravel/ai Version ^1.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package fissible/verdict-console contains the following files

Loading the files please wait ...