Skip to content

Collect incident evidence without SSH

A caller requests read-only diagnosis and receives a finite evidence stream; an Agent or A2A adapter is outside this fixture.

The problem

Diagnosis often starts by giving a person or agent a shell, which is much broader than the task.

What gets published

Allowlist the service, cap lookback at 60 minutes, and stream at most ten ordered samples.

What stays local

Observability adapters, machine access, and remediation authority.

Business data crossing the call boundary

Bounded diagnosis, finite samples, caller and invocation identifiers.

What this shows

People and future agent adapters can inspect the same formatted diagnosis before any remediation is approved.

What it doesn't prove

This fixture only collects read-only evidence; it excludes remediation, approval, rollback, and A2A task planning.

Public source evidence for this case

Evidence level
Source layout and declarations are anonymously inspectable
Pinned public EasyRemote revision
44c768ca26d0f92a5ab9d1d03342895c29c27dc6
Public inspection
Public inspection
Expected check
Required files, Python syntax, and @node.register declaration are checked without installing dependencies
Runtime invocation
Not established by this source fixture; record separate discovery, Invocation, and terminal Receipt evidence

Run in a compatible source workspace

This Provider/Client walkthrough requires compatible EasyRemote, EasyNet-Cli, and EasyNet-Axon sibling source checkouts, a compatible Hub, and a paired, running Runtime. The source is public; clean installation from public packages is not yet verified. Technical Alpha offers guided setup. Use the pinned EasyRemote revision below; this page does not pin the other components. Runtime admission still determines whether the caller may execute the function.

# From EasyRemote revision 44c768ca26d0f92a5ab9d1d03342895c29c27dc6
cd gallery/projects/03_a2a_incident_copilot
# Terminal 1
uv sync --frozen
uv run python node.py

# Terminal 2 (same project)
uv run python client.py
Connect your own function

Read the setup first. You need compatible sibling source checkouts, a compatible Hub, and a paired, running Runtime. Technical Alpha offers guided help; public-package clean installation is not yet verified.

All source casesRequest technical alpha