feat(workers): a seat stores its own answer where the deliberation asks #89

Closed
peersky wants to merge 5 commits from feat/a-deliberation-says-how-it-carries-answers into dev
Owner
No description provided.
- Added Ability for a worker whose task names an addressed deliberation to store its answer and propose the name for it, deriving the subject from the job, its own name and the tree it already speaks on, with nothing presented to use it.
- Added Function deciding where a seat stores, separated from the sending so every reason not to — no request, unknown type, no job, already a name, nothing to store — is covered without a broker.
- Improved Function leaving the answer in the proposal wherever storing fails or is refused, so a storage hiccup costs a larger record rather than a seat's work.
- Added Function encoding a name into one reversible subject token, since sanitising alone is lossy and Unicode-aware, and a job id it passed through un-encoded had every write from that seat silently fall back to inline content.
- Improved Function deriving the seat's put subject to sanitise for identity then encode for the wire, the same composition the serving side decodes with its inverse.
- Added Ability for a policy to set deliberation_type, carried on the request a run submits, so one line of workspace configuration turns addressed storage on for every deliberation the policy starts.
- Added Interface field on the deliberation request, left unset unless the policy says, so the deployment's default still decides for policies that do not.
- Fixed Bug where the store behind read_proposal returned rounds as stored, so under an addressed deliberation every protocol tool handed the model a name where prose belongs, on the worker side of the wire a deployed agent runs on.
- Added Function fetching addressed content window by window through the seat's own reading subject, bounded by the stated size and verified against the digest the address asserts.
- Added Ability for a reader given no serving path to return history exactly as written, and coverage of the fetch refusing forged bytes, surfaced refusals, endless responders and over-serving.
feat(telemetry): a failed task says why
All checks were successful
CI / Dependency Age Check (pull_request) Successful in 4s
CI / Lint & Audit (pull_request) Successful in 1m7s
CI / Spell Check (pull_request) Successful in 6s
Commit Lint / Validate PR Title (pull_request) Successful in 3s
CI / Test (pull_request) Successful in 4m52s
Publish Release / Create Tag & Sync (pull_request) Has been skipped
Publish Release / Publish to crates.io (pull_request) Has been skipped
Publish Release / Publish dry-run (no side effects) (pull_request) Has been skipped
Publish Release / Create GitHub Release (pull_request) Has been skipped
8a80b3c6b3
- Added Interface carrying the head of the failure's rendered chain on the task-failed event, with the provider detail where one exists, since a class alone says a task failed and diagnosis needs the words.
- Fixed Bug where every non-payment failure was classed as a timeout, so parse failures and empty completions wore a label pointing investigation at the clock; the class now comes from the chain.
forgejo-actions changed title from feat/a-deliberation-says-how-it-carries-answers to feat(workers): a seat stores its own answer where the deliberation asks 2026-08-29 05:54:57 +00:00
peersky closed this pull request 2026-08-29 07:01:14 +00:00
All checks were successful
CI / Dependency Age Check (pull_request) Successful in 4s
CI / Lint & Audit (pull_request) Successful in 1m7s
CI / Spell Check (pull_request) Successful in 6s
Commit Lint / Validate PR Title (pull_request) Successful in 3s
CI / Test (pull_request) Successful in 4m52s
Publish Release / Create Tag & Sync (pull_request) Has been skipped
Publish Release / Publish to crates.io (pull_request) Has been skipped
Publish Release / Publish dry-run (no side effects) (pull_request) Has been skipped
Publish Release / Create GitHub Release (pull_request) Has been skipped

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
release
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
peeramid-labs/quorum-rs!89
No description provided.