Integrations and peers

The capability register, peer links, CodeBook as a peer (station gates, traces, outcomes, proposals) and MadeBook as a peer (evidence, governance).

• The capability registerEvery adapter operation EvalBook has or will have, with a status, the documentation it was built against, the version tested and its evidence. A named integration is a requirement, not a claim of support.
• Peer linksHow an EvalBook project is linked to a CodeBook or MadeBook workspace, how every call between the products is authenticated, signed and made idempotent, and what the outbox and inbox guarantee.
• CodeBook as a peerWhat crosses between a CodeBook factory and a linked EvalBook project — a station gated on a suite, runs exported as traces, outcomes told to EvalBook, and proposals that arrive as cards — and the messages behind each.
• MadeBook as a peerHow an EvalBook report becomes evidence on a MadeBook pull request — re-fetched and re-hashed, trusted only as far as its assurance — and how EvalBook asks MadeBook before it changes protected configuration.