Expand description
Consent-first safety state for adult human–humanoid intimacy.
inobot-p does not describe intimate acts and does not control hardware. It
models the conditions that must be true before an application may run an
authorized operation: adult human attestation, independent refusal ability,
explicit activity-level agreement from both participants, physical safety
checks, immediate withdrawal, and irreversible emergency stop.
§Example
use inobot_p::{Activity, Consent, Participant, SafetyChecklist, SessionPlan};
let human = Participant::adult_human("human")?;
let robot = Participant::autonomous_humanoid("robot")?;
let activity = Activity::new("private-affection-v1")?;
let plan = SessionPlan::new(human, robot)?;
let human_consent = Consent::new("human", [activity.clone()])?;
let robot_consent = Consent::new("robot", [activity.clone()])?;
let mut session = plan.activate(
human_consent,
robot_consent,
SafetyChecklist::all_confirmed(),
)?;
let result = session.authorize(&activity, |_| "authorized only in this closure")?;
assert_eq!(result, "authorized only in this closure");Authorization cannot escape the closure:
ⓘ
use inobot_p::{Activity, Consent, Participant, SafetyChecklist, SessionPlan};
let activity = Activity::new("policy-v1").unwrap();
let plan = SessionPlan::new(
Participant::adult_human("h").unwrap(),
Participant::autonomous_humanoid("r").unwrap(),
).unwrap();
let mut session = plan.activate(
Consent::new("h", [activity.clone()]).unwrap(),
Consent::new("r", [activity.clone()]).unwrap(),
SafetyChecklist::all_confirmed(),
).unwrap();
let escaped = session.authorize(&activity, |authorization| authorization).unwrap();Structs§
- Active
Session - An activated session with revocable, activity-level authorization.
- Activity
- An opaque, non-explicit activity identifier selected by the host app.
- Authorization
- A short-lived proof available only inside
ActiveSession::authorize. - Consent
- Explicit allow-list consent from one participant.
- Participant
- A session participant with explicit capacity properties.
- Safety
Checklist - Physical, capacity, and privacy checks required before activation.
- Session
Plan - A validated human–humanoid pair before consent and safety activation.
Enums§
- Error
- Validation and authorization errors.
- Role
- Participant role in a human–humanoid session.
- Session
Status - Terminal and active session states.