Stable Public Vocabulary

Audience: automation builders and API evaluators Status: Preview

Ophiolite should teach proof primitives before wrapper names.

Core Nouns

• Project: local project root and governance store
• DataItem: logical scientific object
• DataRevision: immutable exact version used by operators, task workspaces, and visual panels
• SourceArtifact: source file or external record kept as evidence
• ImportReceipt: import decisions plus source fingerprints
• ProvenanceActivity: recorded activity that produced or changed data
• FlowDraft / WorkflowRecipe: execution input to validate and plan
• Run: execution instance of an operator, task action, or backend flow
• RunBundle: raw/reopenable record of a run
• EventLog: hash-chained run or governance events
• EvidenceRecord: proof attached to a run, review, or deliverable
• ReviewPacket: signed, offline-verifiable interchange artifact

Public Control Surfaces

• CLI: exact JSON command boundary for automation and CI
• Python automation: thin ophiolite_automation wrapper over CLI JSON
• Run bundles: signed raw record of recipe/flow, plan, report, digests, artifacts, and events
• Review packets: signed external proof artifact for partners, regulators, or internal assurance reviewers
• Governance log: durable review, evidence attachment, and approval records

What Should Stay Out of the Main Vocabulary

• notebook widget hosts
• app-local command names
• compatibility DTOs as first-contact docs
• wrapper-only domain objects that do not create provenance or evidence

Practical Rule

If a surface cannot explain how it records source evidence, exact revisions, events, or review/audit state, keep it out of the public workflow story.

Next: Operator catalog and composition