slipcase-open 0.1.5

Open the payload of a Slipcase container in its own application, and write edits back into the container
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

//! The slipcase-open engine: everything the tool does that is not a user
//! interface.
//
// Author: David M. Anderson
// Built with AI assistance (Claude, Anthropic)
//
//! Concept 8 keeps this free of any dependency on how the tool presents
//! itself, so that the session model is one body of code on three platforms
//! rather than three programs sharing a name, and so that every
//! security-relevant decision — validation, policy, the launch path, the
//! write-back — lives in one place and is testable without a desktop.
//!
//! `src/main.rs` is the command line over it, which concept 9 keeps as the
//! floor beneath the notifications and the tray.

// The level `Cargo.toml` explains: `forbid` everywhere Windows is not.
#![cfg_attr(not(windows), forbid(unsafe_code))]

pub mod content;
pub mod endpoint;
pub mod extension;
pub mod extract;
pub mod flow;
pub mod identity;
pub mod ipc;
pub mod outside;
pub mod platform;
pub mod policy;
pub mod present;
pub mod recover;
pub mod resident;
pub mod session;
pub mod table;
pub mod watch;
pub mod writeback;