Skip to content

Guardana Control 0.8.0-alpha

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 06 Oct 07:20
· 217 commits to main since this release
Immutable release. Only release title and notes can be modified.

One agent run can now be checked against the procedure it was meant to
follow. guardana-control supervise reads a plane's evidence export for a run
an operator opened, and the observations the agent's runtime reported for that
run, and writes findings that cite both. guardana-control notify hands each
alert to a program the operator names, and marks it delivered only once the
program accepts it, so a crash or a failure makes the next run hand it over
again. guardana-control coverage gives each path an operator declares one
state: enforced by a plane, decided but not enforced, observed by a source,
unknown, or not covered; where a source observed a call that no plane's export
records, it says so. None of these commands contacts a plane or changes a
decision, and a finding that rests on what the runtime reported is marked
suspected, not confirmed. An upstream answer that quotes a credential the plane
sends is replaced by a fixed answer from the plane, so the agent does not
receive the credential. On upgrade, two changes: a call that needs an approval
under a run an operator opened is held for the approval, where before it was
blocked; and a call refused as too large records the digest of its over-long
name or resource. Fixes from an audit of this release include: coverage took a
prompt or a resource read through the plane for the plane's record of an
observed tool call, and supervision let the runtime's own report of a step
count as the step. docs/status.md says what is
implemented and what is experimental. Nothing here is a security boundary
yet.

Added

  • guardana-control coverage prints, for each path an operator declares in an
    inventory, whether a plane enforces it, decides it without enforcing it, a
    live source observed it, nobody can tell, or nothing covers it, and a
    standing row for the paths nobody declared
    (ADR-0041,
    ADR-0044).
    It reads the planes' configurations, source descriptors, observation logs
    and evidence exports, and contacts no plane. Against a whole evidence export
    it shows an observed call no plane recorded as a call around the plane, and
    exits 1 for it.
  • guardana-control supervise checks one run an operator opened against a
    versioned procedure, from the plane's evidence export and the observations
    that claim the run, and appends findings with typed references to a
    findings log; guardana-control notify hands each alert to a program of the
    operator's, at least once, keyed on the finding's id
    (ADR-0045).
    Six rules: repeated denial, a step outside the procedure, a deadline, a
    skipped required step, a step out of order, and a run that carried on after
    a failure. A finding resting on what the agent's runtime reported is
    suspected at most, and a skipped step is never confirmed. No plane reads a
    finding, and no finding stops a run. examples/refund-supervision/ runs it
    on a live plane.

Changed

  • An upstream's answer, wire error, listed item or tool definition that quotes
    a credential the plane sends reaches the agent as a fixed answer, never with
    the upstream's text
    (ADR-0042).
    The plane looks for the credentials in its endpoints, headers and proxies,
    and, from 8 bytes, for query values and the variables a command upstream
    receives: as written, percent-encoded, JSON-escaped and in base64. A
    withheld tools/call success says the call ran; a read, a prompt or a list
    answers -31103; a tool whose definition quotes one is never listed. The
    closing record keeps the upstream's outcome and hash, with withheld: before
    its protocol status. doctor names the values too short to scan, and
    /metrics counts withheld answers.

Fixed

  • A call that needs an approval, under a run an operator opened, was blocked
    with EVIDENCE_UNAVAILABLE on a live plane instead of held: the run's expiry
    was judged at the call's first clock reading, which the kernel's later
    reading had already passed. A test clock that never moves had hidden it.
  • An upstream could put the gateway's _meta namespace inside a content
    block, an embedded resource or a prompt message, where it reached the agent;
    it is now stripped from every _meta an upstream's result carries.
  • A tools/list right after a manifest refresh could be answered with the
    list cached from the previous manifest.
  • A call refused as too large records overlong:sha256: and the digest of its
    over-long action name or resource id in their place, so the recorded
    proposal validates
    (ADR-0043);
    both were left empty, which a validating reader refused.

Image: ghcr.io/guardana/control-gateway@sha256:b4ef184ce5b85a08dc1f5443bbfa98c59633f7b9f9efbc97ccd931052937f930