[RefImpl] Expectations for Guardian implementations #252

Target runtime or language

Python, Go, Rust, TypeScript

What this proves

Four pull requests now add or rework a Guardian: #229 (TypeScript), #169 (Go), #187 (Rust), and #183 (Python). Each one read the porting issues (#86, #87, #88) differently, because those issues are one sentence long and name no acceptance criteria. The result is four implementations that cannot be reviewed against each other and cannot yet talk to each other.

I propose a document that states what we expect from each maintained Guardian reference implementation. It defines rules for architecture, message signing, logging, concurrency, and use of the AGT runtime, along with verification and acceptance criteria for each implementation.

I will open a pull request with the text, and the discussion can happen there.

Do you intend to implement this yourself

Yes, I want this assigned to me

Current Priority Scope

Feeds the runnable Guardian reference implementation