Decisions, engineered.Book a Decision Discovery ↗EDAF™ is Brillion’s defining, technology-independent framework for treating enterprise decisions as first-class architectural assets.
EDAF™ stands for Enterprise Decision Architecture Framework. It is Brillion’s intellectual property and defining framework for how enterprises identify, architect, govern, engineer, operate, measure and improve decisions.
EDAF™ gives enterprises a technology-independent way to describe the decisions that connect intent, evidence, authority and outcomes.
EDAF™ is Brillion’s intellectual property and defining framework for Enterprise Decision Management. It supplies the vocabulary, principles, meta-model, reference views, lifecycle and governance concepts needed to treat decisions as part of enterprise architecture. The framework is deliberately broader than a rules engine or a modelling notation: it describes how a decision belongs to the enterprise, how it is governed and how its effects are observed over time.
The framework begins with a simple architectural observation. Information does not create business value by existing in a data platform; value is created when authorised people or systems use information to determine what should happen next. That determination is shaped by objectives, policy, risk appetite, constraints, models, available resources and human judgement. EDAF™ makes those relationships explicit so that a decision can be designed and discussed before it is embedded in a product or process.
EDAF™ is not a claim that every organisation must use one technology or one degree of automation. A decision may be implemented with rules, a DMN model, a predictive model, optimisation, a graph, a simulation, a human review or a combination of these mechanisms. The architecture remains useful because it records the purpose, authority, dependencies, evidence and outcomes independently of the implementation choice.
At the upper level, a business objective and capability explain why a decision exists. A decision domain groups related questions such as eligibility, pricing or allocation. An Enterprise Decision Object describes a governed class of determinations: its owner, objective, trigger, inputs, policies, rules, models, constraints, confidence, explanation, review path, action, outcomes, measures, feedback, version and audit evidence. A decision service then exposes the approved behaviour to the systems and people that need to use it.
This structure prevents two common errors. The first is to start with a technical component and call it the decision, even though the component has no clear owner, authority or outcome. The second is to write a policy document without defining how its intent becomes a repeatable service. EDAF™ holds the business and engineering views together without collapsing them into one artefact.
A decision is consequential because it changes a case, a customer, a resource position or a future option. Its governance therefore cannot be added after deployment. EDAF™ treats approval, effective dates, test evidence, explanation, human review, audit, monitoring and retirement as architectural concerns. The lifecycle runs from discovery and modelling through validation, approval, publication, execution, observation, explanation, learning, improvement and retirement.
The current EDAF™ material is controlled alpha content. Brillion labels proposed principles and research constructs clearly so that readers can distinguish a framework definition from an externally verified standard. That editorial discipline is part of the framework’s purpose: an authority on decisions must make the status and limits of its own claims visible.
Constitutional proposition
An enterprise is fundamentally a governed network of interconnected decisions that transform information into business outcomes.
This is an EDAF™ architectural premise. It is not presented as an empirically proven universal description of every organisation.
Objectives, capabilities, domains, decision objects, authority, actions, outcomes and evidence belong in one coherent architecture.
Open the architecture library →
Selected architecture principles
Model dependencies, shared sub-decisions, authority and outcome effects.
Give every material decision an identity, owner, version and lifecycle.
Preserve accountability even when execution is synchronous.
Capture enough evidence to reconstruct, explain and assure a decision.
Observe trigger, result, action, outcome and improvement.
Learning proposes a change; it does not silently mutate approved logic.
A governed, versioned architectural description of a class of determinations. It connects purpose and context, determination mechanisms, authorised execution, outcomes, evidence and controlled improvement.
Explore every attribute ↗Lifecycle
Autonomy is the sixth stage, not the starting point. It requires observable decisions, bounded authority, evidence and controlled learning.
