DOCS / REFERENCE

Domain model reference

Review the strict, vendor-neutral Pydantic contracts exported from lumis_sdk.domain.

PHASE 1 · PRE-1.0PYTHON 3.11+EDIT ON GITHUB ↗

Incident and diagnosis

TypePurpose
IncidentInputSource tool, optional pipeline, environment, and raw payload.
EvidenceItem / EvidenceRequest / EvidenceCollection / EvidenceFailureBounded observations, the collection ask, the typed answer, and structured collection errors.
TriageResultClassification, severity, summary, and missing context.
DiagnosisResultFacts, hypothesis, confidence, evidence, gaps, next steps, method, and review flag.
ConfirmedResolutionHuman- or verification-confirmed cause, action, outcome, and truth state.
Severity / DiagnosisMethod / TruthStateThe shared enums used across diagnosis and memory.

Planning and governance

TypePurpose
PlaybookDocument / PlaybookAction / ParameterDefinitionVersioned allowlist of typed, bounded, risk-labeled actions.
PolicyDocument / PolicyRuleDefault-deny mapping from actions to approval requirements.
ActionProposal / EvidenceReferenceRecommendation-only, digest-linked, expiring proposal with bounded parameters.
ApprovalDecision / ApprovalDecisionRecordExplicit attributable approval state with idempotency support.
VerificationRequest / VerificationCheck / VerificationRecordExplicit passed, failed, unknown, or timed-out verification outcomes.
AuditEvent / LifecycleResultInspectable transitions and the complete output of one non-executing lifecycle run.
PluginManifest / PluginLoadPolicy / PluginAuthorityStatic plugin identity, explicit load policy, and named sensitive authorities.

Strict contracts

Public domain models reject unknown fields. This makes integration mistakes visible and prevents provider-specific data from silently leaking into core contracts. Proposal and approval documents additionally use canonical JSON with SHA-256 digests, so revisions can be pinned and tampering is detectable.