Skip to content

gage 0.1.0

Choose a tag to compare

View all tags
@warewithall2 warewithall2 released this 18 Oct 17:59
v0.1.0
9ecb517

Hand context between agents — files, prompts and decisions — with a trust boundary that survives the hop.
When one agent hands work to another, nothing normally says who wrote it or whether it can be trusted. gage wraps that handoff so the receiving agent is told who signed it, whether you have ever confirmed that person, and that nothing inside carries any authority.

Install

cargo install gage

That works anywhere Rust does, and is the recommended route.

A prebuilt Linux x86_64 binary is attached below with its SHA256SUMS. Verify it before running it:

sha256sum -c SHA256SUMS

There is no macOS binary in this release. A darwin-arm64 build needs a Mac reachable over passwordless SSH to build on, and there isn't one yet — cross-compiling is not an option here because rustls brings a C dependency, and a binary built where it runs is one fewer thing to be wrong about. macOS users should use cargo install gage for now.

What the attached binary reports

gage --version prints gage 0.1.0 (b75f84f).

That is deliberate and worth explaining, because provenance is the thing this project is selling. The binary was built from b75f84f, while this tag points at 9ecb517. The three commits in between are cargo fmt across the tree, the clippy fixes behind the new -D warnings CI gate, and this site's landing page — formatting, lints and documentation, with no change to a line of behaviour. Both commits are in the history, so the binary can still be tied back to the exact source it came from.

Verification

At b75f84f, the commit the attached binary was built from, the full self-check was green — build, unit tests, attack suite and the viewer end-to-end leg, all in one run:

  • 708 adversarial checks, 0 failed (tests/attacks.sh)
  • 108 unit tests, 0 failed
  • viewer end-to-end: ok

Those checks are the project's substance rather than a formality: most were written after an attack worked in testing, and each pins the specific thing that went wrong — nonced fence markers so payload text cannot close the trust frame early, trust computed by the receiver instead of carried in the manifest, replay refused on a witness rather than an id, and the auto-accept budget keyed on a parent the receiver itself sent.

At this tag, cargo clippy --locked -- -D warnings and cargo fmt --check are also clean, and CI now gates both.

Where this is

This is the first release, and it is early software. The honest way to try it is docs/first-tester.md — a twenty-minute packet written from the other person's side, which needs two people because every step after the install is two-sided.

Assets 4
Loading