Repository navigation
Guardana Control 0.7.0-alpha
Pre-releaseAn agent runtime's OpenTelemetry GenAI traces can now be imported as
observations. guardana-control observe import keeps what each span reports
was done, by which source, when and how it ended, in an observation log;
observe export writes that log in the evidence export's shape. The record,
guardana.control.observe.v1alpha1, is outside any compatibility promise; it
keeps no prompt, output, argument or result, and the plane never reads it. A
call that carries W3C trace context records its trace and span ids, so its
evidence trail can be joined to the runtime's traces. On upgrade: a
configuration with a negative duration no longer loads, and run now exits 1
when it stopped uncleanly. An audit of the whole tree before the release
fixed defects, among them: an upstream's failure reached the agent and the
log with its endpoint, and any credential in it; a stop closed the evidence
under a call whose agent had dropped its connection, and exited 0; an HTTP
upstream's answer was read whole, whatever its size; a rewriting obligation
could send a call on a resource no decision covered; the approvals store
accepted another account's directory; and the commit gate could stamp a
commit that broke the wire contract. docs/status.md says
what is implemented and what is experimental. Nothing here is a security
boundary yet.
Added
- Observations:
guardana-control observe importreads an agent runtime's
OpenTelemetry GenAI spans (OTLP/JSON, conventions 1.41.0) for one source an
operator describes, keeps what each span reports was done, by which source,
when and how it ended, and appends
it to an observation log;observe exportwrites the log in the evidence
export's shape. The record isguardana.control.observe.v1alpha1, version
0.1, outside any compatibility promise. No prompt, output, tool argument
or result is kept, and reasoning is counted and dropped. An observation is
testimony: the plane never reads one. - A call to the MCP gateway that carries W3C trace context in
_meta.traceparentrecords the trace id and the caller's span id in its
envelope'strace_idandspan_id, so a trail can be joined to the agent
runtime's traces. A missing or malformed value leaves both empty and changes
nothing else.
Changed
- The plan follows ADR-0039:
MCP is one channel of several. The next milestone is one task under
supervision across two channels, the plane and an agent runtime's
OpenTelemetry traces, with a coverage map, findings, a local notifier and a
stop of one run, before any public SDK. Extensions are planned as separate
programs speaking versioned data contracts. The README and the website
describe this plan, markedplannedwherever nothing is built yet. - The website's home page draws its three diagrams as cards and arrows in
text, readable on a phone, instead of animated scenes and flowcharts. - The website's header stays on one row on a phone and shows the newest
release, whichmake docs-gentakes from this file. Documentation pages get
a menu above the content on narrow screens, and a wide table scrolls inside
itself instead of breaking words.
Fixed
- A stateful listener near its
listener.max_sessionscap no longer refuses
an open while the previous open's answer is still being written: a session
whose answer has begun is counted once, not twice. - The gateway's configuration refuses a negative value for every duration
key and names that key in the error.approvals.ttl,
approvals.retry_after,export.linger,export.backoff,
export.max_backoffandlist.ttlaccepted a negative value before, and a
negativepolicy.max_stalewas refused under another key's name. policy renewholds the signer floor directory's lock from the raise of
the floor until its statement is written, so two renews of one bundle can
no longer leave the older statement in--outwhile the floor holds the
newer. Renews under different floor directories are not ordered. Waiting
for the lock, opening included, ends after 10 seconds.- An evidence line that does not decode is refused naming where it went wrong,
never quoting the value or member name it held, so a sender cannot put a
credential into the collector's log through a malformed line. guardana-gateway doctornames a command upstream's program and how many
arguments it takes, never the arguments, which can carry a credential.- The approvals store refuses a directory another account owns, as every
other store already did, and a record that repeats a member. A record, a
hold journal entry or a file whose filing failed after it was linked is
unlinked again. An answer the plane spent before the failed filing is
reported as filed. One already gone when it is unlinked is reported as of
unknown outcome, never as not filed, andapprovals approveandreject
then say to list before answering again. - The evidence spool refuses a segment or its quarantine that another account
owns or the group or others may write, keeps every quarantined id so a crash
cannot quarantine a record twice, syncs a repair before it continues, and
refuses an append once its sequence is spent. The trail file's recovery cuts
only a tail its writer could have left, and an export reads the line that
would cross its byte bound no further than the bound. - The
evidence-reportexample refuses an export past 100 000 records and
its trailer or 64 MiB after its header, and a trailer without
scanned_bytesor with adedup_scopeother thanexport. The demo's
servers do not start on a journal that is a link, a pipe, a file with a
second name, or a file another account owns or may read or write. - The MCP gateway answers an upstream failure that is not the upstream's own
wire error, on a call, a read, a prompt or a forwarded list, with-32603
the upstream did not answer, and logs a refresh failure by what failed:
neither the agent nor the log sees the endpoint, which can carry a
credential. A transport failure is printed and logged by its operation and
a cause its error's type gives, never by its text, which can quote what the
upstream echoed of the request, the Authorization header included; the OTLP
exporter's log does the same for the collector. Run and doctor also
withhold a refusal that quotes an endpoint's userinfo, raw, decoded or as
the Basic credentials sent, its query or its fragment. An HTTP upstream's
answer, other than an event stream, is read no further than 16 MiB, so an oversize answer fails the call instead of
being held whole. - A rewriting obligation that changes the member a tool's
resource_from
reads, or anything inside it when it is an object, a list or a boolean,
aborts the call withOBLIGATION_NOT_UNDERSTOODinstead of sending
it. A call nothing classifies is held to the rest of the envelope contract,
and each name, client tag or resource id past the string bound is left
off, so the proposal can still be recorded. - A closing record the sink refused no longer forgets the held request, an
OTLP request of many records is decoded in one pass, and a collector's
answer of exactly 64 KiB is read as whole. guardana-gateway runanddevstop admitting calls when they stop and
wait for every call admitted before, one whose agent dropped its
connection included, on HTTP and stdio, and exit 1 when one was cut, a
closing record was lost, even after the plane closed, or the plane did not
close;doctorfails itsclosecheck, and a scenario whose
plane did not stop cleanly could not run. The configuration, a scenario
file and the trail it reads are read only as regular files, so a named pipe
no longer holds them. A test case refusesnullfor a member that takes a
string, a boolean or a list.
Image: ghcr.io/guardana/control-gateway@sha256:c29b812a9bf2db998fd0d2e825e51463636beb904e0049bc584159b0190c5ada