Skip to main content

Crate day_script_protocol

Crate day_script_protocol 

Source
Expand description

Dayscript’s shared wire protocol and on-disk format.

This leaf crate depends only on serde, JSON and YAML. The CLI and embedded engine share request/reply types and document validation without linking any UI, localization or transport.

Re-exports§

pub use ids::EvidenceClass;
pub use ids::IdCatalog;
pub use ids::IdDeclaration;
pub use ids::IdEvidence;
pub use format::FailurePolicy;
pub use format::FormatError;
pub use format::Script;
pub use format::ScriptStep;
pub use format::steps_from_yaml;
pub use format::steps_to_yaml;

Modules§

format
Canonical flow: documents. Transport, project expansion and execution stay with callers.
ids
Compiled declaration catalogs and family-level dayscript evidence.

Structs§

MemorySample
MemorySize
A memory threshold in bytes. Accepts an integer byte count or a size string; serialization uses bytes, so the wire is independent of the author’s unit spelling.
Reply
Request

Enums§

DialogMode
Native UI integration or deterministic Day request/response testing.
ShotPolicy
Which captures a run keeps.
Step

Constants§

DEFAULT_TIMEOUT_SECS
Default implicit-wait budget, in seconds.