Primitive Explorer
Operational primitives are stable ingredients: reusable capabilities that should converge over time rather than fragment by customer or industry.
Intake / Ingestion
Captures requests, alerts, tickets, documents, signals, and events into a consistent operational starting point.
Workflows using it
Industries using it
Should this become a primitive?
Intake appears across nearly every workflow and is foundational for agent-safe invocation because agents need validated inputs.
Operational examples
- Vendor request form
- Security alert intake
- Support ticket capture
- Prior authorization packet
Related primitives
Canonical Entity Layer
Normalizes domain nouns into stable entities such as customers, vendors, users, assets, policies, patients, and cases.
Workflows using it
Industries using it
Should this become a primitive?
Entity normalization is a shared substrate capability, not a recipe-specific feature, when multiple operators depend on consistent records.
Operational examples
- Vendor profile
- Patient case
- Account graph
- Identity record
Related primitives
Search / Retrieval
Finds relevant records, documents, context, policies, evidence, and historical resolutions.
Workflows using it
Industries using it
Should this become a primitive?
Retrieval is reusable because most operators need trusted context before decisions or recommendations.
Operational examples
- Find similar support cases
- Retrieve vendor documents
- Search security runbooks
- Surface account history
Related primitives
Evidence / Traceability
Collects, cites, and preserves the artifacts that justify operational decisions.
Workflows using it
Industries using it
Should this become a primitive?
Evidence is governance-critical and agent-valuable because automated actions require traceable justification.
Operational examples
- Approval rationale
- Log bundle
- Call transcript citation
- Compliance artifact packet
Related primitives
Recommendation / Prioritization
Ranks next actions, opportunities, risks, or cases based on configured signals and goals.
Workflows using it
Industries using it
Should this become a primitive?
Recommendation becomes a primitive when ranking logic is reused across operators and grounded in evidence.
Operational examples
- Next best revenue action
- Case priority
- Creator shortlist
- Incident severity
Related primitives
Workflow / Orchestration
Coordinates steps, states, assignments, waits, escalations, and tool calls across an operational process.
Workflows using it
Industries using it
Should this become a primitive?
Workflow orchestration is the clearest shared primitive because recipes differ mostly in composition, not execution substrate.
Operational examples
- Procurement routing
- Incident remediation
- Support resolution path
- Access review
Related primitives
Approval / HITL
Captures human review, authorization, exception handling, and accountable handoffs.
Workflows using it
Industries using it
Should this become a primitive?
Approval is reused across industries and is governance-critical, especially when agents trigger operational tools.
Operational examples
- Manager approval
- Security authorization
- Clinical review
- Budget exception
Related primitives
Timeline / Audit
Records what happened, when, why, by whom, and with which supporting artifacts.
Workflows using it
Industries using it
Should this become a primitive?
Timelines are broadly reused and foundational for auditability, debugging, agent supervision, and customer trust.
Operational examples
- Case history
- Approval trail
- Incident chronology
- Deal activity stream
Related primitives
Graph / Relationships
Models relationships among entities, signals, people, policies, cases, vendors, and assets.
Workflows using it
Industries using it
Should this become a primitive?
Graph capabilities become primitive when multiple recipes need relationship traversal and impact awareness.
Operational examples
- Account relationship map
- Identity access graph
- Vendor dependency map
- Creator audience adjacency
Related primitives
Communication / Notifications
Sends updates, requests missing information, coordinates handoffs, and notifies stakeholders.
Workflows using it
Industries using it
Should this become a primitive?
Communication is reusable when templates standardize stakeholder updates, reminders, and escalation patterns.
Operational examples
- Approval reminder
- Customer update
- Vendor document request
- Incident escalation note
Related primitives
Learning / Evaluation
Measures outcomes, compares recommendations to decisions, captures feedback, and improves future workflows.
Workflows using it
Industries using it
Should this become a primitive?
Learning is a platform primitive when evaluation loops are reused across agent-ready operational capabilities.
Operational examples
- Resolution quality score
- Recommendation acceptance
- Policy drift signal
- Agent tool evaluation
Related primitives
Policy / Governance
Encodes rules, eligibility, compliance constraints, thresholds, permissions, and operating policies.
Workflows using it
Industries using it
Should this become a primitive?
Policy is deterministic, governance-critical, and agent-valuable, so it should converge as a shared primitive.
Operational examples
- Access policy
- Procurement threshold
- Clinical requirement
- SLA rule
Related primitives