docs: cover ke-extraction and ke-ownership across the integrator site - #109
Conversation
…sequence at the gate
There was a problem hiding this comment.
Risk: low. Approved: docs-only integrator-site coverage of existing ke-extraction and ke-ownership facts; Cursor Bugbot and Cursor Security Agent were not present after the first poll, so those signals were skipped, and no other policy requires human review. No reviewers assigned.
Sent by Cursor Approval Agent: Pull Request Router and Approver
|
Dismissed because a newer commit was pushed; Greptile will re-review the current head.


Summary
The integrator site now documents the two optional KE capability families the protocol ships. The connect pages already carried their remote face; the in-process half was missing, so a reader of the site alone could not learn that either family exists.
ke-extraction— in-process surfacereference/ops: new optional-op section withExtractRequest/ExtractResponsefield tables, the provisional-only admission rule, therun_idecho, and theextractversusextract→promotedistinction;Scopeselector gains theviewpointrow.how-to/orchestrate-ops:orchestrateExtract(ports, request, runExtractor)in the orchestrator roster plus a worked example of the standaloneExtractionPortand the injected async extractor.how-to/implement-adapter: ake-extractioncapability row and anExtractionPortsubsection beside the other optional families.packages/quick-start: orchestrator and port naming in the integrator path.ke-ownership— governance factsreference/data-model:KnowledgeEntry.ownerandKnowledgeEntry.disclosurerows plus an ownership-governance section stating the exact-matchowner-privaterule againstScope.viewpoint.reference/protocol: the capability registry now lists all eight flags; the schema inventory is corrected to 34 committed schema files (2 common + 10 data + 16 ops + 6 connect) with the 21-file baseline subset stated beside it.explanation/conceptsand the home page: bothke-*flags named.explanation/connectandhow-to/multi-peer-routing: the two remote capability gates (anextractinvoke needs negotiatedke-extraction; a viewpoint-bearing Scope needske-ownershipon top of its row capability), each linking the connect reference; the native-binding and C/C++ overview pages point at the extraction surface.Redundancy trim (bounded)
Four page-to-page restatements were replaced by links to the owning page: the
explanation/connectopening paragraph, theconnect-remote-adapterenvelope-authentication bullets, the duplicated walkthrough infirst-connect-session, and a restatedTransportsentence inintegrate-remote-adapter. The trimmed tutorial still walks its own goal end to end.Every page was updated in EN and ZH together.
Verification
node tooling/docs/twin-parity.mjs— 24 twin pairs, 0 heading-structure mismatchespnpm docs:build— cleannode tooling/docs/deadlink-check.mjs— 49 pages, 2785 anchor links and 68 fragment links, 0 dead, 0 brokenRequest Changes(a capability-table shorthand that invited a wrong adapter choice) plus two approvals; the finding and one suggestion were fixed and re-validated, no residual left openDeferred (tracked on the project roadmap)
WsTransportandhost.cppbodies out of their how-to pages into committed examples