Plans and frontiers
A KAR plan declares the evidence requirements for one proposition. The evaluator does not invent missing requirements and does not relax the ones you supplied.
The typed frontiers follow the plan:
| Frontier | Evidence it collects |
|---|---|
| Support | Material the plan treats as supporting the proposition |
| Opposition | Material the plan treats as opposing it |
| Qualification | Exceptions, limits, and conditions |
| Temporal / applicability | Time and scope limits |
| Authority | Who or what the plan treats as authoritative |
result.frontiers on the contracts demo carries both support and opposition identifiers. KAR keeps both. Dropping opposition because it lowers a rank score is a ranked-retrieval behavior, not a KAR behavior.
result.certificate.roots carries the frozen roots for kar-1-research-1. Verification recomputes them. Changing the plan changes the evaluation. Citing a result from composition does not change KARRoot.
Plans are data. The MCP server's knolo_kar_evaluate, in the published @knolo/mcp@0.2.0 server, accepts an inline plan object of at most 65536 UTF-8 bytes. It does not accept Domain Pack template names. The @knolo/mcp@0.1.0 server does not expose that tool. See MCP.