Formal protocol specs

Open
#33 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
haskell, rust
Domain
api, documentation

Research direction

No files, tests, or entry points are named. Start by examining the existing KES agent protocol implementation and identify the messages, wire behavior, and security requirements a Rust client must rely on; done means those protocols are captured in a sufficiently formal specification.

Written by the indexing model from the issue text.

Description

backburner documentation enhancement

It may be necessary to implement KES agent clients in Rust; for that, we need a sufficiently formal specification of the KES agent protocols.

Dominant language
Haskell
Stars
2
Forks
13
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IntersectMBO/kes-agent

All issues in IntersectMBO/kes-agent

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.