Architecture
Built around the process, not another technology silo.
Eight layers with one write path and one record. Executives can read it as responsibilities; architects as a system. Capability status is stated where it matters.
Layers
From connection to experience.
Operational Memory is not a layer of its own in the stack — it runs through every layer, written by every action and read by every decision.
- Experience
- Executive
- Process owner
- Analyst
- Operator
- Developer
- Admin
One platform, several surfaces: the executive sees outcomes and value; the operator sees today's prioritized queue; the analyst sees maps, variants and root causes; the developer sees APIs and playbook-as-code; the admin sees identities, policies and costs.
- GovernanceProcesario Control
- Identity
- Permissions
- Policies
- Autonomy
- HITL
- Audit
- Model governance
- Cost controls
Every executor — person, agent, automation, system — acts under an identity, a scope, a policy and an autonomy level, and leaves an audit record.
- OrchestrationProcesario Orchestrate
- Workflow
- AI agents
- Humans
- APIs
- Systems
- RPA
- Events
Playbooks route each intervention to the executor suited to the work, with durable execution for interventions that take days.
- Decision
- Recommendations
- Rules
- Policies
- Next-best action
- Optimization
- Explainability
- Confidence
Prediction, process context, policy, value, risk and human judgment combine into a permitted next step. No hidden leap from “AI says” to “system executes.”
- PredictionProcesario Predict
- Next event
- Remaining time
- SLA risk
- Payment risk
- Delivery risk
- Exception probability
- Anomaly
Case-level prediction with calibrated confidence and process-language explanations, refreshed as events arrive.
- Process intelligenceProcesario Discover
- Discovery
- Conformance
- Variants
- Root cause
- Object-centric analysis
- KPI
- Value leakage
The evidence base: how each process actually runs, where it deviates, what drives delay and what each leak costs.
- Process contextProcesario Process Graph
- Cases
- Objects
- Events
- Activities
- Roles
- Systems
- Policies
- Decisions
- Relationships
- Outcomes
The connected representation of how work relates — derived from events, not hand-modelled — that gives predictions coherence and agents context.
- Connect
- ERP
- CRM
- Databases
- Files
- APIs
- Event streams
- Documents
- Data platforms
Read broadly from the systems where work happens; write narrowly through governed actions. No data warehouse to build.
Spans all layers
Operational Memory
The record of what was predicted, decided, done and achieved — read by every layer, written by every action.
- predictions
- decisions · edits
- actions · agent traces
- outcomes · KPI deltas
- policy changes
Design principles
Six decisions that shape everything else.
- 01
Event-native, object-centric
Everything enters as events about objects. Cases are views over objects, so one order with three invoices and two deliveries is one connected trace.
- 02
Read broadly, write narrowly
Procesario reads from data platforms and systems of record; it writes to them only through governed actions that are typed, permissioned, logged and reversible where possible.
- 03
Predictions are objects
A prediction has a subject, a target, a value, a confidence, an explanation, a model version and a lifecycle. It is stored, not just displayed.
- 04
Every action has a policy and a record
No executor — human, agent, automation or API — runs outside an autonomy level and an audit entry.
- 05
Model- and vendor-neutral
Model providers, agent frameworks, RPA tools and workflow engines are executors behind interfaces. The intelligence, the policies and the record are Procesario's.
- 06
Built for the data platform you run
Designed to compute against the customer's data platform where possible, which shortens security reviews and avoids becoming another warehouse.
Process context
The Procesario Process Graph.
The connected representation of how work relates: processes, cases, events and activities; the customers, suppliers, orders, invoices and assets they concern; the roles, teams, systems, agents and automations that act on them; the rules, policies, decisions and KPIs that govern them; and the predictions, risks, recommendations, interventions and outcomes of the loop itself.
The graph is derived from events rather than hand-modelled, and it carries predictions and interventions as first-class objects. It is what gives an explanation its coherence and an agent its context. Not every object is implemented today; the semantics are what the platform is built toward.
- process
- Process · Case · Event · Activity
- business
- Customer · Supplier · Order · Invoice · Asset
- organization
- Role · Team · System · Agent · Automation
- governance
- Rule · Policy · Decision · KPI
- loop
- Prediction · Risk · Recommendation · Intervention · Outcome
The record
Procesario Operational Memory.
The persistent record of the loop: each prediction with its model version, each recommendation with its evidence, each approval, rejection or human modification, each agent or automated action with its inputs and outputs, and each measured result.
Designed as an append-only record so that results are reported from evidence — treated cases against comparable untreated cases — rather than asserted. This is a design intent and a development target, not a claim of a finished product.
- Prediction
value · confidence · drivers · model version
1 - Recommendation
action · expected value · policy
2 - Decision
approved · edited · rejected · by whom
3 - Action
executor · level · inputs · outputs
4 - Result
outcome · KPI delta · timing
5
Procesario Operational Memory
append-only · every entry linked to its case
- Prediction
- Model version
- Recommendation
- Evidence
- Approval
- Rejection
- Human modification
- Agent action
- Automated action
- Execution
- Outcome
- Performance
result → next prediction · next recommendation · next autonomy decision
For technical readers
Where to go next.
Start with the outcome you want to change.
Show us one process where delay, risk, rework or exceptions cost real money. We'll explore how Procesario could move from evidence to prediction to controlled action.