Cyan Eclipse Darkseal
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ECLIPSE_DARKSEAL_STATE | Yes | The record store path. | |
| ECLIPSE_DARKSEAL_SURFACE_KEYS | Yes | Executing-surface channel keys as JSON; surface-held in production. The keys in `keys/` are test fixtures only. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| darkseal_seal_defaultsC | Seal a flow's default-state vector element by element at traversal start, as captured by the executing surface's own witness module: element class, identity as presented, and default state as rendered, across checkboxes, toggles, radio/plan selectors, and continuity switches. Bundles from any non-executing source are rejected on provenance. The check is free. Darkseal seals the state the flow started in — every pre-ticked add-on, pre-chosen plan, and continuity toggle, element by element — at the moment your agent entered it. If a charge began as a default you never chose, the sealed record names the element it began as, and anyone can recompute the verdict from the record itself. |
| darkseal_diff_outcomeB | Diff the principal's own confirmation and charge artifacts (held as digests) against the sealed defaults and mint the verdict: a charge or binding term that began as a sealed pre-selected element verdicts PRESELECTED-AND-CHARGED naming that element. The check is free. |
| darkseal_get_verdictC | The full verdict record for a capture: verdict, charged element names, grammar version, coverage statement, separation marker, receipt refs. The check is free. |
| darkseal_checkC | Counterparty view: the verdict class and the names of charged elements only. The check is free. |
| darkseal_recomputeB | Recompute a verdict from an exported capture plus the element grammar version plus the outcome artifacts, with no service state. The check is free. |
| darkseal_export_capturesB | Export a sealed capture (element states + seal) with the receipt chain head and grammar version, for independent recomputation. The check is free. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The capture-side tools (seal_defaults, export_captures) are distinct, but four of six tools (diff_outcome, get_verdict, check, recompute) all revolve around producing or reading a verdict. The descriptions differentiate them (mint vs. full record vs. counterparty-limited view vs. stateless recompute), but the boundaries are subtle and an agent could easily pick 'check' when it needs 'get_verdict' or vice versa.
All names share the darkseal_ prefix in snake_case, and most follow a verb_noun shape (seal_defaults, diff_outcome, get_verdict, export_captures). The bare 'check' and 'recompute' break the noun pattern slightly, but the set is otherwise predictable.
Six tools is well-scoped for a seal-and-verdict protocol: capture, diff, retrieve, counterparty view, recompute, export. Each appears to earn its place with no filler.
The surface covers the full lifecycle from sealing defaults through verdict minting, retrieval, counterparty disclosure, independent recomputation, and export. Minor gaps exist (no listing/enumeration of existing captures and no revocation or deletion of a seal), but core workflows are covered.