Skip to content

docs: finalize endorsement API design docs after the enable PR #264

Description

@Storm1289

Final step of the endorsement API implementation, after #246 (the enable PR). Once the API is shipped, convert the design docs from their plan format into normal documentation of the endorsement API.

What to do

docs/design/endorsement-api/ is currently written as a design plan (overview, per-part design, PR sequence, open items, risks). As the last step, rewrite it into reference documentation of the shipped API:

  • drop the plan/rollout framing - PR sequence, "dormant / for now / provisional" caveats, open items, risks;
  • describe the API as it actually exists - service, messages, errors, security, configuration;
  • reflect the settled details: the final serve source (fabric-x-common) and the final Execute / proposal handling.

Docs-only; no code.

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions